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.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- 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() failure0Monitor
- ← EarlierCVE-2026-90335Sep 17, 2026 · tty: skip cdev_del() when no cdev is registered0Monitor
- Later →CVE-2026-90337Sep 17, 2026 · serial: core: do fallible allocations before the console can be registered0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 06b376432974fe5f25f2843a8e8438c6a1cf3d50 | Vendor (CNA) |
| Linux Linux | 5e260edd28eddc3b92c9f578df3026fd11c710cf | Vendor (CNA) |
| Linux Linux | 61a2fb25551be0375bc16ef2a70c987dfca26183 | Vendor (CNA) |
| Linux Linux | 802e2192a9d38027730c2869c67c9131b8c8fe9f | Vendor (CNA) |
| Linux Linux | a9c0ffe5930c97b352f32febfc59a6e6ae6772ee | Vendor (CNA) |
| Linux Linux | ddf51d74ee9f9857c99477329d80408cedebda61 | Vendor (CNA) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | Package 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.
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.
Credits
All researchersFinders, 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/5e260edd28eddc3b92c9f578df3026fd11c710cf
- git.kernel.org/stable/c/61a2fb25551be0375bc16ef2a70c987dfca26183
- git.kernel.org/stable/c/802e2192a9d38027730c2869c67c9131b8c8fe9f
- git.kernel.org/stable/c/a9c0ffe5930c97b352f32febfc59a6e6ae6772ee
- git.kernel.org/stable/c/ddf51d74ee9f9857c99477329d80408cedebda61
Vendor advisories and official records. Exploit/PoC links are deliberately left out.