CVE-2026-64189

CVE CVE-2026-64189EUVD EUVD-2026-46009Published 2026-07-20T16:27:47.000ZLast changed 2026-08-05T12:39:58.000ZCVSS 7.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: netfilter: ipset: fix race between dump and ip_set_list resize The release path of ip_set_dump_do() and ip_set_dump_done() read inst->ip_set_list via ip_set_ref_netlink(), a plain rcu_dereference_raw() of the array pointer. These run from netlink_recvmsg() without the nfnl mutex and without an RCU read-side critical section. A concurrent ip_set_create() can grow the array: it publishes the new array, calls synchronize_net() and then kvfree()s the old one. Since the dump paths read the array outside any RCU reader, synchronize_net() does not wait for them and the old array can be freed while they still index into it, causing a use-after-free. The dumped set itself stays pinned via set->ref_netlink, so only the array load needs protecting. Take rcu_read_lock() around it, matching ip_set_get_byname() and __ip_set_put_byindex(). BUG: KASAN: slab-use-after-free in ip_set_dump_do (net/netfilter/ipset/ip_set_core.c:1697) Read of size 8 at addr ffff88800b5c4018 by task exploit/150 Call Trace: ... kasan_report (mm/kasan/report.c:595) ip_set_dump_do (net/netfilter/ipset/ip_set_core.c:1697) netlink_dump (net/netlink/af_netlink.c:2325) netlink_recvmsg (net/netlink/af_netlink.c:1976) sock_recvmsg (net/socket.c:1159) __sys_recvfrom (net/socket.c:2315) ... Oops: general protection fault, probably for non-canonical address ... KASAN NOPTI KASAN: maybe wild-memory-access in range [0x02d6...d0-0x02d6...d7] RIP: 0010:ip_set_dump_do (net/netfilter/ipset/ip_set_core.c:1698) Kernel panic - not syncing: Fatal exception

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: 5.10.261; patch: 0; patch: 7.2-rc2; 4.19.5 <4.20; 8a02bdd50b2ecb6d62121d2958d3ea186cc88ce7 <7cd9103283b26b917360ec99d7d2f2d761bcf1ab; patch: 7.1.4; 2f6bf7917f55f9dae913193e49672b3598620eab; patch: 5.15.212; 8a02bdd50b2ecb6d62121d2958d3ea186cc88ce7 <e8a9976b61f1bc4aa7fd25fa26726dfdf2adf710; 8a02bdd50b2ecb6d62121d2958d3ea186cc88ce7 <96fbafc20ebd9a613736c2998b89c539fe3042f5; 8a02bdd50b2ecb6d62121d2958d3ea186cc88ce7 <81d54c766337b923eec26da0a13406760b091093; patch: 6.6.145; 8a02bdd50b2ecb6d62121d2958d3ea186cc88ce7 <a7a299277959683204d73333c32c092fd69327d4; 8a02bdd50b2ecb6d62121d2958d3ea186cc88ce7 <e8ee198bbc04a32d336e79160fde980e0235b39f; 4.20; 8a02bdd50b2ecb6d62121d2958d3ea186cc88ce7 <ff86ea9b7fdf70564e60436fbee68c96bc459943; patch: 6.18.39; 8a02bdd50b2ecb6d62121d2958d3ea186cc88ce7 <1bc67c3fc98e9fc07032cc56afcdbc690c47d11e; patch: 6.12.96; patch: 6.1.178

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 days

Patchlage 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.