CVE-2025-39902
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-01

Last updated on: 2025-11-03

Assigner: kernel.org

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-01
Last Modified
2025-11-03
Generated
2026-05-07
AI Q&A
2025-10-01
EPSS Evaluated
2026-05-05
NVD
CVE-2025-39902
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
linux linux_kernel 6.1.153-1
linux linux_kernel 5.10.244-1
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability occurs in the Linux kernel's memory management subsystem (mm/slub). Specifically, the function object_err() attempts to access metadata of an object pointer for debugging purposes. If the pointer is invalid or corrupted, accessing this metadata can cause the kernel to crash. The issue arises when alloc_consistency_checks() detects a corrupted freelist pointer and calls object_err() to report it, but object_err() does not handle invalid pointers safely, leading to a crash. The fix ensures that if the pointer is NULL or invalid, object_err() only prints the pointer value without accessing metadata, preventing the crash.


How can this vulnerability impact me? :

This vulnerability can cause the Linux kernel to crash when it tries to access invalid object metadata during debugging of memory allocation issues. Such crashes can lead to system instability, unexpected reboots, or denial of service, impacting the availability and reliability of systems running vulnerable kernel versions.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart