CVE-2026-53107
Received Received - Intake
USB Kill URB in Libertas WiFi Driver

Publication date: 2026-06-24

Last updated on: 2026-06-24

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: wifi: libertas: don't kill URBs in interrupt context Serialization for the TX path was enforced by calling usb_kill_urb()/usb_kill_anchored_urbs(), to prevent transmission before a previous URB was completed. usb_tx_block() can be called from interrupt context (e.g. in the HCD giveback path), so we can't always use it to kill in-flight URBs. Prevent sleeping during interrupt context by checking the tx_submitted anchor for existing URBs. We now return -EBUSY, to indicate there's a pending request.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-24
Last Modified
2026-06-24
Generated
2026-06-25
AI Q&A
2026-06-24
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel's wifi libertas driver involves improper handling of USB Request Blocks (URBs) in interrupt context. Specifically, the driver previously killed URBs during interrupt context using usb_kill_urb() or usb_kill_anchored_urbs(), which is unsafe because usb_tx_block() can be called from interrupt context where sleeping is not allowed.

The fix prevents sleeping during interrupt context by checking if there are existing URBs in the tx_submitted anchor and returning an -EBUSY error code to indicate a pending request instead of killing URBs directly.

Impact Analysis

This vulnerability could cause instability or crashes in the Linux kernel's wifi driver due to improper handling of URBs in interrupt context. Killing URBs in interrupt context can lead to unexpected behavior, including potential kernel panics or data transmission issues, which may disrupt wireless communication.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53107. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart