CVE-2026-89883

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 — 4 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: rc: sunxi-cir: Unregister rc device on probe failure

After rc_register_device() succeeds, later probe failures must undo the registration with rc_unregister_device(). The current error path jumps to the allocation cleanup label and only calls rc_free_device(), leaving the rc device registration and resources created by rc_register_device() behind.

Add a registered-device unwind label for the IRQ lookup, IRQ request, and hardware initialization failure paths. Keep rc_free_device() for failures before rc_register_device() succeeds.

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 (7)

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

media: rc: sunxi-cir: Unregister rc device on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/826763adbd8bd3137c5b3756650da473dc6216d5
generic

media: rc: sunxi-cir: Unregister rc device on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5e6f5bffaa80fc8ecce348ec0e34fed9d843e47e
generic

media: rc: sunxi-cir: Unregister rc device on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5b58d8c206f37525c8217171e1f3e91dd2fa55e5
generic

media: rc: sunxi-cir: Unregister rc device on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/59951b8a87ef4fb4b5b9409f70ba07663681a040
generic

media: rc: sunxi-cir: Unregister rc device on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4efd7146dcf959afe64e9c51531cd8f82e60eab6
generic

media: rc: sunxi-cir: Unregister rc device on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/479aa6fa8c50f1052f1451326ef7d4d586d340c3
generic

media: rc: sunxi-cir: Unregister rc device on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4655a591478e4b31a3396695a2457daad9d4c899

Vendor Advisories for CVE-2026-89883(2)

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 44× in last 7d / 122× 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.

Showing the most recent 100 of 122 total refreshes for this CVE.

  1. 2026-10-05 06:40 UTCEG score recompute
  2. 2026-10-05 06:40 UTCVendor advisory
  3. 2026-10-05 06:40 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 19:47 UTCVendor advisory
  6. 2026-10-04 19:47 UTCGHSA enrichment
  7. 2026-10-04 08:54 UTCVendor advisory
  8. 2026-10-04 08:54 UTCGHSA enrichment
  9. 2026-10-03 22:00 UTCEG score recompute
  10. 2026-10-03 22:00 UTCVendor advisory
  11. 2026-10-03 22:00 UTCGHSA enrichment
  12. 2026-10-03 11:06 UTCVendor advisory
  13. 2026-10-03 11:06 UTCGHSA enrichment
  14. 2026-10-03 00:13 UTCEG score recompute
  15. 2026-10-03 00:13 UTCVendor advisory
  16. 2026-10-03 00:13 UTCGHSA enrichment
  17. 2026-10-02 13:19 UTCVendor advisory
  18. 2026-10-02 13:19 UTCGHSA enrichment
  19. 2026-10-02 02:26 UTCEG score recompute
  20. 2026-10-02 02:26 UTCVendor advisory
  21. 2026-10-02 02:26 UTCGHSA enrichment
  22. 2026-10-01 19:51 UTCEPSS rescore
  23. 2026-10-01 15:17 UTCVendor advisory
  24. 2026-10-01 15:17 UTCGHSA enrichment
  25. 2026-10-01 04:24 UTCVendor advisory
