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-90336serial: core: clear freed pointers on uart_register_driver() failure

Description

In the Linux kernel, the following vulnerability has been resolved: serial: core: clear freed pointers on uart_register_driver() failure uart_register_driver() leaves drv->state pointing to freed memory when tty_alloc_driver() fails. If tty_register_driver() fails, drv->tty_driver also retains a pointer after its reference is dropped. Drivers that use drv->state as an "already registered" flag can then skip registration on the next probe and pass the freed state to uart_add_one_port(). This issue was found with failslab on QEMU's raspi1ap board by failing registration and binding the PL011 port again. Clear both pointers on their failure paths, as uart_unregister_driver() already does.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 43 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5e260edd28eddc3b92c9f578df3026fd11c710cf
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a9c0ffe5930c97b352f32febfc59a6e6ae6772ee
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 802e2192a9d38027730c2869c67c9131b8c8fe9f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ddf51d74ee9f9857c99477329d80408cedebda61
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 06b376432974fe5f25f2843a8e8438c6a1cf3d50
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 61a2fb25551be0375bc16ef2a70c987dfca26183
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .