Linux kernel out-of-bounds read in nvmem cell bit offsets
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvmem: core: Fix OOB read for bit offsets of more than one byte
When the bit offset is BITS_PER_BYTE or larger the read position is advanced by `bytes_offset`. This is not taken into account in the per-byte read loop which still reads `cell->bytes` resulting in an out of bounds read of `bytes_offset` bytes. The information read OOB does not leak directly as the erroneously read bits are cleared.
Detected by KASAN while looking for a use-after-free in simplefb.c.
From the CVE record · Linux
The Linux kernel's nvmem core can read beyond a cell's bounds when its bit offset is at least one byte. The erroneously read bits are cleared, so the information does not leak directly. The input does not establish whether an attacker can trigger this condition or whether access or user interaction is required.
Engineers running the Linux kernel should check their versions; affected versions are not specified in the input.