Show 75 more
  1. 2026-10-01 04:24 UTCGHSA enrichment
  2. 2026-09-30 17:31 UTCEG score recompute
  3. 2026-09-30 17:31 UTCVendor advisory
  4. 2026-09-30 17:31 UTCGHSA enrichment
  5. 2026-09-30 15:04 UTCEPSS rescore
  6. 2026-09-30 06:36 UTCVendor advisory
  7. 2026-09-30 06:36 UTCGHSA enrichment
  8. 2026-09-29 19:43 UTCEG score recompute
  9. 2026-09-29 19:43 UTCVendor advisory
  10. 2026-09-29 19:43 UTCGHSA enrichment
  11. 2026-09-29 08:26 UTCVendor advisory
  12. 2026-09-29 08:26 UTCGHSA enrichment
  13. 2026-09-28 21:33 UTCEG score recompute
  14. 2026-09-28 21:33 UTCVendor advisory
  15. 2026-09-28 21:33 UTCGHSA enrichment
  16. 2026-09-28 13:52 UTCEPSS rescore
  17. 2026-09-28 13:52 UTCEPSS rescore
  18. 2026-09-28 10:41 UTCVendor advisory
  19. 2026-09-28 10:40 UTCGHSA enrichment
  20. 2026-09-27 23:43 UTCEG score recompute
  21. 2026-09-27 23:43 UTCVendor advisory
  22. 2026-09-27 23:42 UTCGHSA enrichment
  23. 2026-09-27 13:49 UTCEPSS rescore
  24. 2026-09-27 12:48 UTCVendor advisory
  25. 2026-09-27 12:48 UTCGHSA enrichment
  26. 2026-09-27 01:55 UTCEG score recompute
  27. 2026-09-27 01:55 UTCVendor advisory
  28. 2026-09-27 01:54 UTCGHSA enrichment
  29. 2026-09-26 15:59 UTCEPSS rescore
  30. 2026-09-26 14:59 UTCVendor advisory
  31. 2026-09-26 14:59 UTCGHSA enrichment
  32. 2026-09-26 04:06 UTCEG score recompute
  33. 2026-09-26 04:06 UTCVendor advisory
  34. 2026-09-26 04:06 UTCGHSA enrichment
  35. 2026-09-25 17:10 UTCVendor advisory
  36. 2026-09-25 17:10 UTCGHSA enrichment
  37. 2026-09-25 06:17 UTCVendor advisory
  38. 2026-09-25 06:17 UTCGHSA enrichment
  39. 2026-09-24 19:24 UTCEG score recompute
  40. 2026-09-24 19:24 UTCVendor advisory
  41. 2026-09-24 19:24 UTCGHSA enrichment
  42. 2026-09-24 14:04 UTCEPSS rescore
  43. 2026-09-24 08:31 UTCVendor advisory
  44. 2026-09-24 08:31 UTCGHSA enrichment
  45. 2026-09-23 21:38 UTCEG score recompute
  46. 2026-09-23 21:38 UTCVendor advisory
  47. 2026-09-23 21:38 UTCGHSA enrichment
  48. 2026-09-23 17:54 UTCEPSS rescore
  49. 2026-09-23 10:45 UTCVendor advisory
  50. 2026-09-23 10:45 UTCGHSA enrichment
  51. 2026-09-22 23:49 UTCEG score recompute
  52. 2026-09-22 23:49 UTCVendor advisory
  53. 2026-09-22 23:49 UTCGHSA enrichment
  54. 2026-09-22 16:01 UTCEPSS rescore
  55. 2026-09-22 12:55 UTCVendor advisory
  56. 2026-09-22 12:55 UTCGHSA enrichment
  57. 2026-09-22 02:02 UTCEG score recompute
  58. 2026-09-22 02:02 UTCVendor advisory
  59. 2026-09-22 02:02 UTCGHSA enrichment
  60. 2026-09-21 21:09 UTCEPSS rescore
  61. 2026-09-21 15:09 UTCVendor advisory
  62. 2026-09-21 15:09 UTCGHSA enrichment
  63. 2026-09-21 04:16 UTCEG score recompute
  64. 2026-09-21 04:16 UTCVendor advisory
  65. 2026-09-21 04:16 UTCGHSA enrichment
  66. 2026-09-20 20:16 UTCEPSS rescore
  67. 2026-09-20 17:23 UTCVendor advisory
  68. 2026-09-20 17:23 UTCGHSA enrichment
  69. 2026-09-20 06:29 UTCVendor advisory
  70. 2026-09-20 06:29 UTCGHSA enrichment
  71. 2026-09-19 19:34 UTCEG score recompute
  72. 2026-09-19 19:34 UTCVendor advisory
  73. 2026-09-19 19:34 UTCGHSA enrichment
  74. 2026-09-19 08:41 UTCVendor advisory
  75. 2026-09-19 08:41 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-89883?
CVE-2026-89883 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: media: rc: sunxi-cir: Unregister rc device on probe failure After rcregisterdevice() succeeds, later probe failures must undo the registration with rcunregisterdevice(). The current error path jumps to the allocation cleanup label…
When was CVE-2026-89883 disclosed?
CVE-2026-89883 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-89883 actively exploited?
CVE-2026-89883 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-89883?
CVE-2026-89883 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-89883?
No fix for CVE-2026-89883 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-89883 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-89883

Explore →

Is Your Infrastructure Affected by CVE-2026-89883?

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