CVE-2025-39809
BaseFortify
Publication date: 2025-09-16
Last updated on: 2025-12-02
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.14 (inc) to 6.16.5 (exc) |
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | 6.17 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a stack-out-of-bounds error in the Linux kernel's intel-quicki2c driver related to ACPI _DSD methods. The _DSD methods return ICRS and ISUB data with an extra trailing byte, making the data length one byte longer than the defined structures. This mismatch causes the kernel to write beyond the allocated stack buffer, leading to a stack-out-of-bounds condition and a kernel crash.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash due to a stack-out-of-bounds write, which may lead to system instability or denial of service. The kernel crash occurs when the intel-quicki2c driver processes ACPI data with incorrect length, potentially affecting system reliability.
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 specific KASAN (Kernel Address Sanitizer) stack-out-of-bounds errors related to the intel_quicki2c driver. You can check the kernel log for messages similar to: 'BUG: KASAN: stack-out-of-bounds in quicki2c_acpi_get_dsd_property'. Commands to detect this include: 'dmesg | grep -i quicki2c' or 'journalctl -k | grep -i quicki2c'. These commands help identify if the kernel has logged any crashes or memory errors related to this vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Linux kernel to a version where this vulnerability is fixed, as the issue has been resolved by adding reserved padding to quicki2c_subip_acpi_parameter/config. Until an update is applied, monitoring for kernel crashes and avoiding workloads that trigger the intel_quicki2c ACPI _DSD methods may reduce risk. There are no specific configuration changes or patches mentioned other than applying the fixed kernel version.