CVE-2026-53107

Awaiting Analysis Awaiting Analysis - Queue

USB Kill URB in Libertas WiFi Driver

Publication date: 2026-06-24

Last updated on: 2026-07-14

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-07-14

Generated

2026-07-15

AI Q&A

2026-06-24

EPSS Evaluated

2026-07-13

NVD

CVE-2026-53107

EUVD

EUVD-2026-38975

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

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.

Hi! I’m here to help you understand CVE-2026-53107. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70