CVE-2026-89901

media: airspy: use vb2_video_unregister_device() on disconnect to fix NULL deref

State
Published
Severity
Not scored
Published
Sep 16, 2026
Updated
Oct 19, 2026
Reserved
Sep 11, 2026

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

media: airspy: use vb2_video_unregister_device() on disconnect to fix NULL deref

airspy_disconnect() clears s->udev under v4l2_lock, but airspy_stop_streaming() unconditionally calls airspy_ctrl_msg() and airspy_free_stream_bufs() afterwards. If a streaming user closes the device after disconnect, stop_streaming() runs and dereferences the NULL s->udev:

airspy_stop_streaming() airspy_ctrl_msg(s, CMD_RECEIVER_MODE, 0, 0, NULL, 0) usb_sndctrlpipe(s->udev, 0) /* NULL deref */ airspy_free_stream_bufs(s) usb_free_coherent(s->udev, ...) /* NULL deref */

The airspy driver uses vb2_fop_release() in its file_operations, so replace video_unregister_device(&s->vdev) with vb2_video_unregister_device(&s->vdev) and move it before clearing s->udev. vb2_video_unregister_device() releases the vb2 queue, which synchronously runs airspy_stop_streaming() if streaming is active, so the URBs, coherent DMA stream buffers and the hardware stop control message all execute while s->udev is still valid.

vb2_video_unregister_device() locks vdev->queue->lock (vb_queue_lock) internally, and stop_streaming() locks v4l2_lock, so the previous outer mutex_lock(&s->vb_queue_lock) / mutex_lock(&s->v4l2_lock) pair around the unregister sequence would self-deadlock and has been removed. A short v4l2_lock critical section around s->udev = NULL remains so any ioctl path that still holds the file descriptor sees coherent state.

Issue identified by automated review of the INV-003 series at https://sashiko.dev/

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 634fe5033951b80ef4b98d8f047cb1083d29170d to before c9081e2655188d2d134a741aec837dc70439d505Affected
  • 634fe5033951b80ef4b98d8f047cb1083d29170d to before 75089cea32e5055773bd13116236d08fdc98678aAffected
  • 634fe5033951b80ef4b98d8f047cb1083d29170d to before 155d0378ae0d6305cc4840583a6b42d2d0595bffAffected
  • 634fe5033951b80ef4b98d8f047cb1083d29170d to before 6e4ea90fdc6608cd5fac342e146ab6ae15d430bcAffected
  • 634fe5033951b80ef4b98d8f047cb1083d29170d to before a9a8c37ddda9fa3687b142be9098e1c37b8faf35Affected
  • 634fe5033951b80ef4b98d8f047cb1083d29170d to before 297fee023f46d771a844520675692ea089d80d9dAffected
  • 634fe5033951b80ef4b98d8f047cb1083d29170d to before c6749ac8f59cc80eb1b2d52f167fdf13e12655ccAffected
  • 634fe5033951b80ef4b98d8f047cb1083d29170d to before 2f378dc45e685fc825d2dd08e7864666d6fcc009Affected
LinuxLinux
  • 3.17Affected
  • before 3.17Not affected
  • 5.10.270 through 5.10.*Not affected
  • 5.15.221 through 5.15.*Not affected
  • 6.1.188 through 6.1.*Not affected
  • 6.6.157 through 6.6.*Not affected
  • 6.12.110 through 6.12.*Not affected
  • 6.18.51 through 6.18.*Not affected
  • 7.2.5 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.