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

  • Medium 6.2

Description

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.

Key facts

Published
6 Nov 2026
Last changed
13 Nov 2026
Assigned by
redhat
EPSS
0.124% likely to be exploited in the next 30 days, higher than 2.205% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.2CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

What to do

  • 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.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Hardened Images
  • Default status: affected
  • 1.16.2-7.1.hum1 up to but excluding * (unaffected)
Red HatRed Hat Enterprise Linux 10
  • Default status: affected
Red HatRed Hat Enterprise Linux 6
  • Default status: unaffected
Red HatRed Hat Enterprise Linux 7
  • Default status: unknown
Red HatRed Hat Enterprise Linux 8
  • Default status: affected
Red HatRed Hat Enterprise Linux 9
  • Default status: affected

Timeline

  1. 27 Oct 2026 Reported to Red Hat.
  2. 27 Oct 2026 Made public.
  3. 6 Nov 2026 Published

Weakness

References