FreeBSD
Use-after-free in TCP RACK stack option handler
The RACK setsockopt(2) handler drops the connection lock in order to copy option data from userspace, then reacquires the lock. After reacquiring, it verifies that the TCP stack had not been switched away, but did not reload its pointer to the stack's per-connection control block. If userspace switches stacks twice during this window, the check will succeed but the saved pointer will refer to freed memory. The bug may be exploitable by an unprivileged local user to escalate privileges.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.4high · scored by CISA ADP · CWE-416
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
FreeBSD FreeBSD
- >= 15.1-RELEASE, < p1
- >= 15.0-RELEASE, < p11
- >= 14.4-RELEASE, < p7
- >= 14.3-RELEASE, < p16
Fixed in p1, p11, p7, p16
Mitigation
Upgrade FreeBSD to p1 or p11 or p7 or p16 or later.
References
- Vendor advisory security.freebsd.org/advisories/FreeBSD-SA-26:43.tcp.asc
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.