dpaa2-switch: Fix interrupt storm after receiving bad if_id in IRQ handler
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 31a7a0bbeb006bac2d9c81a2874825025214b6d8 · < 28fd8ac1d49389cb230d712116f54e27ebec11b8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dpaa2-switch: Fix interrupt storm after receiving bad if_id in IRQ handler
Commit 31a7a0bbeb00 ("dpaa2-switch: add bounds check for if_id in IRQ handler") introduces a range check for if_id to avoid an out-of-bounds access. If an out-of-bounds if_id is detected, the interrupt status is not cleared. This may result in an interrupt storm.
Clear the interrupt status after detecting an out-of-bounds if_id to avoid the problem.
Found by an experimental AI code review agent at Google.
From the CVE record · Linux
The dpaa2-switch IRQ handler can leave interrupt status uncleared when it receives an out-of-bounds if_id, potentially causing an interrupt storm. The input does not establish how an attacker could trigger this condition or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with dpaa2-switch should check their versions; affected versions are not specified.