CVE-2026-68231

media: airspy: Return queued buffers on start_streaming() failure

N/A
Published: August 10, 2026 at 12:00 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: media: airspy: Return queued buffers on start_streaming() failure The vb2 framework hands buffers to the driver via buf_queue() before calling start_streaming(). If start_streaming() returns an error without first returning those buffers via vb2_buffer_done(), vb2_start_streaming() fires WARN_ON(owned_by_drv_count) and the queued buffers leak. airspy_start_streaming() returned -ENODEV early when the USB device had been disconnected (s->udev == NULL) without returning any buffers that buf_queue() had already accepted. Take v4l2_lock first and jump to the existing err_clear_bit label, which already drains s->queued_bufs via vb2_buffer_done(..., VB2_BUF_STATE_QUEUED) before unlocking. This mirrors the uvcvideo fix in commit 4cf3b6fd54eb ("media: uvcvideo: Return queued buffers on start_streaming() failure").

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.17 ≤ v < 5.10.2653.17 ≤ v < 5.15.2163.17 ≤ v < 6.1.1833.17 ≤ v < 6.12.1013.17 ≤ v < 6.18.423.17 ≤ v < 6.6.1483.17 ≤ v < 7.1.63.17 ≤ v < 7.23.17634fe5033951b80ef4b98d8f047cb1083d29170d
Vendor states this is fixed in 04344d0b4929caa94c0df72f767752aa0935ef5d (fixed)
Vendor states this is fixed in 122ce0c0af629a8765ddf1adf6fb85c6db3d47cb (fixed)
Vendor states this is fixed in 170fcc945bc094b1c956bf555c070692826a3eff (fixed)
Vendor states this is fixed in 73bd2779865372b1017d4f555b45270aa2d0d710 (fixed)
Vendor states this is fixed in 877686a74ecdc93dcaee09dbac566e819059c9e7 (fixed)
Vendor states this is fixed in badceeb82a9d8d8e98d07859f3c89130ae1998b9 (fixed)
Vendor states this is fixed in bcdf261c4c29077fc3da6449f7eda77357046205 (fixed)
Vendor states this is fixed in cd42623d698b59f1fe5768f78a4101c28d5feb2e (fixed)
Vendor states this is fixed in 3.17 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card