rootpwn

high · CVSS v3 7.1

CVE-2026-93117

A use‑after‑free flaw in the Linux kernel’s USB subsystem could be triggered when a USB device probe runs concurrently with the removal of a

Overview

A use‑after‑free flaw in the Linux kernel’s USB subsystem could be triggered when a USB device probe runs concurrently with the removal of a dynamic ID. The issue allows an attacker to potentially cause a crash or gain elevated privileges by manipulating USB devices during the probe phase.

Description

In the Linux kernel, the following vulnerability has been resolved: usb: fix UAF when probe runs concurrent to dyn ID removal Dynamic IDs are only guaranteed to be valid when usb_dynids_lock is held, as remove_id_store can free the node. Thus, make a copy in usb_probe_interface. Clarify the documentation that the id parameter is only valid during the probe. USB serial has the same pattern, but it does not need fixing as the IDs cannot be removed via sysfs.

Impact

If exploited, an attacker could cause a kernel crash (availability loss) or execute arbitrary code with kernel privileges (confidentiality and integrity compromise). The risk is limited to systems that allow dynamic USB ID removal and expose the USB subsystem to untrusted devices.

Remediation

Apply the latest kernel update that includes the fix for CVE‑2026‑93117. Verify that the kernel version is at least the one where the patch was merged (see distribution release notes). Disable or restrict dynamic USB ID removal if not required, and ensure USB device access is governed by proper udev rules or SELinux/AppArmor policies.

Risk context

High severity (CVSS 7.1). No EPSS data available. The vulnerability is mitigated in current kernel releases; unpatched systems remain vulnerable until the patch is applied.

Affected products

  • Linux kernel
  • Ubuntu
  • Debian
  • Red Hat Enterprise Linux
  • CentOS
  • Fedora
  • SUSE Linux Enterprise Server
  • Arch Linux

Scores

Severity
high
CVSS v2
2.1
CVSS v3
7.1
CVSS v4
—
EPSS
—

usb kernel use-after-free privilege-escalation denial-of-service patch defense

← All CVEs

Related CVEs

high

CVE-2026-93203

A race condition in the batman-adv kernel module can corrupt the CRC used to validate claim frames, leading to incorrect routing information in mesh networks. The flaw may cause routing tables to become inconsistent, potentially disrupting network connectivity.

View analysis

high

CVE-2026-93110

A high‑severity flaw in the Linux kernel’s RDMA core module allows a use‑after‑free condition when a module is unloaded while RCU callbacks are still queued. The bug can cause kernel crashes or, in the worst case, arbitrary code execution if an attacker can trigger the callback after the module is gone.

View analysis

high

CVE-2026-93111

In the Linux kernel, the following vulnerability has been resolved: bpf: Mark tracing_multi trampolines as ftrace managed Since tracing_multi link does not set ftrace_managed, it would fail to release the tracing_multi link when attaching tracing_multi link and then attaching fentry link. [ 3.714215] WARNING: kernel/bpf/trampoline.c:1727 at bpf_trampoline_multi_detach+0x20b/0x240, CPU#1: test_progs/97 ... [ 3.733170] bpf_tracing_multi_link_release+0x14/0x30 [ 3.733890] bpf_link_free+0x58/0x130 [ 3.734414] bpf_link_release+0x23/0x30 Fix it by setting 'ftrace_managed = true' in register_fentry_multi().

View analysis

high

CVE-2026-93120

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: configfs: fix out-of-bounds read of qw_sign os_desc_qw_sign_show() passes OS_STRING_QW_SIGN_LEN as the input length to utf16s_to_utf8s(), but that argument counts UTF-16 code units while OS_STRING_QW_SIGN_LEN (14) is the byte size of qw_sign[]. The array holds only OS_STRING_QW_SIGN_LEN / 2 (7) code units, so the conversion reads up to 7 units (14 bytes) past the end of qw_sign[] into the following members of struct gadget_info when the stored signature fills the array without a NUL terminator, exposing those bytes through the configfs attribute. The store path halves the count for its input bound but passes the full byte count as the utf8s_to_utf16s() output limit; use the destination code-unit count in both directions.

View analysis