Cloudanix VulnDB

CVE-2026-23422

High · 7.8

CVSS

7.8

EPSS

0.1%

Published

Apr 3, 2026

CISA due date

—

Cloudanix analysis

Next patch cycle SSVC: Track

A flaw in Linux network hardware handling can make the computer keep responding to the same event over and over, slowing or freezing the system.

Exploitation
Local Privilege
Attacker needs
Low Privilege
Complexity
Low
Impact
Denial Of Service
Component
OS kernel
Class
Memory Corruption
Remediation
Patch
Effort
Low
Patch risk
Low

What it actually does

Failure to clear the interrupt status after an out-of-bounds if_id check in the dpaa2-switch IRQ handler allows the hardware to continuously reassert the same interrupt, producing an interrupt storm.

Why it matters to the business

Systems using the affected Linux kernel driver can experience sustained high CPU usage and loss of responsiveness, disrupting network traffic processing on dpaa2 hardware.

How an attack unfolds

An attacker supplies or triggers an IRQ event containing an invalid if_id; the bounds check detects the error but leaves the interrupt pending, causing the handler to be invoked repeatedly without progress.

How to fix it

Apply the upstream fix that clears the interrupt status register immediately after detecting an out-of-bounds if_id; rebuild and deploy an updated Linux kernel containing commit 31a7a0bbeb00 on all affected systems.

How to confirm the fix worked

Inspect the dpaa2-switch IRQ handler source to confirm that an out-of-bounds if_id path now executes the interrupt-acknowledge write before returning.

Typical attack path

  1. Obtain local access or control over the dpaa2 network interface
  2. Generate an IRQ with an out-of-bounds if_id value
  3. Trigger repeated interrupt delivery without status clear
  4. Induce CPU saturation and service degradation

How to detect it

Review kernel logs and performance counters for sustained high rates of dpaa2-switch interrupts without corresponding packet processing; correlate with any recent interface configuration changes.

What your security team should do

  • Prioritize kernel update on any host exposing dpaa2-switch hardware
  • Temporarily disable the interface or reduce interrupt affinity if an immediate update is not feasible
  • Add monitoring for elevated interrupt counts on dpaa2 devices

The record

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.

Affected packages

Ecosystem Package Introduced Fixed

Related vulnerabilities