LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23180: dpaa2-switch: add bounds check for if_id in IRQ handler

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().

HighCVSS 7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux network-switch driver can trust an invalid hardware interface identifier and read beyond an internal ports array during interrupt processing. Systems using the DPAA2 switch driver may crash or expose adjacent kernel memory. The supplied assessment rates it high severity, but exploitation requires local access, privileges, and difficult conditions.

Executive priority

Treat as a targeted high-priority kernel update for DPAA2-based networking systems, not an estate-wide emergency. Inventory affected appliances and hosts promptly, then patch through supported vendor channels. Escalate systems allowing untrusted local users or providing critical network services. No active exploitation is established by the supplied evidence.

Technical view

The dpaa2-switch IRQ handler extracts a 16-bit if_id from a hardware status register and indexes ethsw->ports[] without confirming it is below sw_attr.num_ifs. Values up to 65535 can therefore cause an out-of-bounds read in kernel interrupt context. The stable fixes add the missing bounds check, matching existing receive-path validation.

Likely exposure

Exposure is limited to Linux systems running an affected kernel with the DPAA2 switch driver and relevant hardware active. The supplied record lists affected versions across several stable branches, but its version data is insufficient to define every vulnerable build reliably. General Linux installations without this driver or hardware are unlikely to be exposed.

Exploitation context

The CVSS vector indicates a local, low-privilege, high-complexity path without user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. Although the CVSS impact metrics are high, the description specifically establishes only a potential out-of-bounds read.

Researcher notes

The fix checks if_id before ethsw->ports[] access in interrupt context. The source bundle repeats one hash and provides ambiguous affected-version boundaries, so distribution-specific backport status must be verified. Do not infer exploitability beyond the documented potential read; the bundle contains no crash trace, proof of concept, root-cause reachability analysis, or demonstrated confidentiality, integrity, or availability outcome.

Mitigation direction

  • Identify systems using the DPAA2 switch driver and affected kernel branches.
  • Install a vendor-supported kernel containing the applicable upstream stable fix.
  • Prioritize exposed multi-user or appliance systems where local access is less controlled.
  • If immediate updating is impossible, consult vendor guidance about safely disabling unused DPAA2 switch functionality.

Validation and detection

  • Record each system's kernel build, distribution, hardware platform, and loaded driver state.
  • Confirm whether the dpaa2-switch driver and relevant DPAA2 switch hardware are active.
  • Compare vendor kernel changelogs against CVE-2026-23180 or the supplied stable commits.
  • After updating, verify the running kernel includes the bounds-check fix.
  • Monitor kernel logs for DPAA2 switch faults or unexplained crashes.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23180 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H15.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7High
CVSS 3.1 vector shape for CVE-2026-23180Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux24ab724f8a4661b2dc8e696b41df93bdc108f7a1, 24ab724f8a4661b2dc8e696b41df93bdc108f7a1, 24ab724f8a4661b2dc8e696b41df93bdc108f7a1, 24ab724f8a4661b2dc8e696b41df93bdc108f7a1, 24ab724f8a4661b2dc8e696b41df93bdc108f7a1, 24ab724f8a4661b2dc8e696b41df93bdc108f7a1unaffected
LinuxLinux5.15, 0, 5.15.200, 6.1.163, 6.6.124, 6.12.70, 6.18.10, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.