# CVE-2026-54229: Abrt: chownproblemdir succeeds during active post-create event processing due to inadequate locking

> A race condition in abrt-dbus allows attackers to gain filesystem control over dump directories during event processing, leading to privilege escalation.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jun 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-c3cq-8jxp-w66j

## What is CVE-2026-54229?

CVE-2026-54229 is a high-severity vulnerability in Red Hat Enterprise Linux 6, published on 13 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A 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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-54229?


## How do I fix CVE-2026-54229?

Apply the vendor's patch.

## Is CVE-2026-54229 being exploited?

There is no known exploitation of CVE-2026-54229 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54229 and fix it if it is affected.

What it is: CVE-2026-54229 is a high-severity vulnerability in Red Hat Enterprise Linux 6, published on 13 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54229 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 6. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54229/ (Markdown: https://insights.sbomify.com/CVE-2026-54229/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54229
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54229
- OSV: https://osv.dev/vulnerability/CVE-2026-54229

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54229/
Summaries are generated and may contain mistakes; the official description above is the record.