CVE-2025-37908: mm, slab: clean up slab->obj_exts always
Noroxi assessment
Priority: Monitor (action score 31/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.20% (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 01db0e1a48345aa1937f3bdfc7c7108d03ebcf7e, be8250786ca94952a19ce87f98ad9906448bc9ef, dab2a13059a475b6392550f882276e170fe2fcff.
Low priority for now. Upgrade to Linux Linux 01db0e1a48345aa1937f3bdfc7c7108d03ebcf7e, be8250786ca94952a19ce87f98ad9906448bc9ef, dab2a13059a475b6392550f882276e170fe2fcff 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: mm, slab: clean up slab->obj_exts always When memory allocation profiling is disabled at runtime or due to an error, shutdown_mem_profiling() is called: slab->obj_exts which previously allocated remains. It won't be cleared by unaccount_slab() because of mem_alloc_profiling_enabled() not true. It's incorrect, slab->obj_exts should always be cleaned up in unaccount_slab() to avoid following error: [...]BUG: Bad page state in process... .. [...]page dumped because: page still charged to cgroup [andriy.shevchenko@linux.intel.com: fold need_slab_obj_ext() into its only user]
- Published
- May 20, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-459
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.10 and later · before 6.12.28
- linux linux kernel6.13 and later · before 6.14.6
- linux linux kernel6.15
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.10affected
- 21c690a349baab895dc68ab70d291e1598d7109d and later · before dab2a13059a475b6392550f882276e170fe2fcffaffected · git
- 21c690a349baab895dc68ab70d291e1598d7109d and later · before 01db0e1a48345aa1937f3bdfc7c7108d03ebcf7eaffected · git
- 21c690a349baab895dc68ab70d291e1598d7109d and later · before be8250786ca94952a19ce87f98ad9906448bc9efaffected · git
- before 6.10not affected · semver
- 6.12.28 and later · up to and including 6.12.*not affected · semver
- 6.14.6 and later · up to and including 6.14.*not affected · semver
- 6.15 and laternot affected · original_commit_for_fix
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 |
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-37904May 20, 2025 · btrfs: fix the inode leak in btrfs_iget()22Monitor
- ← EarlierCVE-2025-37905May 20, 2025 · firmware: arm_scmi: Balance device refcount when destroying devices22Monitor
- Later →CVE-2025-37910May 20, 2025 · ptp: ocp: Fix NULL dereference in Adva board SMA sysfs operations22Monitor
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 | 01db0e1a48345aa1937f3bdfc7c7108d03ebcf7e | Vendor (CNA) |
| Linux Linux | be8250786ca94952a19ce87f98ad9906448bc9ef | Vendor (CNA) |
| Linux Linux | dab2a13059a475b6392550f882276e170fe2fcff | Vendor (CNA) |
| debian:linux | 6.12.29-1 · Debian:13 | 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-31668339 days apartseg6: separate dst_cache for input and output paths in seg6 lwtunnel39Monitor
- CVE-2021-47110431 days apartx86/kvm: Disable kvmclock on all CPUs on shutdown28Monitor
- CVE-2024-47693211 days apartIB/core: Fix ib_cache_setup_one error flow cleanup26Monitor
- CVE-2025-3817745 days apartsch_hfsc: make hfsc_qlen_notify() idempotent22Monitor
- CVE-2025-2192449 days apartnet: hns3: make sure ptp clock is unregister and freed if hclge_ptp_get_cycle returns an error22Monitor
- CVE-2023-5292954 days apartnvmem: core: fix cleanup after dev_set_name()22Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-459 · Incomplete CleanupCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
- 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.