CVE-2026-120749: Dbus: dbus-daemon: dbus-daemon aborts (reply_serial != 0) when a broadcast from the driver cannot be delivered to a monitored bus
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. This is an incomplete fix for CVE-2023-34969, which only assigned serials for driver messages sent to a single recipient. On the well-known system bus this is a denial of service.
Other sources
A flaw was found in dbus. This is an incomplete fix for CVE-2023-34969. On multi-user buses such as dbus-daemon --system, if a privileged user has attached a monitoring process such as dbus-monitor or busctl monitor to the system bus, an unprivileged user can trigger a dbus-daemon crash, resulting in a denial of service.
Upstream reference: https://gitlab.freedesktop.org/dbus/dbus/-/workitems/576
Reported via PSIRTSUPT-26737 by Simon McVittie.
— Red Hat