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-89597fbdev: uvesafb: unregister connector callback on init failure

Description

In the Linux kernel, the following vulnerability has been resolved: fbdev: uvesafb: unregister connector callback on init failure uvesafb_init() registers the v86d connector callback before registering the platform driver. If platform_driver_register() fails, the function returns the error directly and leaves the connector callback registered. The later platform-device failure path already unregisters the callback. Add the same cleanup before the final return when platform-driver registration fails. This issue was identified during our ongoing static-analysis research while reviewing kernel code.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 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-89597, 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 (13 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 8bdb3a2d7df48b861972c4bfb58490853a228f51 – < b149f77d04082a9da75944cdc488becb0e35258f
    • affected 8bdb3a2d7df48b861972c4bfb58490853a228f51 – < 0352fdac3cbf11e3b323322ff8cd95e20cbf5cd7
    • affected 8bdb3a2d7df48b861972c4bfb58490853a228f51 – < 17518e7123f7ef01b1155064dc01f2087583908e
    • affected 8bdb3a2d7df48b861972c4bfb58490853a228f51 – < 9eb7b3cbe99c9c0edbff69eb155c723e30983c22
    • affected 8bdb3a2d7df48b861972c4bfb58490853a228f51 – < 9f8a822b44c42502f105cf6574f4867067eecdd0
    • affected 8bdb3a2d7df48b861972c4bfb58490853a228f51 – < 466a8af0dee2cf745307155e26884e19a37b7e15
    • affected 8bdb3a2d7df48b861972c4bfb58490853a228f51 – < 9e768ae51426af2034d479133cfd73010d641b1a
    • affected 8bdb3a2d7df48b861972c4bfb58490853a228f51 – < de8db23aa7c337e606fca9faf48b3ba72968597a
  • Linux · Linux

    • affected 2.6.24
    • unaffected < 2.6.24
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .