Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-90336: serial: core: clear freed pointers on uart_register_driver() failure

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 06b376432974fe5f25f2843a8e8438c6a1cf3d50, 5e260edd28eddc3b92c9f578df3026fd11c710cf, 61a2fb25551be0375bc16ef2a70c987dfca26183.

Low priority for now. Upgrade to Linux Linux 06b376432974fe5f25f2843a8e8438c6a1cf3d50, 5e260edd28eddc3b92c9f578df3026fd11c710cf, 61a2fb25551be0375bc16ef2a70c987dfca26183 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 17, 2026
Updated
Oct 30, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-90336

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5e260edd28eddc3b92c9f578df3026fd11c710cfaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a9c0ffe5930c97b352f32febfc59a6e6ae6772eeaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 802e2192a9d38027730c2869c67c9131b8c8fe9faffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ddf51d74ee9f9857c99477329d80408cedebda61affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 06b376432974fe5f25f2843a8e8438c6a1cf3d50affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 61a2fb25551be0375bc16ef2a70c987dfca26183affected · git
    • before 2.6.12not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.115-26.12.115-2
Debian:14linuxbefore 7.2.6-17.2.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-90334Sep 17, 2026 · tty: clear cdev pointer after cdev_add() failure
    0Monitor
  • ← EarlierCVE-2026-90335Sep 17, 2026 · tty: skip cdev_del() when no cdev is registered
    0Monitor
  • Later →CVE-2026-90337Sep 17, 2026 · serial: core: do fallible allocations before the console can be registered
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux06b376432974fe5f25f2843a8e8438c6a1cf3d50Vendor (CNA)
Linux Linux5e260edd28eddc3b92c9f578df3026fd11c710cfVendor (CNA)
Linux Linux61a2fb25551be0375bc16ef2a70c987dfca26183Vendor (CNA)
Linux Linux802e2192a9d38027730c2869c67c9131b8c8fe9fVendor (CNA)
Linux Linuxa9c0ffe5930c97b352f32febfc59a6e6ae6772eeVendor (CNA)
Linux Linuxddf51d74ee9f9857c99477329d80408cedebda61Vendor (CNA)
debian:linux6.12.115-2 · Debian:13Package registry (OSV)
debian:linux7.2.6-1 · Debian:14Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records