CVE-2025-38068: crypto: lzo - Fix compression buffer overrun
In the Linux kernel, the following vulnerability has been resolved:
crypto: lzo - Fix compression buffer overrun
Unlike the decompression code, the compression code in LZO never checked for output overruns. It instead assumes that the caller always provides enough buffer space, disregarding the buffer length provided by the caller.
Add a safe compression interface that checks for the end of buffer before each write. Use the safe interface in crypto/lzo.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38068?
CVE-2025-38068 is classified as a moderate severity vulnerability in the Linux kernel.
How do I fix CVE-2025-38068?
To fix CVE-2025-38068, upgrade to the patched version of the Linux kernel that addresses this vulnerability.
What is the impact of CVE-2025-38068?
CVE-2025-38068 can lead to potential buffer overrun issues during compression, which may compromise system stability.
Which versions of the Linux kernel are affected by CVE-2025-38068?
CVE-2025-38068 affects versions of the Linux kernel prior to the implementation of the fix for this vulnerability.
Is CVE-2025-38068 exploitable in a production environment?
Yes, CVE-2025-38068 can be exploitable in a production environment if the affected software is used without the necessary updates.