VulnerabilityPublished 17 Sep 2026Updated 30 Oct 2026

CVE-2026-90337: Linux kernel · serial: core: do fallible allocations before the console can be registered

Source GCVE Database

Compare

Authoritative record:CVE-2026-90337· High

Not known to be exploited · fixed in e2ddbfd826836cba1b7a25ee4eb512f7d752b703 : patch Linux kernel soon.

Data as of 30 Oct 2026, 18:33 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in e2ddbfd826836cba1b7a25ee4eb512f7d752b703, c2aec15f78b2e6ccd9b94216a901248511355982, be61f56c4f0ed1cbf16c5f7b0dec6d6414993dd4 +3

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-3m6c-788w-h698

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 266dcff03eed0050b6af11aaf2a61ab837d7ba3f, < e2ddbfd826836cba1b7a25ee4eb512f7d752b703	Fixed in e2ddbfd826836cba1b7a25ee4eb512f7d752b703
LinuxLinux	Affected ≥ 266dcff03eed0050b6af11aaf2a61ab837d7ba3f, < c2aec15f78b2e6ccd9b94216a901248511355982	Fixed in c2aec15f78b2e6ccd9b94216a901248511355982
LinuxLinux	Affected ≥ 266dcff03eed0050b6af11aaf2a61ab837d7ba3f, < be61f56c4f0ed1cbf16c5f7b0dec6d6414993dd4	Fixed in be61f56c4f0ed1cbf16c5f7b0dec6d6414993dd4
LinuxLinux	Affected ≥ 266dcff03eed0050b6af11aaf2a61ab837d7ba3f, < 9260a92ce90e6a95ce2ffdf1441c5216bf3f9552	Fixed in 9260a92ce90e6a95ce2ffdf1441c5216bf3f9552
LinuxLinux	Affected ≥ 266dcff03eed0050b6af11aaf2a61ab837d7ba3f, < 8c7c75bfa7b84d6999de2100ce9c09e3779249a0	Fixed in 8c7c75bfa7b84d6999de2100ce9c09e3779249a0
LinuxLinux	Affected ≥ 266dcff03eed0050b6af11aaf2a61ab837d7ba3f, < 1a0e4fbce5d9c1bc179a35a2fd9ed142664299e3	Fixed in 1a0e4fbce5d9c1bc179a35a2fd9ed142664299e3

AI-suggested

A fix has been implemented in the Linux kernel to allocate necessary resources before console registration and port configuration. Users should update to the fixed kernel versions once available. Since this is a kernel-level issue, applying the official kernel patches or upgrading to a patched kernel release is the recommended mitigation.

Description

A vulnerability in the Linux kernel's serial core subsystem involves improper ordering of memory allocations during console registration. Specifically, allocations for uport->tty_groups occur after uart_configure_port(), which may register the console. If allocation fails, the driver may unwind the port while the console remains registered, leading to potential NULL dereference and use-after-free conditions in console output drivers. The issue has been resolved by allocating necessary resources before linking and configuring the port.

Impact

This vulnerability can cause kernel NULL pointer dereferences and use-after-free conditions in console output drivers, potentially leading to kernel crashes or instability. There is no indication of remote code execution or privilege escalation from the provided data. No known exploitation in the wild has been reported.

Summary

The Linux kernel serial core had a flaw where fallible allocations (uport->tty_groups and uport->name) were performed after the console could be registered via uart_configure_port(). Failure in these allocations could leave the console registered while the port was unwound or freed, causing NULL dereference and KASAN use-after-free errors in console output drivers such as PL011 and i.MX. The fix involves performing these allocations before linking the port and configuring it, ensuring safe resource management and preventing use-after-free scenarios.

References

Community reviews

Loading reviews…