CVE-2026-128987 · Infrastructure
NO FIX YET
A flaw in dbus's socket transport treats broken pipe write errors as retryable, so a local client that stops reading while keeping its connection open makes the target process loop continuously. The result is excessive CPU use and a denial of service for that process.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only local users or processes that can connect to an affected dbus service can trigger this, so the exposure is on machines where untrusted local code can reach the bus. The sources do not name the affected dbus versions or which services are most exposed. Systems where only trusted local users run software are lower risk.
Not affected if no-untrusted-local-users
Who cares dbus, linux, local-services
Unknown from the sources.
No fix yet, per the sources.
A flaw was found in dbus. A local attacker can exploit this vulnerability by connecting to an affected service, requesting a response, and stopping socket reads while keeping the connection open. Because the socket transport handles broken pipe write errors as retryable, the application enters a continuous retry loop. This can lead to excessive CPU consumption, resulting in a denial of service (DoS) for the target process.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.