CVE-2025-38113
BaseFortify
Publication date: 2025-07-03
Last updated on: 2025-12-17
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.19 (inc) to 6.1.142 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.94 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.34 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.15.3 (exc) |
| linux | linux_kernel | 6.16 |
| debian | debian_linux | 11.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's ACPI CPPC component when the 'nosmp' kernel command line option is used. With 'nosmp', other CPUs are not started, leaving their cpc_desc_ptr pointers NULL. However, CPU0 still iterates over all possible CPUs and dereferences these NULL pointers, causing a kernel panic due to a NULL pointer dereference.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to panic and crash when the 'nosmp' option is used, leading to system instability and potential downtime. The kernel panic occurs because of a NULL pointer dereference, which can halt system operation and require a reboot.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel panic messages related to NULL pointer dereference when the 'nosmp' kernel command line parameter is used. Specifically, look for panic logs containing messages like 'Unable to handle kernel NULL pointer dereference at virtual address 00000000000000b8' and backtrace entries referencing 'cppc_allow_fast_switch'. You can check the kernel logs using commands such as 'dmesg | grep -i panic' or 'journalctl -k | grep -i panic' to find relevant panic messages.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, avoid using the 'nosmp' kernel command line parameter, as it causes other CPUs not to be brought up and leads to NULL pointer dereference. Updating the Linux kernel to a version where this issue is fixed is also recommended.