Skip to main content
Vulnerability Database/CVE-2026-97539

CVE-2026-97539: Linux Kernel USB xusbatm Driver Vulnerability

CVE-2026-97539 is a USB driver flaw in the Linux kernel xusbatm module caused by improper pointer arithmetic when handling dynamic IDs. This post explains its technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-97539 Overview

CVE-2026-97539 affects the Linux kernel's xusbatm USB ATM driver. The driver's probe function relied on pointer arithmetic against a static usb_device_id table to compute an index. When a dynamic ID is registered through sysfs, the usb_device_id passed to probe lives on the heap instead of the static table. The resulting pointer subtraction produces an index that is wildly out of bounds, leading to invalid memory access inside the kernel.

The upstream fix converts xusbatm to carry its index in driver_info and sets no_dynamic_id to prevent dynamic ID registration against this driver.

Critical Impact

An out-of-bounds index derived from heap-resident usb_device_id pointers can corrupt kernel memory state or trigger a crash when a dynamic USB ID is bound to xusbatm.

Affected Products

  • Linux kernel versions containing the xusbatm driver prior to the fix commits
  • Stable kernel branches referenced by commits 8944ef1, eb6cd6d3, f7db611d, and fad6cab3
  • Distributions shipping unpatched kernels with USB ATM (xusbatm) support enabled

Discovery Timeline

  • 2026-09-25 - CVE-2026-97539 published to the National Vulnerability Database
  • 2026-09-28 - Last updated in NVD database

Technical Details for CVE-2026-97539

Vulnerability Analysis

The xusbatm driver is a USB ATM (Asynchronous Transfer Mode) helper driver in the Linux kernel. Its probe handler identified which configured device it was matching by subtracting the base address of its static usb_device_id array from the pointer passed in by the USB core. That technique worked only while the matching entry resided in the driver's own static table.

The USB subsystem lets users register additional device IDs at runtime through sysfs (new_id). For dynamic IDs, the USB core allocates a usb_device_id on the heap and passes that heap pointer to probe. The static-table pointer arithmetic then yields a nonsensical, large index. The driver subsequently uses this index to dereference its internal arrays, resulting in out-of-bounds reads or writes in kernel space [CWE-125 / CWE-787].

The fix carries the intended index in the driver_info field of each usb_device_id, which is the standard USB driver pattern. The patch additionally sets no_dynamic_id because xusbatm initializes its device IDs dynamically at module load and cannot meaningfully support user-supplied dynamic IDs.

Root Cause

The root cause is unsafe pointer arithmetic that assumed the probe-time usb_device_id always lived inside the driver's static array. The assumption broke once dynamic IDs entered the picture, producing an uncontrolled index used for array indexing in the driver.

Attack Vector

Triggering the condition requires the ability to write to xusbatm's new_id sysfs attribute, which is restricted to privileged users (root/CAP_SYS_ADMIN), and a USB device matching the registered dynamic ID. On systems where unprivileged users or scripts can influence USB ID registration, the out-of-bounds index can be reached without an exploit chain. The practical impact ranges from kernel memory corruption to a denial-of-service crash.

No verified public exploit code is available. See the kernel commit references for the exact source changes.

Detection Methods for CVE-2026-97539

Indicators of Compromise

  • Kernel oops or panic messages referencing xusbatm in the call trace
  • Unexpected KASAN reports flagging out-of-bounds access in xusbatm_usb_probe or related functions
  • Unexplained writes to /sys/bus/usb/drivers/xusbatm/new_id in audit logs

Detection Strategies

  • Inventory running kernel versions and compare against the fix commits 8944ef1, eb6cd6d3, f7db611d, and fad6cab3 to identify unpatched hosts
  • Enable CONFIG_KASAN on test kernels to surface out-of-bounds accesses during QA of USB stacks
  • Monitor dmesg and journal logs for xusbatm warnings, oopses, or driver re-binding events

Monitoring Recommendations

  • Alert on auditd rules covering writes to /sys/bus/usb/drivers/*/new_id and remove_id
  • Track kernel crash telemetry on endpoints running DSL or legacy USB ATM hardware
  • Correlate USB device insertion events with subsequent kernel errors to identify abuse attempts

How to Mitigate CVE-2026-97539

Immediate Actions Required

  • Apply the stable kernel updates containing commits 8944ef1bfd, eb6cd6d3d8, f7db611d98, and fad6cab364
  • If xusbatm is not required, blacklist the module by adding blacklist xusbatm to /etc/modprobe.d/
  • Restrict access to USB driver sysfs attributes to administrative accounts only

Patch Information

The fix is distributed across multiple stable kernel branches. Reference the upstream commits: Kernel Git Commit 8944ef1, Kernel Git Commit eb6cd6d3, Kernel Git Commit f7db611d, and Kernel Git Commit fad6cab3. The patch replaces static-table pointer arithmetic with driver_info-based indexing and sets no_dynamic_id on the driver.

Workarounds

  • Unload the module with modprobe -r xusbatm on systems that do not use USB ATM hardware
  • Prevent automatic loading by writing install xusbatm /bin/true to a modprobe configuration file
  • Enforce strict permissions on /sys/bus/usb/drivers/xusbatm/ to block unauthorized dynamic ID registration
bash
# Configuration example: block xusbatm module load on affected hosts
echo 'blacklist xusbatm' | sudo tee /etc/modprobe.d/disable-xusbatm.conf
echo 'install xusbatm /bin/true' | sudo tee -a /etc/modprobe.d/disable-xusbatm.conf
sudo modprobe -r xusbatm 2>/dev/null || true

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.