Answer in brief
CVE-2025-39902 records a High severity (CVSS 7.1) vulnerability in mm/slub: avoid accessing metadata when pointer is invalid in object_err(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.17:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.17:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.17:rc4:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <872f2c34ff232af1e65ad2df86d61163c8ffad42 || >=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <f66012909e7bf383fcdc5850709ed5716073fdc4 || >=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <7e287256904ee796c9477e3ec92b07f236481ef3 || >=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <1f0797f17927b5cad0fb7eced422f9a7c30a3191 || >=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <0ef7058b4dc6fcef622ac23b45225db57f17b83f || >=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <dda6ec365ab04067adae40ef17015db447e90736 || >=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <3baa1da473e6e50281324ff1d332d1a07a3bb02e || >=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <b4efccec8d06ceb10a7d34d7b1c449c569d53770 | 872f2c34ff232af1e65ad2df86d61163c8ffad42, f66012909e7bf383fcdc5850709ed5716073fdc4, 7e287256904ee796c9477e3ec92b07f236481ef3, 1f0797f17927b5cad0fb7eced422f9a7c30a3191, 0ef7058b4dc6fcef622ac23b45225db57f17b83f, dda6ec365ab04067adae40ef17015db447e90736, 3baa1da473e6e50281324ff1d332d1a07a3bb02e, b4efccec8d06ceb10a7d34d7b1c449c569d53770 |
| Linux/Linuxgeneric | 2.6.22 | Not reported |
Published upstream
Oct 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: mm/slub: avoid accessing metadata when pointer is invalid in object_err() object_err() reports details of an object for further debugging, such as the freelist pointer, redzone, etc. However, if the pointer is invalid, attempting to access object metadata can lead to a crash since it does not point to a valid object. One known path to the crash is when alloc_consistency_checks() determines the pointer to the allocated object is invalid because of a freelist corruption, and calls object_err() to report it. The debug code should report and handle the corruption gracefully and not crash in the process. In case the pointer is NULL or check_valid_pointer() returns false for the pointer, only print the pointer value and skip accessing metadata.
Quoted source text, attributed separately from HOL analysis.