octeontx2-af: fix out-of-bounds read setting MSI-X irq affinity
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
octeontx2-af: fix out-of-bounds read setting MSI-X irq affinity
rvu_register_interrupts() walks every MSI-X vector and uses strstr() to match "Mbox" or "FLR" in irq_name before pinning those interrupts to CPU 0. irq_name is a per-vector NAME_SIZE buffer, but not every slot is populated before this loop runs. strstr() keeps scanning until it finds a NUL terminator, so an uninitialized slot can trigger a KASAN slab-out-of-bounds read at boot when debug options are enabled.
Use strnstr() with NAME_SIZE to bound the search within each vector's name buffer.
From the CVE record · Linux
The Linux kernel's octeontx2-af driver can read beyond an MSI-X interrupt-name buffer when an uninitialized slot is searched. This can trigger a KASAN report at boot when debug options are enabled; the input does not describe an attacker path or access requirements.
Engineers running Linux kernels with the octeontx2-af driver should check their versions; affected versions are not specified.