CVE-2025-38234: sched/rt: Fix race in push_rt_task
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 07ecabfbca64f4f0b6071cf96e49d162fa9d138d, 35b55cd665fbfd72805318f7017626eefd13dca5, 690e47d1403e90b7f2366f03b52ed3304194c793; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 4.7.
Low priority for now. Upgrade to Linux Linux 07ecabfbca64f4f0b6071cf96e49d162fa9d138d, 35b55cd665fbfd72805318f7017626eefd13dca5, 690e47d1403e90b7f2366f03b52ed3304194c793; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: sched/rt: Fix race in push_rt_task Overview ======== When a CPU chooses to call push_rt_task and picks a task to push to another CPU's runqueue then it will call find_lock_lowest_rq method which would take a double lock on both CPUs' runqueues. If one of the locks aren't readily available, it may lead to dropping the current runqueue lock and reacquiring both the locks at once. During this window it is possible that the task is already migrated and is running on some other CPU. These cases are already handled. However, if the task is migrated and has already been executed and another CPU is now trying to wake it up (ttwu) such that it is queued again on the runqeue (on_rq is 1) and also if the task was run by the same CPU, then the current checks will pass even though the task was migrated out and is no longer in the pushable tasks list. Crashes ======= This bug resulted in quite a few flavors of crashes triggering kernel panics with various crash signatures such as assert failures, page faults, null pointer dereferences, and queue corruption errors all coming from scheduler itself. Some of the crashes: -> kernel BUG at kernel/sched/rt.c:1616! BUG_ON(idx >= MAX_RT_PRIO) Call Trace: ? __die_body+0x1a/0x60 ? die+0x2a/0x50 ? do_trap+0x85/0x100 ? pick_next_task_rt+0x6e/0x1d0 ? do_error_trap+0x64/0xa0 ? pick_next_task_rt+0x6e/0x1d0 ? exc_invalid_op+0x4c/0x60 ? pick_next_task_rt+0x6e/0x1d0 ? asm_exc_invalid_op+0x12/0x20 ? pick_next_task_rt+0x6e/0x1d0 __schedule+0x5cb/0x790 ? update_ts_time_stats+0x55/0x70 schedule_idle+0x1e/0x40 do_idle+0x15e/0x200 cpu_startup_entry+0x19/0x20 start_secondary+0x117/0x160 secondary_startup_64_no_verify+0xb0/0xbb -> BUG: kernel NULL pointer dereference, address: 00000000000000c0 Call Trace: ? __die_body+0x1a/0x60 ? no_context+0x183/0x350 ? __warn+0x8a/0xe0 ? exc_page_fault+0x3d6/0x520 ? asm_exc_page_fault+0x1e/0x30 ? pick_next_task_rt+0xb5/0x1d0 ? pick_next_task_rt+0x8c/0x1d0 __schedule+0x583/0x7e0 ? update_ts_time_stats+0x55/0x70 schedule_idle+0x1e/0x40 do_idle+0x15e/0x200 cpu_startup_entry+0x19/0x20 start_secondary+0x117/0x160 secondary_startup_64_no_verify+0xb0/0xbb -> BUG: unable to handle page fault for address: ffff9464daea5900 kernel BUG at kernel/sched/rt.c:1861! BUG_ON(rq->cpu != task_cpu(p)) -> kernel BUG at kernel/sched/rt.c:1055! BUG_ON(!rq->nr_running) Call Trace: ? __die_body+0x1a/0x60 ? die+0x2a/0x50 ? do_trap+0x85/0x100 ? dequeue_top_rt_rq+0xa2/0xb0 ? do_error_trap+0x64/0xa0 ? dequeue_top_rt_rq+0xa2/0xb0 ? exc_invalid_op+0x4c/0x60 ? dequeue_top_rt_rq+0xa2/0xb0 ? asm_exc_invalid_op+0x12/0x20 ? dequeue_top_rt_rq+0xa2/0xb0 dequeue_rt_entity+0x1f/0x70 dequeue_task_rt+0x2d/0x70 __schedule+0x1a8/0x7e0 ? blk_finish_plug+0x25/0x40 schedule+0x3c/0xb0 futex_wait_queue_me+0xb6/0x120 futex_wait+0xd9/0x240 do_futex+0x344/0xa90 ? get_mm_exe_file+0x30/0x60 ? audit_exe_compare+0x58/0x70 ? audit_filter_rules.constprop.26+0x65e/0x1220 __x64_sys_futex+0x148/0x1f0 do_syscall_64+0x30/0x80 entry_SYSCALL_64_after_hwframe+0x62/0xc7 -> BUG: unable to handle page fault for address: ffff8cf3608bc2c0 Call Trace: ? __die_body+0x1a/0x60 ? no_context+0x183/0x350 ? spurious_kernel_fault+0x171/0x1c0 ? exc_page_fault+0x3b6/0x520 ? plist_check_list+0x15/0x40 ? plist_check_list+0x2e/0x40 ? asm_exc_page_fault+0x1e/0x30 ? _cond_resched+0x15/0x30 ? futex_wait_queue_me+0xc8/0x120 ? futex_wait+0xd9/0x240 ? try_to_wake_up+0x1b8/0x490 ? futex_wake+0x78/0x160 ? do_futex+0xcd/0xa90 ? plist_check_list+0x15/0x40 ? plist_check_list+0x2e/0x40 ? plist_del+0x6a/0xd0 ? plist_check_list+0x15/0x40 ? plist_check_list+0x2e/0x40 ? dequeue_pushable_task+0x20/0x70 ? __schedule+0x382/0x7e0 ? asm_sysvec_reschedule_i ---truncated---
- Published
- Jul 4, 2025
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-362
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.7
- CNA · Linux
- 7.8
- 3.1 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.25affected
- e8fa136262e1121288bb93befe2295928ffd240d and later · before 35b55cd665fbfd72805318f7017626eefd13dca5affected · git
- e8fa136262e1121288bb93befe2295928ffd240d and later · before 9f6022b2573ae068793810db719e131df3ded405affected · git
- e8fa136262e1121288bb93befe2295928ffd240d and later · before debfbc047196df1f6bfd52f2d028c21dce67f0deaffected · git
- e8fa136262e1121288bb93befe2295928ffd240d and later · before 07ecabfbca64f4f0b6071cf96e49d162fa9d138daffected · git
- e8fa136262e1121288bb93befe2295928ffd240d and later · before 690e47d1403e90b7f2366f03b52ed3304194c793affected · git
- before 2.6.25not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.124 and later · up to and including 6.6.*not affected · semver
- 6.12.64 and later · up to and including 6.12.*not affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 6.15.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.54.1.el8_10 | 4.18.0-553.54.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.54.1.rt7.395.el8_10 | 4.18.0-553.54.1.rt7.395.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.54.1.rt7.395.el8_10 | 4.18.0-553.54.1.rt7.395.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.54.1.rt7.395.el8_10 | 4.18.0-553.54.1.rt7.395.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.54.1.rt7.395.el8_10 | 4.18.0-553.54.1.rt7.395.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.54.1.rt7.395.el8_10 | 4.18.0-553.54.1.rt7.395.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.54.1.rt7.395.el8_10 | 4.18.0-553.54.1.rt7.395.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.54.1.rt7.395.el8_10 | 4.18.0-553.54.1.rt7.395.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.54.1.rt7.395.el8_10 | 4.18.0-553.54.1.rt7.395.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.54.1.rt7.395.el8_10 | 4.18.0-553.54.1.rt7.395.el8_10 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38231Jul 4, 2025 · nfsd: Initialize ssc before laundromat_work to prevent NULL dereference22Monitor
- ← EarlierCVE-2025-38232Jul 4, 2025 · NFSD: fix race between nfsd registration and exports_proc18Monitor
- Later →CVE-2025-38235Jul 6, 2025 · HID: appletb-kbd: fix "appletb_backlight" backlight device reference counting22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 07ecabfbca64f4f0b6071cf96e49d162fa9d138d | Vendor (CNA) |
| Linux Linux | 35b55cd665fbfd72805318f7017626eefd13dca5 | Vendor (CNA) |
| Linux Linux | 690e47d1403e90b7f2366f03b52ed3304194c793 | Vendor (CNA) |
| Linux Linux | 9f6022b2573ae068793810db719e131df3ded405 | Vendor (CNA) |
| Linux Linux | debfbc047196df1f6bfd52f2d028c21dce67f0de | Vendor (CNA) |
| cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| almalinux:bpftool | 4.18.0-553.54.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.54.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.54.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.54.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.54.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.54.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.54.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.54.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.54.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.54.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.54.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.54.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.69-1 · Debian:13 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-553.54.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-553.54.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-553.54.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-553.54.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-553.54.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-553.54.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-553.54.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-553.54.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:4.18.0-553.54.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules | 0:4.18.0-553.54.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
+14
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.