CVE Alert: CVE-2026-110331 – Red Hat

A flaw was found in abrt. The completeness check introduced to mitigate CVE-2026-54228 and CVE-2026-54229 only verifies that a dump directory contains a "count" element, which an unprivileged user can create. This allows a local attacker to bypass the guard and again poison elements in, or seize ownership of, dump directories while privileged ABRT handlers are processing them. Related Problems2 mutating methods remain ungated by the same check.

**Risk verdict:** High risk on systems with untrusted local users; urgency cannot be fully calibrated because KEV, SSVC, PoC and EPSS data were not provided.

**Why this matters:** A local user with limited privileges may interfere with crash-report processing, potentially causing privileged handlers to alter files or directory ownership. This could support tampering, disruption, or a stepping stone to greater access, although the stated scope indicates impact should remain within the affected system.

**Most likely attack path:** An attacker needs local access and low-level privileges; network access, complex conditions and another user’s interaction are not required. They exploit the report-processing workflow while a privileged handler operates on attacker-influenced data. The stated unchanged scope suggests no direct cross-security-boundary impact, but resulting file changes may affect services or data on the same host.

**Who is most exposed:** Multi-user enterprise Linux hosts with crash-reporting services enabled are most exposed, especially shared servers and systems where local accounts or workloads are not fully trusted.

Review crash-report directories for unexpected ownership, permissions or newly created entries.

Correlate report-processing activity with file changes by unprivileged users.

Alert on crashes or handler failures followed by unusual service or file activity.

Check service and D-Bus activation logs for unexpected invocation.

Mitigation and prioritisation:

Apply the vendor’s fixed package as soon as available; verify remediation covers all affected mutating paths.

If reporting is unnecessary, disable or remove the related services, accounting for D-Bus activation.

Restrict local account access and monitor privileged handler activity.

Test the update and service changes on representative hosts before broad deployment.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.