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

CVE-2026-90337

serial: core: do fallible allocations before the console can be registered

Description

In the Linux kernel, the following vulnerability has been resolved: serial: core: do fallible allocations before the console can be registered serial_core_add_one_port() allocates uport->tty_groups after uart_configure_port(), which may register the console. If the allocation fails, the driver unwinds the port while its console remains registered. The earlier uport->name allocation has a related failure path that leaves state->uart_port linked to a port being freed. Failslab reproduced a NULL dereference in PL011 console output and a KASAN use-after-free in i.MX console output after failed binds. Allocate the name and tty_groups before linking the port and configuring it. Reserve space for the optional driver attribute group because config_port() may populate uport->attr_group during configuration.

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 (10 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 266dcff03eed0050b6af11aaf2a61ab837d7ba3f – < be61f56c4f0ed1cbf16c5f7b0dec6d6414993dd4
    • affected 266dcff03eed0050b6af11aaf2a61ab837d7ba3f – < e2ddbfd826836cba1b7a25ee4eb512f7d752b703
    • affected 266dcff03eed0050b6af11aaf2a61ab837d7ba3f – < 8c7c75bfa7b84d6999de2100ce9c09e3779249a0
    • affected 266dcff03eed0050b6af11aaf2a61ab837d7ba3f – < 9260a92ce90e6a95ce2ffdf1441c5216bf3f9552
    • affected 266dcff03eed0050b6af11aaf2a61ab837d7ba3f – < c2aec15f78b2e6ccd9b94216a901248511355982
    • affected 266dcff03eed0050b6af11aaf2a61ab837d7ba3f – < 1a0e4fbce5d9c1bc179a35a2fd9ed142664299e3
  • Linux · Linux

    • affected 3.17
    • unaffected < 3.17
    • 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

6

Sources

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

Badge for a README or a ticket

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

Record last updated .