CVE-2026-23447
Medium
Elevated severity or exploit probability.
CVSS base
7.8
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS — probability of exploitation (30 days)
0.1%
3.0th percentile
CISA KEV
Not listed
Weakness / dates
CWE-129
Published 2026-04-03 · modified 2026-09-14
CVSS breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
| Attack Vector | L | Local |
| Attack Complexity | L | Low |
| Privileges Required | L | Low |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | H | High |
| Integrity | H | High |
| Availability | H | High |
Timeline
- 2026-04-03 — Published (NVD)
- 2026-09-14 — Last modified (NVD)
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.
Affected
References
- https://git.kernel.org/stable/c/125f932a76a97904ef8a555f1dd53e5d0e288c54
- https://git.kernel.org/stable/c/77914255155e68a20aa41175edeecf8121dac391
- https://git.kernel.org/stable/c/a5bd5a2710310c965ea4153cba4210988a3454e2
- https://git.kernel.org/stable/c/af0d1613d6751489dbf9f69aac1123f0b1e566e5
- https://git.kernel.org/stable/c/baf246d6680befde2086b1df9eb3aaba3fb6853f
- https://git.kernel.org/stable/c/de70da1fb1d152e981ecb3157f7ec2b633005c16