crypto: caam - fix overflow on long hmac keys
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: caam - fix overflow on long hmac keys
When a key longer than block size is supplied, it is copied and then hashed into the real key. The memory allocated for the copy needs to be rounded to DMA cache alignment, as otherwise the hashed key may corrupt neighbouring memory.
The copying is performed using kmemdup, however this leads to an overflow: reading more bytes (aligned_len - keylen) from the keylen source buffer. Fix this by replacing kmemdup with kmalloc, followed by memcpy.
From the CVE record · Linux
The Linux kernel CAAM crypto code has an overflow when handling an HMAC key longer than the block size. Copying the key can read beyond the source buffer, and processing the hashed key may corrupt neighboring memory. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with the CAAM crypto component should check whether their kernel includes the fix; affected versions are not specified.