CVE-2023-53667net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize
- 5.5MediumCVSS base score
- 0.15%Exploitation in 30 daysEPSS · top 96% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize Currently in cdc_ncm_check_tx_max(), if dwNtbOutMaxSize is lower than the calculated "min" value, but greater than zero, the logic sets tx_max to dwNtbOutMaxSize. This is then used to allocate a new SKB in cdc_ncm_fill_tx_frame() where all the data is handled. For small values of dwNtbOutMaxSize the memory allocated during alloc_skb(dwNtbOutMaxSize, GFP_ATOMIC) will have the same size, due to how size is aligned at alloc time: size = SKB_DATA_ALIGN(size); size += SKB_DATA_ALIGN(sizeof(struct skb_shared_info)); Thus we hit the same bug that we tried to squash with commit 2be6d4d16a084 ("net: cdc_ncm: Allow for dwNtbOutMaxSize to be unset or zero") Low values of dwNtbOutMaxSize do not cause an issue presently because at alloc_skb() time more memory (512b) is allocated than required for the SKB headers alone (320b), leaving some space (512b - 320b = 192b) for CDC data (172b). However, if more elements (for example 3 x u64 = [24b]) were added to one of the SKB header structs, say 'struct skb_shared_info', increasing its original size (320b [320b aligned]) to something larger (344b [384b aligned]), then suddenly the CDC data (172b) no longer fits in the spare SKB data area (512b - 384b = 128b). Consequently the SKB bounds checking semantics fails and panics: skbuff: skb_over_panic: text:ffffffff831f755b len:184 put:172 head:ffff88811f1c6c00 data:ffff88811f1c6c00 tail:0xb8 end:0x80 dev:<NULL> ------------[ cut here ]------------ kernel BUG at net/core/skbuff.c:113! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 0 PID: 57 Comm: kworker/0:2 Not tainted 5.15.106-syzkaller-00249-g19c0ed55a470 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023 Workqueue: mld mld_ifc_work RIP: 0010:skb_panic net/core/skbuff.c:113 [inline] RIP: 0010:skb_over_panic+0x14c/0x150 net/core/skbuff.c:118 [snip] Call Trace: <TASK> skb_put+0x151/0x210 net/core/skbuff.c:2047 skb_put_zero include/linux/skbuff.h:2422 [inline] cdc_ncm_ndp16 drivers/net/usb/cdc_ncm.c:1131 [inline] cdc_ncm_fill_tx_frame+0x11ab/0x3da0 drivers/net/usb/cdc_ncm.c:1308 cdc_ncm_tx_fixup+0xa3/0x100 Deal with too low values of dwNtbOutMaxSize, clamp it in the range [USB_CDC_NCM_NTB_MIN_OUT_SIZE, CDC_NCM_NTB_MAX_SIZE_TX]. We ensure enough data space is allocated to handle CDC data by making sure dwNtbOutMaxSize is not smaller than USB_CDC_NCM_NTB_MIN_OUT_SIZE.
Timeline
ID reserved
By Linux
Published
- 13 months later
· 13 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.15% · top 96% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 289507d3364f96f4b8814726917d572f71350d87 – < 2334ff0b343ba6ba7a6c0586fcc83992bbbc1776
- affected 289507d3364f96f4b8814726917d572f71350d87 – < bf415bfe7573596ac213b4fd1da9e62cfc9a9413
- affected 289507d3364f96f4b8814726917d572f71350d87 – < ff484163dfb61b58f23e4dbd007de1094427669c
- affected 289507d3364f96f4b8814726917d572f71350d87 – < 42b78c8cc774b47023d6d16d96d54cc7015e4a07
- affected 289507d3364f96f4b8814726917d572f71350d87 – < 9be921854e983a81a0aeeae5febcd87093086e46
- affected 289507d3364f96f4b8814726917d572f71350d87 – < 6147745d43ff4e0d2c542e5b93e398ef0ee4db00
- affected 289507d3364f96f4b8814726917d572f71350d87 – < 72d0240b0ee4794efc683975c213e4b384fea733
- affected 289507d3364f96f4b8814726917d572f71350d87 – < 7e01c7f7046efc2c7c192c3619db43292b98e997
- affected 3.16
- unaffected < 3.16
- unaffected 4.14.317 – ≤ 4.14.*
- unaffected 4.19.285 – ≤ 4.19.*
- unaffected 5.4.245 – ≤ 5.4.*
- unaffected 5.10.181 – ≤ 5.10.*
- unaffected 5.15.114 – ≤ 5.15.*
- unaffected 6.1.31 – ≤ 6.1.*
- unaffected 6.3.5 – ≤ 6.3.*
- unaffected 6.4 – ≤ *
References
References8
- https://git.kernel.org/stable/c/2334ff0b343ba6ba7a6c0586fcc83992bbbc1776 (opens in a new tab)
- https://git.kernel.org/stable/c/bf415bfe7573596ac213b4fd1da9e62cfc9a9413 (opens in a new tab)
- https://git.kernel.org/stable/c/ff484163dfb61b58f23e4dbd007de1094427669c (opens in a new tab)
- https://git.kernel.org/stable/c/42b78c8cc774b47023d6d16d96d54cc7015e4a07 (opens in a new tab)
- https://git.kernel.org/stable/c/9be921854e983a81a0aeeae5febcd87093086e46 (opens in a new tab)
- https://git.kernel.org/stable/c/6147745d43ff4e0d2c542e5b93e398ef0ee4db00 (opens in a new tab)
- https://git.kernel.org/stable/c/72d0240b0ee4794efc683975c213e4b384fea733 (opens in a new tab)
- https://git.kernel.org/stable/c/7e01c7f7046efc2c7c192c3619db43292b98e997 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-31951 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-53667)Record last updated .