OESA-2026-4902: dbus security update
D-Bus is a message bus system, a simple way for applications to talk to one another. In addition to interprocess communication, D-Bus helps coordinate process lifecycle; it makes it simple and reliable to code a "single instance" application or daemon, and to launch applications and daemons on demand when their services are needed. Security Fix(es):
A flaw was found in D-Bus. With a privileged Monitoring client attached (for example dbus-monitor or busctl monitor), an unprivileged local user can cause dbus-daemon to abort if a driver-originated broadcast such as NameOwnerChanged or ActivatableServicesChanged cannot be delivered to a recipient (for example due to a deny rule or an exceeded outgoing message queue). Driver broadcasts still use serial 0; when delivery fails, composing the monitor error reply asserts replyserial != 0 and aborts the daemon.(CVE-2026-120749)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
openeuler/dbusto a version that resolves this vulnerability.Fixed in 1.14.8-4.oe2403sp4
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems running dbus-daemon are exposed when a privileged Monitoring client is attached, such as dbus-monitor or busctl monitor. The failure condition also requires a driver-originated broadcast to be undeliverable to a recipient, for example because of a deny rule or an exceeded outgoing message queue.
What access does an attacker need?
An attacker needs local access as an unprivileged user. No privileges or user interaction are required according to the supplied severity vector.
What is the practical effect of successful exploitation?
Successful exploitation causes dbus-daemon to abort, resulting in a denial of service. The supplied vector indicates availability impact only, with no stated confidentiality or integrity impact.