CVE-2026-43422
Received Received - Intake
Null Pointer Dereference in Linux Kernel USB NCM Driver

Publication date: 2026-05-08

Last updated on: 2026-05-08

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: usb: legacy: ncm: Fix NPE in gncm_bind Commit 56a512a9b410 ("usb: gadget: f_ncm: align net_device lifecycle with bind/unbind") deferred the allocation of the net_device. This change leads to a NULL pointer dereference in the legacy NCM driver as it attempts to access the net_device before it's fully instantiated. Store the provided qmult, host_addr, and dev_addr into the struct ncm_opts->net_opts during gncm_bind(). These values will be properly applied to the net_device when it is allocated and configured later in the binding process by the NCM function driver.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-08
Last Modified
2026-05-08
Generated
2026-05-09
AI Q&A
2026-05-08
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's legacy NCM (Network Control Model) USB driver. A recent change deferred the allocation of the net_device structure, which caused the legacy NCM driver to attempt accessing this net_device before it was fully created. This results in a NULL pointer dereference (NPE) during the binding process in the gncm_bind function.

The fix involves storing certain parameters (qmult, host_addr, and dev_addr) into a configuration structure during gncm_bind, so they can be properly applied later when the net_device is fully allocated and configured.


How can this vulnerability impact me? :

This vulnerability can cause a NULL pointer dereference in the legacy NCM USB driver, which may lead to a kernel crash or system instability when the affected code path is executed.

Such crashes could result in denial of service conditions on affected systems, potentially disrupting normal operations or requiring a system reboot.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart