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-23180dpaa2-switch: add bounds check for if_id in IRQ handler

Description

In the Linux kernel, the following vulnerability has been resolved: dpaa2-switch: add bounds check for if_id in IRQ handler The IRQ handler extracts if_id from the upper 16 bits of the hardware status register and uses it to index into ethsw->ports[] without validation. Since if_id can be any 16-bit value (0-65535) but the ports array is only allocated with sw_attr.num_ifs elements, this can lead to an out-of-bounds read potentially. Add a bounds check before accessing the array, consistent with the existing validation in dpaa2_switch_rx().

Timeline

  1. ID reserved

    By Linux

  2. · 32 days later

    Published

  3. · 8 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-23180, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 – < 77611cab5bdfff7a070ae574bbfba20a1de99d1b
    • affected 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 – < 34b56c16efd61325d80bf1d780d0e176be662f59
    • affected 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 – < f89e33c9c37f0001b730e23b3b05ab7b1ecface2
    • affected 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 – < 2447edc367800ba914acf7ddd5d250416b45fb31
    • affected 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 – < 1b381a638e1851d8cfdfe08ed9cdbec5295b18c9
    • affected 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 – < 31a7a0bbeb006bac2d9c81a2874825025214b6d8
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.200 – ≤ 5.15.*
    • unaffected 6.1.163 – ≤ 6.1.*
    • unaffected 6.6.124 – ≤ 6.6.*
    • unaffected 6.12.70 – ≤ 6.12.*
    • unaffected 6.18.10 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .