CVE-2023-53667 Details
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.
A denial-of-service vulnerability has been identified in the Linux kernel's cdc_ncm component. The issue arises when the dwNtbOutMaxSize parameter is set too low, leading to memory allocation problems. Specifically, if dwNtbOutMaxSize is greater than zero but lower than the calculated minimum value, the transmission maximum is incorrectly set, causing allocated memory to be misaligned. This misalignment can result in a kernel panic due to buffer overflow errors, as the allocated space for CDC data becomes insufficient.
Users can update to the latest version of the Linux kernel where this vulnerability has been addressed. Instructions for updating the kernel can be found in the official Linux documentation.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2334ff0b343ba6ba7a6c0586fcc83992bbbc1776 | kernel.org | Patch |
| https://git.kernel.org/stable/c/42b78c8cc774b47023d6d16d96d54cc7015e4a07 | kernel.org | Patch |
| https://git.kernel.org/stable/c/6147745d43ff4e0d2c542e5b93e398ef0ee4db00 | kernel.org | Patch |
| https://git.kernel.org/stable/c/72d0240b0ee4794efc683975c213e4b384fea733 | kernel.org | Patch |
| https://git.kernel.org/stable/c/7e01c7f7046efc2c7c192c3619db43292b98e997 | kernel.org | Patch |
| https://git.kernel.org/stable/c/9be921854e983a81a0aeeae5febcd87093086e46 | kernel.org | Patch |
| https://git.kernel.org/stable/c/bf415bfe7573596ac213b4fd1da9e62cfc9a9413 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ff484163dfb61b58f23e4dbd007de1094427669c | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-476 | NULL Pointer Dereference | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 3.16, < 4.14.317 >= 4.15, < 4.19.285 >= 4.20, < 5.4.245 >= 5.5, < 5.10.181 >= 5.11, < 5.15.114 >= 5.16, < 6.1.31 >= 6.2, < 6.3.5 6.4 rc1 6.4 rc2 6.4 rc3 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Feb 26, 2026 | Reanalysis | [email protected] |
| Feb 3, 2026 | Initial Analysis | [email protected] |
| Oct 7, 2025 | New CVE Received | kernel.org |