VulnerabilityPublished 3 Apr 2026Updated 5 Nov 2026

CVE-2026-23447: Linux kernel · net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check

Affects Linux kernelSource CVE Database V5

Compare

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

Data as of 5 Nov 2026, 22:04 UTC

Severity

Unrated

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

Thin evidence

One scorer or none

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 de70da1fb1d152e981ecb3157f7ec2b633005c16, baf246d6680befde2086b1df9eb3aaba3fb6853f, af0d1613d6751489dbf9f69aac1123f0b1e566e5 +6

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=4.14.317 <4.15 >=4.19.285 <4.20 >=5.4.245 <5.5	Fixed in de70da1fb1d152e981ecb3157f7ec2b633005c16 baf246d6680befde2086b1df9eb3aaba3fb6853f af0d1613d6751489dbf9f69aac1123f0b1e566e5 a5bd5a2710310c965ea4153cba4210988a3454e2 77914255155e68a20aa41175edeecf8121dac391 125f932a76a97904ef8a555f1dd53e5d0e288c54 5.5 4.20 4.15
LinuxLinux	Affected =5.7	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check The same bounds-check bug fixed for NDP16 in the previous patch also exists in cdc_ncm_rx_verify_ndp32(). The DPE array size is validated against the total skb length without accounting for ndpoffset, allowing out-of-bounds reads when the NDP32 is placed near the end of the NTB. Add ndpoffset to the nframes bounds check and use struct_size_t() to express the NDP-plus-DPE-array size more clearly. Compile-tested only.

References

Community reviews

Loading reviews…