5.5

CVE-2026-23371: sched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting

Modified
AliasesUBUNTU-CVE-2026-23371DEBIAN-CVE-2026-23371CGA-29v4-5g35-86j5
Published 25-03-2026Last modified 30-10-2026

Vulnerability summary

CVE-2026-23371 is a medium (CVSS 5.5) vulnerability in linux. EPSS estimates a 0.18% chance of exploitation in the next 30 days, higher than 8.2% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 5.5, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
5.5/10
010
Medium · v3.1 (NVD)
EPSS score
0.18%
0%100%
Low · +0.07 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 6 · Related 4

Timeline

  1. 25-03-2026
    PublishedVulnerability first disclosed.
  2. 30-10-2026
    Last modifiedVulnerability information updated.

Description

In the Linux kernel, the following vulnerability has been resolved: sched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting Running stress-ng --schedpolicy 0 on an RT kernel on a big machine might lead to the following WARNINGs (edited). sched: DL de-boosted task PID 22725: REPLENISH flag missing WARNING: CPU: 93 PID: 0 at kernel/sched/deadline.c:239 dequeue_task_dl+0x15c/0x1f8 ... (running_bw underflow) Call trace: dequeue_task_dl+0x15c/0x1f8 (P) dequeue_task+0x80/0x168 deactivate_task+0x24/0x50 push_dl_task+0x264/0x2e0 dl_task_timer+0x1b0/0x228 __hrtimer_run_queues+0x188/0x378 hrtimer_interrupt+0xfc/0x260 ... The problem is that when a SCHED_DEADLINE task (lock holder) is changed to a lower priority class via sched_setscheduler(), it may fail to properly inherit the parameters of potential DEADLINE donors if it didn't already inherit them in the past (shorter deadline than donor's at that time). This might lead to bandwidth accounting corruption, as enqueue_task_dl() won't recognize the lock holder as boosted. The scenario occurs when: 1. A DEADLINE task (donor) blocks on a PI mutex held by another DEADLINE task (holder), but the holder doesn't inherit parameters (e.g., it already has a shorter deadline) 2. sched_setscheduler() changes the holder from DEADLINE to a lower class while still holding the mutex 3. The holder should now inherit DEADLINE parameters from the donor and be enqueued with ENQUEUE_REPLENISH, but this doesn't happen Fix the issue by introducing __setscheduler_dl_pi(), which detects when a DEADLINE (proper or boosted) task gets setscheduled to a lower priority class. In case, the function makes the task inherit DEADLINE parameters of the donoer (pi_se) and sets ENQUEUE_REPLENISH flag to ensure proper bandwidth accounting during the next enqueue operation.

CVSS metrics

4 scores · 3 sources · 2 versions

EPSS trend

Probability

0.18%

Chance of exploitation in the next 30 days

Percentile

8%

Versus all other CVEs

30-day change

Increase +0.07 pp

From 0.12% on 21-10-2026

21-10-202620-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu155 products
  • linuxAll versions (No fix recorded) | < 6.8.0-151.151
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 6.8.0-1070.76
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Chainguard41 products
  • hyperv-daemons-6.18All versions (No fix recorded)
  • linux-aws-6.12All versions (No fix recorded)
  • linux-aws-6.18< 6.18.34-r0
  • linux-aws-6.18-boot-installed< 6.18.34-r0
  • linux-aws-6.18-bootcAll versions (No fix recorded) | < 6.18.55-r0 | < 6.18.34-r0
Debian2 products
  • linuxAll versions (No fix recorded) | < 6.1.192-1 | < 6.12.115-2 | < 6.19.8-1
  • linux-6.12< 6.12.115-2~deb12u1
Linux2 products
  • linux≥ 2279f540ea7d05f22d2f0c4224319330228586bc, < e0e20852d44261a9d69188bc483872930e7ba727 | ≥ 2279f540ea7d05f22d2f0c4224319330228586bc, < ce6253fe718811cceb3a0ae0dbf0a5941dea3eb6 | ≥ 2279f540ea7d05f22d2f0c4224319330228586bc, < 65af3633caf195d397ec4c39f51ae7615bd5a627 | ≥ 2279f540ea7d05f22d2f0c4224319330228586bc, < 0638bf16b7a73a2fe63624bd0d16d9fd904805c3 | ≥ 2279f540ea7d05f22d2f0c4224319330228586bc, < ba1c22924ddcc280672a2a06a9ca99ee3a1b92c3 | ≥ 2279f540ea7d05f22d2f0c4224319330228586bc, < d658686a1331db3bb108ca079d76deb3208ed949 | 3cc3d77dc541181f97f1dc96d2977ef8359fd760 | d2b65976bf1ae9d0d9dd5770cd01695559438309 | ≥ 4.19.257, < 4.20 | ≥ 5.4.212, < 5.5 | 5.10
  • linux_kernel≥ 4.19.257, < 4.20 | ≥ 5.4.212, < 5.5 | ≥ 5.10.1, < 6.19.7 | 5.10 | 7.0:rc1 | 7.0:rc2 | 7.0:rc3 | 7.0:rc4 | 7.0:rc5 | 7.0:rc6 | 7.0:rc7

4 vendors · 200 products

References

13 links
Show all 13 references