CVE-2026-53389
CVE CVE-2026-53389EUVD EUVD-2026-45511Published 2026-07-19T12:01:54.000ZLast changed 2026-08-05T12:35:29.000ZCVSS 7.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: net/tcp-ao: fix use-after-free of key in del_async path In tcp_ao_delete_key(), the del_async path skips the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are always NULL on LISTEN sockets. However, if a key was added with set_current=1/set_rnext=1 while the socket was in CLOSE state, current_key and rnext_key will be non-NULL after listen() transitions the socket to LISTEN. When such a key is deleted with del_async=1, hlist_del_rcu() and call_rcu() free the key without clearing the dangling pointers. After the RCU grace period, getsockopt(TCP_AO_INFO) dereferences current_key->sndid and rnext_key->rcvid from freed slab memory. Clear current_key and rnext_key in the del_async path when they reference the key being deleted.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.12.95; patch: 7.1.3; d6732b95b6fbbc6d5bb9d2f809e275763640c4a2 <e77fbefd1269b5c123e7c651a1ebdce1b87d19a0; d6732b95b6fbbc6d5bb9d2f809e275763640c4a2 <6ce7ef41743740ce15c2061561b784148b565b3f; 6.7; patch: 7.2-rc1; patch: 0; d6732b95b6fbbc6d5bb9d2f809e275763640c4a2 <7ddc29a094d96e9b3aa280433c6dc443df9eabf2; patch: 6.18.38; d6732b95b6fbbc6d5bb9d2f809e275763640c4a2 <5ba9950bc9078e19b69cca1e56d1553b125c6857
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.