{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89881 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89881 is a memory corruption vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89881 and fix it if it is affected.\n\nWhat it is: CVE-2026-89881 is a memory corruption vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89881 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-89881/ (Markdown: https://insights.sbomify.com/CVE-2026-89881/index.md)","id":"CVE-2026-89881","markdown":"https://insights.sbomify.com/CVE-2026-89881/index.md","name":"CVE-2026-89881","record":{"aliases":["AZL-101550","BELL-CVE-2026-89881","DEBIAN-CVE-2026-89881","GHSA-64c5-3gxh-7523","UBUNTU-CVE-2026-89881"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A memory leak in the rtl2832_sdr driver allows local attackers to exhaust kernel memory by repeatedly connecting and disconnecting the device, causing denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rtl2832_sdr: use vb2_video_unregister_device() on remove to fix DMA leak\n\nrtl2832_sdr_remove() runs on USB disconnect and clears dev-\u003eudev to\nNULL before any pending streaming teardown has run. When user space\nlater closes its file descriptor, vb2 calls rtl2832_sdr_stop_streaming()\nwhich in turn calls rtl2832_sdr_free_stream_bufs(). That helper releases\neach coherent buffer with:\n\n    usb_free_coherent(dev-\u003eudev, dev-\u003ebuf_size,\n                      dev-\u003ebuf_list[dev-\u003ebuf_num],\n                      dev-\u003edma_addr[dev-\u003ebuf_num]);\n\nusb_free_coherent() returns immediately when its dev argument is NULL,\nso every DMA stream buffer that was live at disconnect is silently\nleaked. The URBs allocated in rtl2832_sdr_alloc_urbs() outlive the\ndevice for the same reason.\n\nThe rtl2832_sdr driver uses vb2_fop_release() in its file_operations,\nso replace video_unregister_device(\u0026dev-\u003evdev) with\nvb2_video_unregister_device(\u0026dev-\u003evdev) and move it before clearing\ndev-\u003eudev. vb2_video_unregister_device() releases the vb2 queue, which\nsynchronously runs rtl2832_sdr_stop_streaming() if streaming is active,\nso URBs and coherent DMA stream buffers are freed while dev-\u003eudev is\nstill 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(\u0026dev-\u003evb_queue_lock) / mutex_lock(\u0026dev-\u003ev4l2_lock) pair\naround the unregister sequence would self-deadlock and has been removed.\nA short v4l2_lock critical section around dev-\u003eudev = NULL remains so\nany ioctl 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/","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"media: rtl2832_sdr: use vb2_video_unregister_device() on remove to fix DMA leak","id":"CVE-2026-89881","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"media: rkvdec: hevc: guard INTER_REF_PIC_SET_PRED index underflow","id":"CVE-2026-89882"},"packages":[],"prev":{"headline":"media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure","id":"CVE-2026-89880"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A memory leak in the rtl2832_sdr driver allows local attackers to exhaust kernel memory by repeatedly connecting and disconnecting the device, causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-89881/"}