LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23206: dpaa2-switch: prevent ZERO_SIZE_PTR dereference when num_ifs is zero

In the Linux kernel, the following vulnerability has been resolved: dpaa2-switch: prevent ZERO_SIZE_PTR dereference when num_ifs is zero The driver allocates arrays for ports, FDBs, and filter blocks using kcalloc() with ethsw->sw_attr.num_ifs as the element count. When the device reports zero interfaces (either due to hardware configuration or firmware issues), kcalloc(0, ...) returns ZERO_SIZE_PTR (0x10) instead of NULL. Later in dpaa2_switch_probe(), the NAPI initialization unconditionally accesses ethsw->ports[0]->netdev, which attempts to dereference ZERO_SIZE_PTR (address 0x10), resulting in a kernel panic. Add a check to ensure num_ifs is greater than zero after retrieving device attributes. This prevents the zero-sized allocations and subsequent invalid pointer dereference.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel crash bug in the dpaa2-switch driver. If a device reports zero interfaces, the driver can still try to use the first port and dereference an invalid pointer, causing a kernel panic. The public record does not provide a CVSS score or evidence of active exploitation.

Executive priority

Treat this as a targeted availability risk, not a broadly proven internet-exploited issue. Prioritize patching where dpaa2-switch is present or business services depend on affected Linux hosts. Broader urgency depends on asset exposure and vendor kernel advisories.

Technical view

The driver allocates port, FDB, and filter-block arrays using num_ifs. With num_ifs equal to zero, kcalloc returns ZERO_SIZE_PTR rather than NULL. dpaa2_switch_probe later accesses ethsw->ports[0]->netdev, dereferencing address 0x10 and panicking. Stable fixes add a post-attribute check requiring num_ifs greater than zero.

Likely exposure

Exposure appears limited to Linux systems using the affected dpaa2-switch driver and device or firmware states that can report zero interfaces. The source lists affected Linux kernel versions and stable fixes, but does not describe remote reachability or default deployment prevalence.

Exploitation context

The provided sources describe a crash condition triggered by a zero-interface device attribute. They do not state active exploitation, public exploit availability, privilege requirements, or remote attackability. KEV status is false in the source bundle.

Researcher notes

Evidence supports a NULL-like invalid pointer dereference via ZERO_SIZE_PTR when num_ifs is zero. The record lacks CVSS, CWE, exploitability analysis, and attack preconditions. Avoid assuming remote exploitability; validate through source, kernel configuration, device presence, and stable patch lineage.

Mitigation direction

  • Update to a kernel containing the referenced stable dpaa2-switch fixes.
  • Check Linux distribution advisories for packaged kernel availability and backports.
  • Prioritize systems using dpaa2-switch hardware or firmware configurations.
  • If unable to update, review vendor guidance for safe operational workarounds.

Validation and detection

  • Inventory Linux systems for dpaa2-switch driver usage and relevant hardware.
  • Compare running kernel builds against distribution advisories and referenced stable commits.
  • Review boot and kernel logs for dpaa2-switch probe failures or panics.
  • Confirm updated kernels include a num_ifs greater-than-zero check.
Prepared
Confidence
medium
Sources
8

Public sources used

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-23206 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0b1b71370458860579831e77485883fcf2e8fbbe, 0b1b71370458860579831e77485883fcf2e8fbbe, 0b1b71370458860579831e77485883fcf2e8fbbe, 0b1b71370458860579831e77485883fcf2e8fbbe, 0b1b71370458860579831e77485883fcf2e8fbbe, 0b1b71370458860579831e77485883fcf2e8fbbeunaffected
LinuxLinux5.13, 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.