CVE-2026-43421
USB Gadget NCM Net Device Lifecycle Fix
Publication date: 2026-05-08
Last updated on: 2026-05-22
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.19 (exc) |
| linux | linux_kernel | From 6.19 (inc) to 6.19.9 (exc) |
| linux | linux_kernel | From 3.11 (inc) to 6.12.78 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's USB gadget function for network control model (f_ncm). It occurs because the network device (net_device) outlives its parent gadget device during disconnection, which leads to dangling sysfs links and null pointer dereference issues.
Previous attempts to fix this problem either caused regressions related to power management or broke the one-to-one mapping between the function instance and the network device, which affected DHCP server functionality.
The final fix uses device_move to reparent the net_device between the gadget device and /sys/devices/virtual/ during bind and unbind cycles. This preserves the network interface across USB reconnections and allows the DHCP server to maintain its binding.
How can this vulnerability impact me? :
This vulnerability can cause system instability due to null pointer dereferences when the network device outlives its parent gadget device during USB disconnection.
It can also lead to dangling sysfs links, which may cause unexpected behavior or errors in system management tools.
Additionally, improper handling of the network device lifecycle can break DHCP server functionality, potentially disrupting network connectivity on affected systems.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been resolved in the Linux kernel by fixing the net_device lifecycle with device_move to properly reparent the network device between the gadget device and /sys/devices/virtual/ across bind/unbind cycles.
To mitigate this vulnerability, you should update your Linux kernel to a version that includes this fix.