CVE-2026-43458
What it is
In the Linux kernel, the following vulnerability has been resolved: serial: caif: hold tty->link reference in ldisc_open and ser_release A reproducer triggers a KASAN slab-use-after-free in pty_write_room() when caif_serial's TX path calls tty_write_room(). The faulting access is on tty->link->port. Hold an extra kref on tty->link for the lifetime of the caif_serial line discipline: get it in ldisc_open() and drop it in ser_release(), and also drop it on the ldisc_open() error path. With this change applied, the reproducer no longer triggers the UAF in my testing.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.253
- Linux Kernel < 5.15.203
- Linux Kernel < 6.1.167
- Linux Kernel < 6.6.130
- Linux Kernel < 6.12.78
- Linux Kernel < 6.18.19
- Linux Kernel < 6.19.9
- Linux Kernel 7.0
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-43458.md and follow it. Check whether this project is affected by CVE-2026-43458. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/23a3ac2e2262a291498567418227b99e1f3606b1
- https://git.kernel.org/stable/c/27e43356d0defb9fc7fa25265219a3ffeb7b3e98
- https://git.kernel.org/stable/c/288598d80a068a0e9281de35bcb4ce495f189e2a
- https://git.kernel.org/stable/c/35b58d3bc716ebb9ebd10fe1cac8c1177242511c
- https://git.kernel.org/stable/c/52135420e9f75853ea0c6cea7b736e3e98495f7d
- https://git.kernel.org/stable/c/8460187b4852fd00bd1c76394358053f3fa4d089
- https://git.kernel.org/stable/c/97a0bb491cae39478c6225381f14e9ac67b7bba7
- https://git.kernel.org/stable/c/ca2ceba983bb23ea0202c2882d963253416654a3
References
- https://git.kernel.org/stable/c/23a3ac2e2262a291498567418227b99e1f3606b1
- https://git.kernel.org/stable/c/27e43356d0defb9fc7fa25265219a3ffeb7b3e98
- https://git.kernel.org/stable/c/288598d80a068a0e9281de35bcb4ce495f189e2a
- https://git.kernel.org/stable/c/35b58d3bc716ebb9ebd10fe1cac8c1177242511c
- https://git.kernel.org/stable/c/52135420e9f75853ea0c6cea7b736e3e98495f7d
- https://git.kernel.org/stable/c/8460187b4852fd00bd1c76394358053f3fa4d089
- https://git.kernel.org/stable/c/97a0bb491cae39478c6225381f14e9ac67b7bba7
- https://git.kernel.org/stable/c/ca2ceba983bb23ea0202c2882d963253416654a3