Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ed48a84a72fefb20a82dd90a7caa7807e90c6f66 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:49 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in ed48a84a72fefb20a82dd90a7caa7807e90c6f66, b97415c4362f739e25ec6f71012277086fabdf6f, 80165ff16051448d6f840585ebe13f2400415df3 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 0b1b71370458860579831e77485883fcf2e8fbbe, < ed48a84a72fefb20a82dd90a7caa7807e90c6f66
Fixed in
  • ed48a84a72fefb20a82dd90a7caa7807e90c6f66
LinuxLinuxAffected
  • ≥ 0b1b71370458860579831e77485883fcf2e8fbbe, < b97415c4362f739e25ec6f71012277086fabdf6f
Fixed in
  • b97415c4362f739e25ec6f71012277086fabdf6f
LinuxLinuxAffected
  • ≥ 0b1b71370458860579831e77485883fcf2e8fbbe, < 80165ff16051448d6f840585ebe13f2400415df3
Fixed in
  • 80165ff16051448d6f840585ebe13f2400415df3
LinuxLinuxAffected
  • ≥ 0b1b71370458860579831e77485883fcf2e8fbbe, < 155eb99aff2920153bf21217ae29565fff81e6af
Fixed in
  • 155eb99aff2920153bf21217ae29565fff81e6af
LinuxLinuxAffected
  • ≥ 0b1b71370458860579831e77485883fcf2e8fbbe, < 4acc40db06ffd0fd92683505342b00c8a7394c60
Fixed in
  • 4acc40db06ffd0fd92683505342b00c8a7394c60
LinuxLinuxAffected
  • ≥ 0b1b71370458860579831e77485883fcf2e8fbbe, < 2fcccca88456b592bd668db13aa1d29ed257ca2b
Fixed in
  • 2fcccca88456b592bd668db13aa1d29ed257ca2b

Description

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.

References

Community reviews

Loading reviews…