crypto: lzo - Fix compression buffer overrun
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 64c70b1cf43de158282bc1675918d503e5b15cc1 · < cc47f07234f72cbd8e2c973cdbf2a6730660a463| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s crypto/lzo compression code does not check whether its output buffer is large enough. When the caller provides an insufficient buffer, compression can write past its end. The input does not specify how an attacker could trigger this or whether authentication or user interaction is required.
Engineers running the Linux kernel should check their versions; the affected versions are not specified.