CVE-2026-89880

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure

rtl2832_sdr_start_streaming() calls rtl2832_sdr_alloc_stream_bufs(), rtl2832_sdr_alloc_urbs() and rtl2832_sdr_submit_urbs() in sequence and shares a single err: label that only unlocks the mutex and returns. When alloc_urbs() succeeds but submit_urbs() fails, or when alloc_urbs() itself returns -ENOMEM after alloc_stream_bufs() has already succeeded, the URBs and/or the coherent DMA stream buffers stay allocated while streaming reports failure to vb2. Two latent defects follow on the next VIDIOC_STREAMON:

1) rtl2832_sdr_alloc_stream_bufs() unconditionally resets dev->buf_num to 0 and overwrites dev->buf_list[]/dev->dma_addr[], permanently leaking the coherent DMA memory allocated by the previous attempt.

2) rtl2832_sdr_alloc_urbs() never resets dev->urbs_initialized and only increments it. After a second successful pass urbs_initialized can exceed MAX_BULK_BUFS, so the subsequent rtl2832_sdr_free_urbs() walks from urbs_initialized - 1 down to 0 and reads past the end of dev->urb_list[], passing garbage pointers to usb_free_urb().

Mirror the teardown that stop_streaming() already performs: on the error path call rtl2832_sdr_free_urbs() and rtl2832_sdr_free_stream_bufs() before unlocking. Both helpers are idempotent (free_urbs kills and zeros urbs_initialized; free_stream_bufs is gated on URB_BUF and clears the buf_num counter), so partial-failure paths and the no-allocation paths remain safe.

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

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 16, 2026

Last Modified

September 16, 2026

Advisory Details (8)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fe50cdaebf12cd32ff9a44d92bfd6fbc2300dbd4
generic

media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f14a713a36a5c87568430e9770896f2a8f5bbbb7
generic

media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c91e8ae2b39c6da81f26f2c9877d3fd33a4465ce
generic

media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c819dea3a433ae790b829443fdcc1715d1586560
generic

media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ac02b2c56ccef0788cea9b86990a8f349a3fc6d8
generic

media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8bcf11a239eac4e224ad856277de9a36c91b1711
generic

media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26a2a985bbeee3eaa6f80ff7de732161a171ec9f
generic

media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0337ab0759285076a3f9dcfcc40906e69ab519b3

Vendor Advisories for CVE-2026-89880(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 26× in last 7d / 76× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 05:33 UTCEG score recompute
  2. 2026-10-05 05:33 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 16:32 UTCGHSA enrichment
  5. 2026-10-04 03:32 UTCGHSA enrichment
  6. 2026-10-03 14:31 UTCEG score recompute
  7. 2026-10-03 14:30 UTCGHSA enrichment
  8. 2026-10-03 01:28 UTCEG score recompute
  9. 2026-10-03 01:28 UTCGHSA enrichment
  10. 2026-10-02 12:26 UTCGHSA enrichment
  11. 2026-10-01 22:48 UTCEG score recompute
  12. 2026-10-01 22:48 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 09:47 UTCGHSA enrichment
  15. 2026-09-30 20:46 UTCEG score recompute
  16. 2026-09-30 20:46 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 07:45 UTCGHSA enrichment
  19. 2026-09-29 18:42 UTCEG score recompute
  20. 2026-09-29 18:42 UTCGHSA enrichment
  21. 2026-09-29 04:51 UTCEG score recompute
  22. 2026-09-29 04:51 UTCGHSA enrichment
  23. 2026-09-28 15:50 UTCEG score recompute
  24. 2026-09-28 15:50 UTCGHSA enrichment
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 51 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 02:49 UTCEG score recompute
  3. 2026-09-28 02:49 UTCGHSA enrichment
  4. 2026-09-27 13:49 UTCEPSS rescore
  5. 2026-09-27 13:48 UTCGHSA enrichment
  6. 2026-09-27 00:35 UTCEG score recompute
  7. 2026-09-27 00:35 UTCGHSA enrichment
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-26 11:34 UTCEG score recompute
  10. 2026-09-26 11:34 UTCGHSA enrichment
  11. 2026-09-25 22:34 UTCGHSA enrichment
  12. 2026-09-25 08:57 UTCGHSA enrichment
  13. 2026-09-24 19:56 UTCEG score recompute
  14. 2026-09-24 19:56 UTCGHSA enrichment
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-24 06:54 UTCEG score recompute
  17. 2026-09-24 06:54 UTCGHSA enrichment
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-23 17:53 UTCGHSA enrichment
  20. 2026-09-23 04:53 UTCEG score recompute
  21. 2026-09-23 04:53 UTCGHSA enrichment
  22. 2026-09-22 16:01 UTCEPSS rescore
  23. 2026-09-22 15:52 UTCGHSA enrichment
  24. 2026-09-22 02:51 UTCEG score recompute
  25. 2026-09-22 02:51 UTCGHSA enrichment
  26. 2026-09-21 21:09 UTCEPSS rescore
  27. 2026-09-21 13:49 UTCGHSA enrichment
  28. 2026-09-21 00:48 UTCEG score recompute
  29. 2026-09-21 00:48 UTCGHSA enrichment
  30. 2026-09-20 20:16 UTCEPSS rescore
  31. 2026-09-20 11:46 UTCGHSA enrichment
  32. 2026-09-19 22:42 UTCEG score recompute
  33. 2026-09-19 22:42 UTCGHSA enrichment
  34. 2026-09-19 09:42 UTCGHSA enrichment
  35. 2026-09-18 20:38 UTCEG score recompute
  36. 2026-09-18 20:38 UTCGHSA enrichment
  37. 2026-09-18 19:28 UTCEPSS rescore
  38. 2026-09-18 07:21 UTCEG score recompute
  39. 2026-09-18 07:21 UTCGHSA enrichment
  40. 2026-09-17 19:32 UTCEPSS rescore
  41. 2026-09-17 18:20 UTCGHSA enrichment
  42. 2026-09-17 04:22 UTCEG score recompute
  43. 2026-09-17 04:22 UTCGHSA enrichment
  44. 2026-09-16 15:19 UTCEG score recompute
  45. 2026-09-16 15:19 UTCGHSA enrichment
  46. 2026-09-16 14:48 UTCEG score recompute▲ 7.80
  47. 2026-09-16 14:48 UTCGHSA enrichment
  48. 2026-09-16 14:45 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  49. 2026-09-16 11:21 UTCNVD update
  50. 2026-09-16 10:40 UTCEG score recompute
  51. 2026-09-16 10:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-89880?
CVE-2026-89880 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: media: rtl2832sdr: release URBs and stream buffers on startstreaming() failure rtl2832sdrstartstreaming() calls rtl2832sdrallocstream_bufs(), rtl2832sdrallocurbs() and rtl2832sdrsubmiturbs() in sequence and shares a single err:…
When was CVE-2026-89880 disclosed?
CVE-2026-89880 was first published on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89880 actively exploited?
CVE-2026-89880 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89880?
CVE-2026-89880 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89880?
No fix for CVE-2026-89880 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-89880 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-89880

Explore →

Is Your Infrastructure Affected by CVE-2026-89880?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.