Use-after-free in TCP RACK stack option handler
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in p16, p7, p11 and 1 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| FreeBSD | freebsd | =14.3, =14.4, =15.0, =15.1 | |
| FreeBSD | >=14.3-RELEASE <p16, >=14.4-RELEASE <p7, >=15.0-RELEASE <p11, >=15.1-RELEASE <p1 | p16, p7, p11, p1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket