CVE-2026-43424: usb: gadget: f_tcm: Fix NULL pointer dereferences in nexus handling
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: ftcm: Fix NULL pointer dereferences in nexus handling
The tpg->tpgnexus pointer in the USB Target driver is dynamically managed and tied to userspace configuration via ConfigFS. It can be NULL if the USB host sends requests before the nexus is fully established or immediately after it is dropped.
Currently, functions like botsubmitcommand() and the data transfer paths retrieve tvnexus = tpg->tpgnexus and immediately dereference tvnexus->tvnsesess without any validation. If a malicious or misconfigured USB host sends a BOT (Bulk-Only Transport) command during this race window, it triggers a NULL pointer dereference, leading to a kernel panic (local DoS).
This exposes an inconsistent API usage within the module, as peer functions like usbgsubmitcommand() and botsendbadresponse() correctly implement a NULL check for tvnexus before proceeding.
Fix this by bringing consistency to the nexus handling. Add the missing if (!tvnexus) checks to the vulnerable BOT command and request processing paths, aborting the command gracefully with an error instead of crashing the system.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43424?
CVE-2026-43424 has a medium severity rating of 5.5 according to the CVSS 3.1 scoring.
How do I fix CVE-2026-43424?
To fix CVE-2026-43424, apply the patch provided in the latest updates for the Linux kernel.
What type of vulnerability is CVE-2026-43424?
CVE-2026-43424 is a Null Pointer Dereference vulnerability affecting the USB Target driver in the Linux kernel.
What systems are affected by CVE-2026-43424?
CVE-2026-43424 affects systems running the vulnerable versions of the Linux kernel that utilize the USB Target driver.
When was CVE-2026-43424 published?
CVE-2026-43424 was published on May 8, 2026.