CVE-2026-89488openvswitch: Fix CT limit teardown use-after-free
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: openvswitch: Fix CT limit teardown use-after-free Packet processing uses CT limit state under RCU, while netns teardown frees that state under ovs_mutex. The CT limit pointer was neither removed from readers nor protected by a grace period, allowing packet processing to dereference the freed state. An unprivileged user can trigger this bug from a user and network namespace, causing a slab-use-after-free in ovs_ct_execute() when the netns is torn down. Publish the CT limit pointer through RCU, remove it before teardown, and wait for readers before freeing its contents. Keep ovs_mutex around individual CT limit updates, and use the RCU read-side lock while GET traverses the RCU-protected limit lists. Netns teardown detaches the RCU-protected CT limit state in the pernet .pre_exit callback while holding ovs_mutex. The pernet core guarantees an RCU grace period between the .pre_exit and .exit callbacks, so the .exit callback completes the teardown without adding any extra synchronization. The netlink command handlers do not need NULL checks because the userspace netlink socket holds an active reference to its network namespace while a request is processed. The per-netns exit path therefore cannot run concurrently with SET, DEL, or GET for that socket's namespace.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 11efd5cb04a184eea4f57b68ea63dddd463158d1 before 239f26589a6926db28c436e14f28517581ef1385; 11efd5cb04a184eea4f57b68ea63dddd463158d1 builds before 3b9369881b403f4cdbb11fa998554382bdcc3d8c; 11efd5cb04a184eea4f57b68ea63dddd463158d1 builds before 3b41d907400cc1dd1da9555b81dca422b1f44433; from 11efd5cb04a184eea4f57b68ea63dddd463158d1 before 680f20d5937fa4d1367c59fe83091b78041015f5; from 11efd5cb04a184eea4f57b68ea63dddd463158d1 before bf4aaa7ea2579e24ed7de2e20578a875bebca011; from 11efd5cb04a184eea4f57b68ea63dddd463158d1 before e15407c3a8a005324f633cd46cd8fb58042c1157; 11efd5cb04a184eea4f57b68ea63dddd463158d1 builds before 6a6d36fadb8537d9b79e72c9fa51885ec0c33e10; from 11efd5cb04a184eea4f57b68ea63dddd463158d1 before 403f96c32c9e24600093d7d0c61c17daeedca957 | CNA record |
References
- https://git.kernel.org/stable/c/239f26589a6926db28c436e14f28517581ef1385
- https://git.kernel.org/stable/c/3b9369881b403f4cdbb11fa998554382bdcc3d8c
- https://git.kernel.org/stable/c/3b41d907400cc1dd1da9555b81dca422b1f44433
- https://git.kernel.org/stable/c/680f20d5937fa4d1367c59fe83091b78041015f5
- https://git.kernel.org/stable/c/bf4aaa7ea2579e24ed7de2e20578a875bebca011
- https://git.kernel.org/stable/c/e15407c3a8a005324f633cd46cd8fb58042c1157
- https://git.kernel.org/stable/c/6a6d36fadb8537d9b79e72c9fa51885ec0c33e10
- https://git.kernel.org/stable/c/403f96c32c9e24600093d7d0c61c17daeedca957
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.