7.5

CVE-2026-64374: sched/rt: Have RT_PUSH_IPI be default off for non PREEMPT_RT

Modified
AliasesUBUNTU-CVE-2026-64374DEBIAN-CVE-2026-64374
Published 25-07-2026Last modified 19-10-2026

Vulnerability summary

CVE-2026-64374 is a high (CVSS 7.5) Improper Locking vulnerability in linux. EPSS estimates a 0.39% chance of exploitation in the next 30 days, higher than 33.6% of scored vulnerabilities.

Priority
Prioritisesevere

Severe, CVSS 7.5 (CVE.org); no exploitation reported by the 5 checked sources; EPSS 0% (FIRST, 20-11-2026)

Source freshness unavailable

How is this decided?
CVSS score
7.5/10
010
High · v3.1 (CVE.org)
EPSS score
0.39%
0%100%
Low · 0.00 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 32 · Related 28

Timeline

  1. 25-07-2026
    PublishedVulnerability first disclosed.
  2. 19-10-2026
    Last modifiedVulnerability information updated.

Description

In the Linux kernel, the following vulnerability has been resolved: sched/rt: Have RT_PUSH_IPI be default off for non PREEMPT_RT RT migration is done aggressively. When a CPU schedules out a high priority RT task for a lower priority task, it will look to see if there's any RT tasks that are waiting to run on another CPU that is of higher priority than the task this CPU is about to run. If it finds one, it will pull that task over to the CPU and allow it to run there instead. Normally, this pulling is done by looking at the RT overloaded mask (rto) which contains all the CPUs in the scheduler domain with RT tasks that are waiting to run due to a higher priority RT task currently running on their CPU. The CPU that is about to schedule a lower priority task will grab the rq lock of the overloaded CPU and move the RT task from that CPU's runqueue to the local one and schedule the higher priority RT task. This caused issues when a lot of CPUs would schedule a lower priority task at the same time. They would all try to grab the same runqueue lock of the CPU with the overloaded RT tasks. Only the first CPU that got in will get that task. All the others would wait until they got the runqueue lock and see there's nothing to pull and do nothing. On systems with lots of CPUs, this caused a large latency (up to 500us) which is beyond what PREEMPT_RT is to allow. The solution to that was to create an RT_PUSH_IPI logic. When any CPU wanted to pull a task, instead of grabbing the runqueue lock of the overloaded CPU, it would start by sending an IPI to the overloaded CPU, and that IPI handler would have the CPU with the waiting RT task do a push instead. Then that handler would send an IPI to the next CPU with overloaded RT tasks, and so on. Note, after the first CPU starts this process, if another CPU wanted to do a pull, it would see that the process has already begun and would only increment a counter to have the IPIs continue again. The RT_PUSH_IPI solved the latency problem with PREEMPT_RT but could cause a new issue with non PREEMPT_RT. Namely, softirqs run in a threaded context on PREEMPT_RT but they can run in an interrupt context in non-RT. If an IPI lands on a CPU that has just woken up multiple RT tasks and the current CPU is running a non RT or a low priority RT task, instead of doing a push, it would simply do a schedule on that CPU. But if a softirq was also executing on this CPU, the schedule would need to wait until the softirq finished. Until then, the CPU would still be considered overloaded as there are RT tasks still waiting to run on it. A live lock occurred on a workload that was doing heavy networking traffic on a large machine where the softirqs would run 500us out of 750us. And it would also be waking up RT tasks, causing the RT pull logic to be constantly executed. When a softirq triggered on a CPU with RT tasks queued but not running yet, and the other CPUs would see this CPU as being overloaded, they would send an IPI over to it. The CPU would notice that the waiting RT tasks are of higher priority than the currently running task and simply schedule that CPU instead. But because the softirq was executing, before it could schedule, it would receive another IPI to do the same. The amount of IPIs would slow down the currently running softirq so much that before it could return back to task context, it would execute another softirq never allowing the CPU to schedule. This live locked that CPU. As RT_PUSH_IPI was created to help PREEMPT_RT, make it default off if PREEMPT_RT is not enabled.

CVSS metrics

4 scores · 4 sources · 1 version

EPSS trend

Probability

0.39%

Chance of exploitation in the next 30 days

Percentile

34%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.39% 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

Affected systems

Version check

Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu169 products
  • linuxAll versions (No fix recorded) | < 5.15.0-198.208 | < 6.8.0-147.147 | < 7.0.0-31.31
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 5.15.0-1117.124 | < 6.8.0-1067.70 | < 7.0.0-1012.12
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian2 products
  • linux< 6.1.180-1 | < 6.12.96-1 | < 7.1.4-1
  • linux-6.12< 6.12.100-1~deb12u1
Linux2 products
  • linux≥ b6366f048e0caff28af5335b7af2031266e1b06b, < b99f04ae3d200d2f8844aa29145bd18eccbeecde | ≥ b6366f048e0caff28af5335b7af2031266e1b06b, < d8312a56d9a162e3ec76476aa487e7d20bc602e9 | ≥ b6366f048e0caff28af5335b7af2031266e1b06b, < 44aae426dbfd51286f7eb601cfa14bc32164812a | ≥ b6366f048e0caff28af5335b7af2031266e1b06b, < 860aaff72c8446fed5e576249e19952883a18885 | ≥ b6366f048e0caff28af5335b7af2031266e1b06b, < 89237c8fc15d8016a194076e648ccb57d75e65ae | ≥ b6366f048e0caff28af5335b7af2031266e1b06b, < 4bd0da48fbc1dbef6774175129107fbbdd353e26 | ≥ b6366f048e0caff28af5335b7af2031266e1b06b, < a18f80bf5359238c4f067d691b96af00286fdd89 | ≥ b6366f048e0caff28af5335b7af2031266e1b06b, < dd29c017aed628076e915fe4cdfb5392fd4c5cab | 4.1
  • linux_kernel≥ 4.1, < 5.10.261 | ≥ 5.11, < 5.15.212 | ≥ 5.16, < 6.1.178 | ≥ 6.2, < 6.6.145 | ≥ 6.7, < 6.12.96 | ≥ 6.13, < 6.18.39 | ≥ 6.19, < 7.1.4

3 vendors · 173 products

References

40 links
Show all 40 references