GHSA-WFP4-JCV3-WQGX
Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 12:30In 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/
{
"affected": [],
"aliases": [
"CVE-2026-89901"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-16T11:16:59Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: airspy: use vb2_video_unregister_device() on disconnect to fix NULL deref\n\nairspy_disconnect() clears s-\u003eudev under v4l2_lock, but\nairspy_stop_streaming() unconditionally calls airspy_ctrl_msg() and\nairspy_free_stream_bufs() afterwards. If a streaming user closes the\ndevice after disconnect, stop_streaming() runs and dereferences the\nNULL s-\u003eudev:\n\n airspy_stop_streaming()\n airspy_ctrl_msg(s, CMD_RECEIVER_MODE, 0, 0, NULL, 0)\n usb_sndctrlpipe(s-\u003eudev, 0) /* NULL deref */\n airspy_free_stream_bufs(s)\n usb_free_coherent(s-\u003eudev, ...) /* NULL deref */\n\nThe airspy driver uses vb2_fop_release() in its file_operations, so\nreplace video_unregister_device(\u0026s-\u003evdev) with\nvb2_video_unregister_device(\u0026s-\u003evdev) and move it before clearing\ns-\u003eudev. vb2_video_unregister_device() releases the vb2 queue, which\nsynchronously runs airspy_stop_streaming() if streaming is active, so\nthe URBs, coherent DMA stream buffers and the hardware stop control\nmessage all execute while s-\u003eudev is still valid.\n\nvb2_video_unregister_device() locks vdev-\u003equeue-\u003elock (vb_queue_lock)\ninternally, and stop_streaming() locks v4l2_lock, so the previous outer\nmutex_lock(\u0026s-\u003evb_queue_lock) / mutex_lock(\u0026s-\u003ev4l2_lock) pair around\nthe unregister sequence would self-deadlock and has been removed. A\nshort v4l2_lock critical section around s-\u003eudev = NULL remains so any\nioctl path that still holds the file descriptor sees coherent state.\n\nIssue identified by automated review of the INV-003 series at\nhttps://sashiko.dev/",
"id": "GHSA-wfp4-jcv3-wqgx",
"modified": "2026-09-16T12:30:41Z",
"published": "2026-09-16T12:30:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89901"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/155d0378ae0d6305cc4840583a6b42d2d0595bff"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/297fee023f46d771a844520675692ea089d80d9d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2f378dc45e685fc825d2dd08e7864666d6fcc009"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6e4ea90fdc6608cd5fac342e146ab6ae15d430bc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/75089cea32e5055773bd13116236d08fdc98678a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a9a8c37ddda9fa3687b142be9098e1c37b8faf35"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c6749ac8f59cc80eb1b2d52f167fdf13e12655cc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c9081e2655188d2d134a741aec837dc70439d505"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.