CVE-2025-37821: sched/eevdf: Fix se->slice being set to U64_MAX and resulting crash
Noroxi assessment
Priority: Monitor (action score 22/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.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 50a665496881262519f115f1bfe5822f30580eb0, 86b37810fa1e40b93171da023070b99ccbb4ea04, bbce3de72be56e4b5f68924b7da9630cc89aa1a8.
Low priority for now. Upgrade to Linux Linux 50a665496881262519f115f1bfe5822f30580eb0, 86b37810fa1e40b93171da023070b99ccbb4ea04, bbce3de72be56e4b5f68924b7da9630cc89aa1a8 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/eevdf: Fix se->slice being set to U64_MAX and resulting crash There is a code path in dequeue_entities() that can set the slice of a sched_entity to U64_MAX, which sometimes results in a crash. The offending case is when dequeue_entities() is called to dequeue a delayed group entity, and then the entity's parent's dequeue is delayed. In that case: 1. In the if (entity_is_task(se)) else block at the beginning of dequeue_entities(), slice is set to cfs_rq_min_slice(group_cfs_rq(se)). If the entity was delayed, then it has no queued tasks, so cfs_rq_min_slice() returns U64_MAX. 2. The first for_each_sched_entity() loop dequeues the entity. 3. If the entity was its parent's only child, then the next iteration tries to dequeue the parent. 4. If the parent's dequeue needs to be delayed, then it breaks from the first for_each_sched_entity() loop _without updating slice_. 5. The second for_each_sched_entity() loop sets the parent's ->slice to the saved slice, which is still U64_MAX. This throws off subsequent calculations with potentially catastrophic results. A manifestation we saw in production was: 6. In update_entity_lag(), se->slice is used to calculate limit, which ends up as a huge negative number. 7. limit is used in se->vlag = clamp(vlag, -limit, limit). Because limit is negative, vlag > limit, so se->vlag is set to the same huge negative number. 8. In place_entity(), se->vlag is scaled, which overflows and results in another huge (positive or negative) number. 9. The adjusted lag is subtracted from se->vruntime, which increases or decreases se->vruntime by a huge number. 10. pick_eevdf() calls entity_eligible()/vruntime_eligible(), which incorrectly returns false because the vruntime is so far from the other vruntimes on the queue, causing the (vruntime - cfs_rq->min_vruntime) * load calulation to overflow. 11. Nothing appears to be eligible, so pick_eevdf() returns NULL. 12. pick_next_entity() tries to dereference the return value of pick_eevdf() and crashes. Dumping the cfs_rq states from the core dumps with drgn showed tell-tale huge vruntime ranges and bogus vlag values, and I also traced se->slice being set to U64_MAX on live systems (which was usually "benign" since the rest of the runqueue needed to be in a particular state to crash). Fix it in dequeue_entities() by always setting slice from the first non-empty cfs_rq.
- Published
- May 8, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- CWE-476
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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
- 6.12affected
- aef6987d89544d63a47753cf3741cabff0b5574c and later · before 86b37810fa1e40b93171da023070b99ccbb4ea04affected · git
- aef6987d89544d63a47753cf3741cabff0b5574c and later · before 50a665496881262519f115f1bfe5822f30580eb0affected · git
- aef6987d89544d63a47753cf3741cabff0b5574c and later · before bbce3de72be56e4b5f68924b7da9630cc89aa1a8affected · git
- before 6.12not affected · semver
- 6.12.29 and later · up to and including 6.12.*not affected · semver
- 6.14.5 and later · up to and including 6.14.*not affected · semver
- 6.15 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.12 and later · before 6.12.29
- linux linux kernel6.13 and later · before 6.14.5
- linux linux kernel6.15
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.29-1 | 6.12.29-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.6.1.160000.2.4 | 6.12.0-160000.6.1.160000.2.4 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-docs | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-kvmsmall | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-obs-qa | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-syms | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-zfcpdump | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro 6.2 | kernel-64kb | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro 6.2 | kernel-default | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro 6.2 | kernel-default-base | before 6.12.0-160000.6.1.160000.2.4 | 6.12.0-160000.6.1.160000.2.4 |
| SUSE:Linux Micro 6.2 | kernel-rt | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro 6.2 | kernel-source | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro Extras 6.2 | kernel-obs-build | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
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-37818May 8, 2025 · LoongArch: Return NULL from huge_pte_offset() for invalid PMD22Monitor
- ← EarlierCVE-2025-37819May 8, 2025 · irqchip/gic-v2m: Prevent use after free of gicv2m_get_fwnode()31Monitor
- Later →CVE-2025-37825May 8, 2025 · nvmet: fix out-of-bounds access in nvmet_enable_port28Monitor
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 | 50a665496881262519f115f1bfe5822f30580eb0 | Vendor (CNA) |
| Linux Linux | 86b37810fa1e40b93171da023070b99ccbb4ea04 | Vendor (CNA) |
| Linux Linux | bbce3de72be56e4b5f68924b7da9630cc89aa1a8 | Vendor (CNA) |
| debian:linux | 6.12.29-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.6.1.160000.2.4 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-zfcpdump | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.6.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default | 6.12.0-160000.6.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.6.1.160000.2.4 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-docs | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.6.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-obs-qa | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-rt | 6.12.0-160000.6.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-source | 6.12.0-160000.6.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-syms | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-zfcpdump | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.