CVE-2025-39902
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.1 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Modified
Affected
- Linux Kernel < 5.4.299
- Linux Kernel < 5.10.243
- Linux Kernel < 5.15.192
- Linux Kernel < 6.1.151
- Linux Kernel < 6.6.105
- Linux Kernel < 6.12.46
- Linux Kernel < 6.16.6
- Linux Kernel 6.17
Attack profile CVSS 3.1 · 7.1
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-39902.md and follow it. Check whether this project is affected by CVE-2025-39902. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0ef7058b4dc6fcef622ac23b45225db57f17b83f
- https://git.kernel.org/stable/c/1f0797f17927b5cad0fb7eced422f9a7c30a3191
- https://git.kernel.org/stable/c/3baa1da473e6e50281324ff1d332d1a07a3bb02e
- https://git.kernel.org/stable/c/7e287256904ee796c9477e3ec92b07f236481ef3
- https://git.kernel.org/stable/c/872f2c34ff232af1e65ad2df86d61163c8ffad42
- https://git.kernel.org/stable/c/b4efccec8d06ceb10a7d34d7b1c449c569d53770
- https://git.kernel.org/stable/c/dda6ec365ab04067adae40ef17015db447e90736
- https://git.kernel.org/stable/c/f66012909e7bf383fcdc5850709ed5716073fdc4
References
- https://git.kernel.org/stable/c/0ef7058b4dc6fcef622ac23b45225db57f17b83f
- https://git.kernel.org/stable/c/1f0797f17927b5cad0fb7eced422f9a7c30a3191
- https://git.kernel.org/stable/c/3baa1da473e6e50281324ff1d332d1a07a3bb02e
- https://git.kernel.org/stable/c/7e287256904ee796c9477e3ec92b07f236481ef3
- https://git.kernel.org/stable/c/872f2c34ff232af1e65ad2df86d61163c8ffad42
- https://git.kernel.org/stable/c/b4efccec8d06ceb10a7d34d7b1c449c569d53770
- https://git.kernel.org/stable/c/dda6ec365ab04067adae40ef17015db447e90736
- https://git.kernel.org/stable/c/f66012909e7bf383fcdc5850709ed5716073fdc4
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html