CVE-2026-54229
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA race condition was found in the abrt-dbus D-Bus service's ChownProblemDir method. ChownProblemDir opens the dump directory with DD_OPEN_READONLY and calls dd_chown to change ownership of all files to the caller's uid, succeeding even while post-create event handlers hold a write lock. This allows an attacker to gain filesystem-level control of the dump directory while privileged event scripts are still running.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA race condition in abrt-dbus D-Bus service's ChownProblemDir method allows attackers to gain filesystem-level control of dump directories. The method opens directories with DD_OPEN_READONLY but still calls dd_chown to change ownership to the caller's uid while post-create event handlers still hold a write lock, allowing privileged event scripts to be manipulated.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify abrt-dbus package is installedCheck for the presence of the abrt-dbus package using your package manager (e.g., rpm -qa | grep abrt-dbus, dpkg -l | grep abrt-dbus, or find /usr/libexec/abrt-dbus* and /usr/bin/abrt-dbus*)Affected if The abrt-dbus binary or package is present on the system
-
Determine abrt-dbus versionRun 'rpm -q abrt-dbus' or 'dpkg -s abrt-dbus' to get the installed version, then compare against any published fixed versions for CVE-2026-54229Affected if The installed version is lower than the fixed version (if a fix has been released)
-
Check if abrt-dbus service is runningRun 'systemctl status abrt-dbus' or 'ps aux | grep abrt-dbus' to determine if the D-Bus service is activeAffected if The abrt-dbus service is currently running
-
Inspect D-Bus policy configurationExamine D-Bus policy files in /etc/dbus-1/system.d/ (such as abrt-dbus.conf) to determine which users or groups are allowed to call the ChownProblemDir methodAffected if The D-Bus policy allows unprivileged users to invoke the ChownProblemDir method without restrictions
-
Monitor for D-Bus method callsUse 'dbus-monitor --system' to observe D-Bus traffic, specifically looking for calls to the 'ChownProblemDir' method on the 'org.freedesktop.problems' interfaceAffected if Calls to ChownProblemDir are observed from untrusted users
A system is affected if abrt-dbus is running and its version is unpatched, or if the D-Bus policy permits unprivileged users to invoke the ChownProblemDir method.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper synchronization to ensure dd_chown cannot execute while event handlers hold write locks; consider removing or restricting the ChownProblemDir method's ability to change ownership on read-only opened directories.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54229 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54229 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data