CVE-2025-40244
BaseFortify
Publication date: 2025-12-04
Last updated on: 2025-12-04
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an uninitialized value issue in the Linux kernel's HFS+ filesystem code, specifically in the function __hfsplus_ext_cache_extent(). It was detected by the Kernel Memory Sanitizer (KMSAN) which found that some memory was used before being initialized, potentially leading to undefined behavior or kernel panic.
How can this vulnerability impact me? :
The vulnerability can cause kernel panics or instability when the affected HFS+ filesystem code is executed. This could lead to system crashes or denial of service, affecting system reliability and availability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel logs for KMSAN (Kernel Memory Sanitizer) uninitialized value warnings related to the __hfsplus_ext_cache_extent function. Look for kernel messages similar to 'BUG: KMSAN: uninit-value in __hfsplus_ext_cache_extent'. You can check the kernel log using commands like 'dmesg | grep KMSAN' or 'journalctl -k | grep KMSAN'.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Linux kernel to a version where the hfsplus KMSAN uninitialized value issue in __hfsplus_ext_cache_extent() has been fixed. Until then, avoid using the hfsplus filesystem or disable it if possible to prevent triggering the vulnerable code path.