{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89880 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89880 is a high-severity 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-89880 and fix it if it is affected.\n\nWhat it is: CVE-2026-89880 is a high-severity 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-89880 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-89880/ (Markdown: https://insights.sbomify.com/CVE-2026-89880/index.md)","id":"CVE-2026-89880","markdown":"https://insights.sbomify.com/CVE-2026-89880/index.md","name":"CVE-2026-89880","record":{"aliases":["AZL-101604","BELL-CVE-2026-89880","DEBIAN-CVE-2026-89880","GHSA-rq55-pff5-xw57","UBUNTU-CVE-2026-89880"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A flaw in the rtl2832_sdr driver causes memory leaks and out-of-bounds reads on streaming failure, potentially leading to denial of service or code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure\n\nrtl2832_sdr_start_streaming() calls rtl2832_sdr_alloc_stream_bufs(),\nrtl2832_sdr_alloc_urbs() and rtl2832_sdr_submit_urbs() in sequence and\nshares a single err: label that only unlocks the mutex and returns.\nWhen alloc_urbs() succeeds but submit_urbs() fails, or when alloc_urbs()\nitself returns -ENOMEM after alloc_stream_bufs() has already succeeded,\nthe URBs and/or the coherent DMA stream buffers stay allocated while\nstreaming reports failure to vb2. Two latent defects follow on the next\nVIDIOC_STREAMON:\n\n1) rtl2832_sdr_alloc_stream_bufs() unconditionally resets dev-\u003ebuf_num\n   to 0 and overwrites dev-\u003ebuf_list[]/dev-\u003edma_addr[], permanently\n   leaking the coherent DMA memory allocated by the previous attempt.\n\n2) rtl2832_sdr_alloc_urbs() never resets dev-\u003eurbs_initialized and only\n   increments it. After a second successful pass urbs_initialized can\n   exceed MAX_BULK_BUFS, so the subsequent rtl2832_sdr_free_urbs() walks\n   from urbs_initialized - 1 down to 0 and reads past the end of\n   dev-\u003eurb_list[], passing garbage pointers to usb_free_urb().\n\nMirror the teardown that stop_streaming() already performs: on the error\npath call rtl2832_sdr_free_urbs() and rtl2832_sdr_free_stream_bufs()\nbefore unlocking. Both helpers are idempotent (free_urbs kills and zeros\nurbs_initialized; free_stream_bufs is gated on URB_BUF and clears the\nbuf_num counter), so partial-failure paths and the no-allocation paths\nremain safe.\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: release URBs and stream buffers on start_streaming() failure","id":"CVE-2026-89880","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: rtl2832_sdr: use vb2_video_unregister_device() on remove to fix DMA leak","id":"CVE-2026-89881"},"packages":[],"prev":{"headline":"media: s2255: bound JPEG frame size before copying into the buffer","id":"CVE-2026-89879"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A flaw in the rtl2832_sdr driver causes memory leaks and out-of-bounds reads on streaming failure, potentially leading to denial of service or code execution.","url":"https://insights.sbomify.com/CVE-2026-89880/"}