CVE-2026-23422: dpaa2-switch: Fix interrupt storm after receiving bad if_id in IRQ handler
In the Linux kernel, the following vulnerability has been resolved:
dpaa2-switch: Fix interrupt storm after receiving bad ifid in IRQ handler
Commit 31a7a0bbeb00 ("dpaa2-switch: add bounds check for ifid in IRQ handler") introduces a range check for ifid to avoid an out-of-bounds access. If an out-of-bounds ifid 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 ifid to avoid the problem.
Found by an experimental AI code review agent at Google.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1 - Compensating control
In the dpaa2-switch IRQ handler, clear the interrupt status when an out-of-bounds if_id is detected to prevent an interrupt storm.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
The issue affects Linux kernel deployments using the dpaa2-switch driver. The failure condition occurs when its IRQ handler receives an out-of-bounds interface identifier (if_id).
What is the operational impact if the condition is triggered?
The interrupt status may remain uncleared after an invalid if_id is detected. This can cause an interrupt storm, potentially affecting system availability.
How can administrators identify a potentially affected system?
Investigate systems using dpaa2-switch that exhibit an interrupt storm, particularly where driver handling reports or encounters an out-of-bounds if_id. The provided fix clears interrupt status when that invalid identifier is detected.