Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23422dpaa2-switch: Fix interrupt storm after receiving bad if_id in IRQ handler

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23422, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 77611cab5bdfff7a070ae574bbfba20a1de99d1b – < 7def51cb9fb8b8d5342443372b8cf28d8fbd7f3d
    • affected 34b56c16efd61325d80bf1d780d0e176be662f59 – < b5bababe7703a7322bc59b803ab1587887a2a5e4
    • affected f89e33c9c37f0001b730e23b3b05ab7b1ecface2 – < c7becfe3e604d138bd53b8ac3111b2b3e8ec6b0e
    • affected 2447edc367800ba914acf7ddd5d250416b45fb31 – < fa4412cdc5178a48799bafcb8af28fd2fbf3d703
    • affected 1b381a638e1851d8cfdfe08ed9cdbec5295b18c9 – < 00f42ace446f1e4bf84988f2281131f52cd32796
    • affected 31a7a0bbeb006bac2d9c81a2874825025214b6d8 – < 28fd8ac1d49389cb230d712116f54e27ebec11b8
    • affected 31a7a0bbeb006bac2d9c81a2874825025214b6d8 – < 74badb9c20b1a9c02a95c735c6d3cd6121679c93
    • affected 5.15.200 – < 5.15.203
    • affected 6.1.163 – < 6.1.167
    • affected 6.6.124 – < 6.6.130
    • affected 6.12.70 – < 6.12.77
    • affected 6.18.10 – < 6.18.17
  • Linux · Linux

    • affected 6.19
    • unaffected < 6.19
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.77 – ≤ 6.12.*
    • unaffected 6.18.17 – ≤ 6.18.*
    • unaffected 6.19.7 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23422 badge
[![CVE-2026-23422](https://cveledger.app/badge/CVE-2026-23422.svg)](https://cveledger.app/cve/CVE-2026-23422)

Record last updated .