CVE-2025-38068
BaseFortify
Publication date: 2025-06-18
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 | to 5.15.185 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.141 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.93 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.31 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.14.9 (exc) |
| debian | debian_linux | 11.0 |
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 buffer overrun issue in the Linux kernel's crypto LZO compression code. Unlike the decompression code, the compression code did not check if the output buffer was large enough before writing data, assuming the caller always provided sufficient space. This could lead to writing beyond the allocated buffer. The fix involved adding a safe compression interface that checks the buffer boundaries before each write.
How can this vulnerability impact me? :
The vulnerability could lead to a buffer overrun during compression, which may cause memory corruption, crashes, or potentially allow an attacker to execute arbitrary code or cause denial of service by exploiting the unchecked buffer writes.
What immediate steps should I take to mitigate this vulnerability?
Update the Linux kernel to a version that includes the fix for the LZO compression buffer overrun vulnerability. The fix involves using a safe compression interface that checks buffer boundaries to prevent overruns.