Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89901

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

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/

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 634fe5033951b80ef4b98d8f047cb1083d29170d – < c9081e2655188d2d134a741aec837dc70439d505
    • affected 634fe5033951b80ef4b98d8f047cb1083d29170d – < 75089cea32e5055773bd13116236d08fdc98678a
    • affected 634fe5033951b80ef4b98d8f047cb1083d29170d – < 155d0378ae0d6305cc4840583a6b42d2d0595bff
    • affected 634fe5033951b80ef4b98d8f047cb1083d29170d – < 6e4ea90fdc6608cd5fac342e146ab6ae15d430bc
    • affected 634fe5033951b80ef4b98d8f047cb1083d29170d – < a9a8c37ddda9fa3687b142be9098e1c37b8faf35
    • affected 634fe5033951b80ef4b98d8f047cb1083d29170d – < 297fee023f46d771a844520675692ea089d80d9d
    • affected 634fe5033951b80ef4b98d8f047cb1083d29170d – < c6749ac8f59cc80eb1b2d52f167fdf13e12655cc
    • affected 634fe5033951b80ef4b98d8f047cb1083d29170d – < 2f378dc45e685fc825d2dd08e7864666d6fcc009
  • Linux · Linux

    • affected 3.17
    • unaffected < 3.17
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89901 badge
[![CVE-2026-89901](https://cveledger.app/badge/CVE-2026-89901.svg)](https://cveledger.app/cve/CVE-2026-89901)

Record last updated .