Service disruption via missed deadline replenishment
Published Mar 25, 2026 · Updated Mar 25, 2026
Scheduler accounting error in affected Linux Kernel releases allows local users to disrupt service through SCHED_DEADLINE priority changes. When a DEADLINE lock holder is moved to a lower class while a DEADLINE donor waits on its PI mutex, sched_setscheduler() fails to inherit the donor parameters and enqueue_task_dl() omits ENQUEUE_REPLENISH, corrupting running-bandwidth accounting. Exploitation requires local low-privileged access and the specific priority-inheritance sequence; the observed result is scheduler warnings and bandwidth underflow, with availability impact rather than data disclosure or modification.
Summary
What happened
Scheduler accounting error in affected Linux Kernel releases allows local users to disrupt service through SCHED_DEADLINE priority changes. When a DEADLINE lock holder is moved to a lower class while a DEADLINE donor waits on its PI mutex, sched_setscheduler() fails to inherit the donor parameters and enqueue_task_dl() omits ENQUEUE_REPLENISH, corrupting running-bandwidth accounting. Exploitation requires local low-privileged access and the specific priority-inheritance sequence; the observed result is scheduler warnings and bandwidth underflow, with availability impact rather than data disclosure or modification.
The record
- CVE
- CVE-2026-23371
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2279f540ea7d05f22d2f0c4224319330228586bc <ba1c22924ddcc280672a2a06a9ca99ee3a1b92c3
- Affected versionversion=2279f540ea7d05f22d2f0c4224319330228586bc <d658686a1331db3bb108ca079d76deb3208ed949
- Affected versionversion=3cc3d77dc541181f97f1dc96d2977ef8359fd760
- Affected versionversion=5.10
- Affected versionversion=d2b65976bf1ae9d0d9dd5770cd01695559438309
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo