Source: dbus Version: 1.9.10-1 Severity: normal Tags: upstream security X-Debbugs-Cc: Debian Security Team <[email protected]> Forwarded: https://gitlab.freedesktop.org/dbus/dbus/-/work_items/576
If a privileged user with control over the dbus-daemon is using the org.freedesktop.DBus.Monitoring interface to monitor message bus traffic, then an unprivileged user with the ability to connect to the same dbus-daemon can cause a dbus-daemon crash under some circumstances. When done on the well-known system bus, this is a denial-of-service vulnerability exploitable by a local user. A major mitigation is that this can only be done if a monitoring process such as dbus-monitor or busctl monitor is active on the same dbus-daemon instance, which is a privileged operation that can only be done by root or the Unix uid of the message bus. If no monitoring process is active, then the vulnerable code is not reached. The situation in which the message bus can be crashed is that an unprivileged user causes the message bus to emit a broadcast signal such as NameOwnerChanged or ActivatableServicesChanged, but the signal cannot be delivered, for example because it is forbidden by a <deny> rule or because the recipient has exceeded the configured limit on its number of queued messages. All versions >= 1.9.10 are vulnerable. It is addressed by 1.16.4, which I plan to release shortly. The security team have already declined to release a DSA for this, see <https://security-tracker.debian.org/tracker/CVE-2026-120749>. smcv

