Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89883

media: rc: sunxi-cir: Unregister rc device on probe failure

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-89883, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected b4e3e59fb59c214c5bcf9d1bf2971f100e0dac4f – < 4655a591478e4b31a3396695a2457daad9d4c899
    • affected b4e3e59fb59c214c5bcf9d1bf2971f100e0dac4f – < 4efd7146dcf959afe64e9c51531cd8f82e60eab6
    • affected b4e3e59fb59c214c5bcf9d1bf2971f100e0dac4f – < 826763adbd8bd3137c5b3756650da473dc6216d5
    • affected b4e3e59fb59c214c5bcf9d1bf2971f100e0dac4f – < 59951b8a87ef4fb4b5b9409f70ba07663681a040
    • affected b4e3e59fb59c214c5bcf9d1bf2971f100e0dac4f – < 5b58d8c206f37525c8217171e1f3e91dd2fa55e5
    • affected b4e3e59fb59c214c5bcf9d1bf2971f100e0dac4f – < 5e6f5bffaa80fc8ecce348ec0e34fed9d843e47e
    • affected b4e3e59fb59c214c5bcf9d1bf2971f100e0dac4f – < 479aa6fa8c50f1052f1451326ef7d4d586d340c3
  • Linux · Linux

    • affected 3.17
    • unaffected < 3.17
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89883 badge
[![CVE-2026-89883](https://cveledger.app/badge/CVE-2026-89883.svg)](https://cveledger.app/cve/CVE-2026-89883)

Record last updated .