- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ipack: ipoctal: fix UAF, null-ptr-deref, and use-after-free in cleanup on remove Three issues arise when the device is removed while a tty session is still active: 1. UAF of struct ipoctal: the remove callback frees ipoctal via kfree() while tty ops may still access it. Fix by introducing kref-based lifetime management — kref is taken in install() when a tty is opened and released in cleanup() when the tty is finally destroyed; remove() uses kref_put() instead of kfree(). 2. NULL dereference in ipoctal_write_tty(): __ipoctal_remove() frees xmit_buf via tty_port_free_xmit_buf() while a userspace process may still hold the tty fd and call write(). Fix by checking for NULL xmit_buf in ipoctal_write_tty(). 3. UAF in ipoctal_cleanup(): ipack_put_carrier(ipoctal->dev) dereferences ipoctal->dev after the ipack_device has been freed by ipack_device_del(). Fix by caching ipoctal->carrier_owner during probe() and calling module_put() on the cached pointer directly in cleanup(), avoiding any access to ipoctal->dev. Also introduce a "removed" flag in struct ipoctal, set at the start of __ipoctal_remove(), and checked in every tty op that accesses hardware resources (port_activate, write_tty, set_termios, hangup, shutdown). This prevents page faults when devm_ioremap() regions are unmapped after remove() returns.
Timeline
ID reserved
By Linux
Published
- 32 days later
· 32 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 05e5027efc9c0bb6d1d04cde279afbafca0a7929 – < ab5f5b27a340004b92252c6a5f23bf1c6cf3b02a
- affected 05e5027efc9c0bb6d1d04cde279afbafca0a7929 – < c92ef8fd834521f0b788e0511976c689fe57c63c
- affected 05e5027efc9c0bb6d1d04cde279afbafca0a7929 – < a4613140f01bd0fb9980e2746ed9aaa65a29b5d6
- affected 05e5027efc9c0bb6d1d04cde279afbafca0a7929 – < 1a3258e105f711538201bdd2ac2a05b11554eabc
- affected 05e5027efc9c0bb6d1d04cde279afbafca0a7929 – < 4a6518be316029650301f2a5e8f0def229b895d9
- affected 05e5027efc9c0bb6d1d04cde279afbafca0a7929 – < b6b5d64cb161a28347d64dc3168a636c4abb68d5
- affected 3.8
- unaffected < 3.8
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/ab5f5b27a340004b92252c6a5f23bf1c6cf3b02a (opens in a new tab)
- https://git.kernel.org/stable/c/c92ef8fd834521f0b788e0511976c689fe57c63c (opens in a new tab)
- https://git.kernel.org/stable/c/a4613140f01bd0fb9980e2746ed9aaa65a29b5d6 (opens in a new tab)
- https://git.kernel.org/stable/c/1a3258e105f711538201bdd2ac2a05b11554eabc (opens in a new tab)
- https://git.kernel.org/stable/c/4a6518be316029650301f2a5e8f0def229b895d9 (opens in a new tab)
- https://git.kernel.org/stable/c/b6b5d64cb161a28347d64dc3168a636c4abb68d5 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82160 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93050)Record last updated .