CVE-2025-37908: mm, slab: clean up slab->obj_exts always
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]
Security readout for executives and security teams
Plain-English summary
A Linux kernel memory-accounting cleanup flaw can leave slab metadata attached after allocation profiling shuts down. This may produce a bad page state and leave memory charged to a control group. Exploitation requires local, low-privileged access according to CVSS, but successful abuse could seriously affect system security and availability.
Executive priority
Prioritize affected multi-user, shared-hosting, and locally accessible systems. Treat remediation as high priority because the stated impact is severe, although exploitation is local and active exploitation is not evidenced. Use normal emergency kernel-change controls where outages from rebooting could create greater immediate risk.
Technical view
When allocation profiling is disabled at runtime or fails, shutdown_mem_profiling() can leave previously allocated slab->obj_exts. Because unaccount_slab() conditionally skipped cleanup when profiling was inactive, stale metadata could trigger bad-page-state detection and lingering cgroup charges. The cited kernel changes make cleanup unconditional.
Likely exposure
Potentially exposed systems run an affected Linux kernel and encounter allocation-profiling shutdown after slab object extensions were allocated. The bundle identifies Linux kernel versions including 6.10, 6.12.28, 6.14.6, and 6.15, but its version-range semantics are incomplete; confirm exposure through distribution advisories and backport records.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. The supplied record is not marked as CISA KEV, and the cited sources provide no evidence of active exploitation or a public exploit. The precise practical path from the accounting error to confidentiality or integrity impact is not documented here.
Researcher notes
The failure condition depends on retained slab object-extension metadata after profiling shutdown and conditional cleanup in unaccount_slab(). The record provides no CWE, proof of concept, exploitation telemetry, or detailed affected-version ranges. Researchers should correlate stable-tree commits with distribution patches and avoid inferring exploitability solely from the CVSS impact ratings.
Mitigation direction
Install the vendor-supported kernel update containing the applicable cited stable fix.
Confirm distribution backports rather than relying only on the displayed kernel version.
If updating is delayed, review vendor guidance for supported temporary mitigations.
Restrict unnecessary local account and workload access on potentially affected hosts.
Validation and detection
Inventory running kernel versions across hosts, virtual machines, containers, and appliances.
Check vendor advisories and package changelogs for CVE-2025-37908 or the cited fix commits.
Determine whether memory allocation profiling is enabled or may shut down after errors.
Review kernel logs for bad page state or pages remaining charged to cgroups.
After updating, verify the fixed kernel is running and repeat relevant stability testing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-37908 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.