Description
In the Linux kernel, the following vulnerability has been resolved:

usb: gadget: f_tcm: Fix NULL pointer dereferences in nexus handling

The `tpg->tpg_nexus` 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 `bot_submit_command()` and the data
transfer paths retrieve `tv_nexus = tpg->tpg_nexus` and immediately
dereference `tv_nexus->tvn_se_sess` 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 `usbg_submit_command()` and `bot_send_bad_response()`
correctly implement a NULL check for `tv_nexus` before proceeding.

Fix this by bringing consistency to the nexus handling. Add the
missing `if (!tv_nexus)` checks to the vulnerable BOT command and
request processing paths, aborting the command gracefully with an
error instead of crashing the system.
Published: 2026-05-08
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

In the Linux kernel, the f_tcm USB target driver can dereference a pointer that is expected to reference a nexus structure, "tpg->tpg_nexus", without verifying that it is non‑NULL. When a USB host sends a Bulk‑Only Transport command during the brief race window before the nexus is fully established or immediately after it is dropped, the driver dereferences a NULL pointer, causing a kernel panic. The effect is a local denial of service that brings the kernel process table to an unrecoverable state.

Affected Systems

The flaw exists in the Linux kernel’s USB target driver across all releases in which the f_tcm gadget is enabled. The affected vendor is Linux; the impact is on all Linux kernel versions that contain the unpatched gadget, regardless of distribution. No specific version numbers are provided in this advisory.

Risk and Exploitability

The vulnerability is exploitable only by a malicious or misconfigured USB host that can send BOT commands during the race window. Because it is a local kernel panic, physical access to the device is required. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, but its impact is high enough that any attack that succeeds will bring the system down. The missing null checks contrast with correctly handled functions such as usbg_submit_command, so the attack vector is an unguarded path in the driver.

Generated by OpenCVE AI on May 8, 2026 at 20:35 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a revision that includes the patch which adds null‑check validation to tpg_nexus handling in the f_tcm driver
  • If the f_tcm gadget is not required in your environment, disable it or limit its use to trusted devices through device‑mode or ConfigFS configuration
  • Optionally, monitor kernel logs for "Null Pointer" or "kernel panic" entries that could indicate a race condition exploit

Generated by OpenCVE AI on May 8, 2026 at 20:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 09 May 2026 12:15:00 +0000


Fri, 08 May 2026 21:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362
CWE-476

Fri, 08 May 2026 14:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_tcm: Fix NULL pointer dereferences in nexus handling The `tpg->tpg_nexus` 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 `bot_submit_command()` and the data transfer paths retrieve `tv_nexus = tpg->tpg_nexus` and immediately dereference `tv_nexus->tvn_se_sess` 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 `usbg_submit_command()` and `bot_send_bad_response()` correctly implement a NULL check for `tv_nexus` before proceeding. Fix this by bringing consistency to the nexus handling. Add the missing `if (!tv_nexus)` checks to the vulnerable BOT command and request processing paths, aborting the command gracefully with an error instead of crashing the system.
Title usb: gadget: f_tcm: Fix NULL pointer dereferences in nexus handling
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-05-08T14:21:58.365Z

Reserved: 2026-05-01T14:12:56.008Z

Link: CVE-2026-43424

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-05-08T15:16:54.497

Modified: 2026-05-08T15:16:54.497

Link: CVE-2026-43424

cve-icon Redhat

Severity :

Publid Date: 2026-05-08T00:00:00Z

Links: CVE-2026-43424 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-05-08T22:15:18Z

Weaknesses