ipack: ipoctal: fix UAF, null-ptr-deref, and use-after-free in cleanup on remove
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 05e5027efc9c0bb6d1d04cde279afbafca0a7929 · fixed in ab5f5b27a340004b92252c6a5f23bf1c6cf3b02a; From 05e5027efc9c0bb6d1d04cde279afbafca0a7929 · fixed in c92ef8fd834521f0b788e0511976c689fe57c63c; From 05e5027efc9c0bb6d1d04cde279afbafca0a7929 · fixed in a4613140f01bd0fb9980e2746ed9aaa65a29b5d6; From 05e5027efc9c0bb6d1d04cde279afbafca0a7929 · fixed in 1a3258e105f711538201bdd2ac2a05b11554eabc; From 05e5027efc9c0bb6d1d04cde279afbafca0a7929 · fixed in 4a6518be316029650301f2a5e8f0def229b895d9; From 05e5027efc9c0bb6d1d04cde279afbafca0a7929 · fixed in b6b5d64cb161a28347d64dc3168a636c4abb68d5
- Linux Linux
3.8
- KernelLinux
From 3.8.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6