Dbus: dbus-daemon: dbus-daemon aborts (reply_serial != 0) when a broadcast from the driver cannot be delivered to a monitored bus
cve-program · CVE-2026-120749 · Published
No access to your tenant or devices. Every item links to its source. What this means
Historical advisory recorded 10 Nov 2026 06:02:11 UTC. Read the latest advisory.
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 reply_serial != 0 and aborts the daemon.
Read the publisher's advisorySee how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
cve-program · CVE-2026-120749 · Published
cve-program · CVE-2026-120749 · Published
cve-program · CVE-2026-120749 · Published
cve-program · CVE-2026-120749 · Published
cve-program · CVE-2026-120749 · Published
This historical link shows only this version and versions saved before it. Browse all advisory history.