CVE-2026-54228
Received Received - Intake
TOCTOU Race Condition in abrt-dbus D-Bus Service

Publication date: 2026-06-13

Last updated on: 2026-06-13

Assigner: Red Hat, Inc.

Description
A time-of-check time-of-use (TOCTOU) race condition was found in the abrt-dbus D-Bus service's SetElement method. Between dump directory creation and post-create event execution, any local user can call SetElement to write arbitrary text files into the root-owned dump directory, bypassing package validation and allowing crashes of unpackaged binaries to survive post-create processing.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-13
Last Modified
2026-06-13
Generated
2026-06-13
AI Q&A
2026-06-13
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
red_hat automatic_bug_reporting_tool *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-367 The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-54228 is a security vulnerability in the Automatic Bug Reporting Tool (abrt) on Red Hat systems. It involves a time-of-check time-of-use (TOCTOU) race condition in the abrt-dbus D-Bus service's SetElement method. This flaw allows a local user to exploit a timing window between the creation of a dump directory and the execution of post-create event scripts. During this window, the attacker can write arbitrary text files into a root-owned dump directory by calling SetElement.

The vulnerability occurs because the access check incorrectly matches the caller's user ID with the dump directory's user ID, enabling unauthorized file writes. This allows malicious files to be planted before processing scripts handle them, bypassing package validation and allowing crashes from unpackaged binaries to survive post-create processing.

Impact Analysis

This vulnerability can allow a local attacker to write arbitrary files into a root-owned dump directory, bypassing package validation mechanisms.

As a result, crashes from unpackaged binaries could evade the normal post-create processing, potentially leading to unauthorized or malicious files being processed with elevated privileges.

This could pose a significant security risk by allowing attackers to execute or persist malicious code on the affected system.

Detection Guidance

Detection of this vulnerability involves monitoring the behavior of the abrt-dbus D-Bus service, specifically the SetElement method, for unauthorized or suspicious file writes to the root-owned dump directory.

Since the vulnerability exploits a timing window between dump directory creation and post-create event execution, you can look for unexpected files in the dump directory that do not correspond to legitimate crash reports.

Commands to help detect potential exploitation might include:

  • Checking for unexpected files in the dump directory (usually under /var/spool/abrt or similar): `ls -l /var/spool/abrt`
  • Monitoring D-Bus calls to the abrt-dbus service for SetElement method usage by local users: `dbus-monitor --system "type='method_call',interface='org.freedesktop.abrt.DBus'"`
  • Reviewing system logs for abnormal abrt activity: `journalctl -u abrtd` or `grep abrt /var/log/messages`
Mitigation Strategies

Immediate mitigation steps include restricting access to the abrt-dbus service to trusted users only, as the vulnerability requires local user access.

Additionally, applying any available patches or updates from Red Hat that address this TOCTOU race condition is critical.

As a temporary workaround, consider disabling the abrt-dbus service if it is not essential, to prevent exploitation.

Monitoring and auditing file creation in the dump directory can also help detect and respond to exploitation attempts.

Compliance Impact

The provided information does not specify how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-54228. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart