CVE-2026-97539 Linux CVE debrief

Who should care

Linux kernel maintainers, Linux distribution vendors, and organizations using Linux-based systems should assess exposure and prioritize patching or mitigation. They should verify Linux kernel versions, prioritize patching or mitigation for affected systems, and monitor system logs for potential exploitation attempts. Additionally, they should review compensating controls for exposed systems while remediation is scheduled and verified, and check relevant

Why it matters

A vulnerability in the Linux kernel has been addressed, related to the xusbatm driver's handling of USB device IDs. Linux kernel maintainers, Linux distribution vendors, and organizations using Linux-based systems should assess exposure and prioritize patching or mitigation.

• Verify Linux kernel versions to assess exposure
• Prioritize patching or mitigation for affected systems
• Monitor system logs for potential exploitation attempts

Technical summary

The xusbatm driver in the Linux kernel has been modified to dynamically initialize USB device IDs, addressing a vulnerability related to pointer arithmetic with the usb_device_id parameter of probe. This change allows the driver to use driver_info directly. However, the driver still cannot support dynamic IDs and sets no_dynamic_id. The vulnerability was addressed by modifying the xusbatm driver to dynamically initialize USB device IDs, allowing it to use driver_info directly. Linux kernel maintainers, Linux distribution vendors, and organizations using Linux-based systems should assess exposure and prioritize patching or mitigation.

Defensive priority

Verify Linux kernel versions and assess exposure; prioritize patching or mitigation for affected systems.

Recommended defensive actions

• Verify Linux kernel versions to assess exposure
• Prioritize patching or mitigation for affected systems
• Monitor system logs for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. Four source references from the Linux kernel Git repository are provided, detailing the patches applied to address the issue. The vulnerability was addressed by modifying the xusbatm driver to dynamically initialize USB device IDs, allowing it to use driver_info directly. However, the driver still cannot support dynamic IDs and sets no_dynamic_id. Linux kernel maintainers, Linux distribution vendors, and organizations using Linux-based systems should verify Linux

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.