CVE-2026-80837netfilter: nf_tables: don't queue packet path object notifications
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: don't queue packet path object notifications All file:line references below are against v7.2-rc4 (ac5b0e5651b1). The trace was captured on 7.2.0-rc6-kasan72rc6 (075b74841bd0), where the same lines apply. nft_obj_notify() is exported and reached from the packet path. Its only in-tree caller is nft_quota_obj_eval() (net/netfilter/nft_quota.c:68), which notifies with GFP_ATOMIC while evaluating a rule for a transiting packet, holding no mutex. Since commit 67cc570edaa0 ("netfilter: nf_tables: coalesce multiple notifications into one skbuff") that notification is no longer sent immediately. __nft_obj_notify() queues it onto nft_net->notify_list via nft_notify_enqueue() (net/netfilter/nf_tables_api.c:1211), which is a bare list_add_tail(). notify_list has no lock of its own (include/net/netfilter/nf_tables.h:1951), it is serialised by commit_mutex: the six other enqueue sites all run inside a netlink transaction, and the drain in nft_commit_notify() (net/netfilter/nf_tables_api.c:10746) does list_del() + kfree_skb() from nf_tables_commit() with commit_mutex held. Sending packets through a chain that references a depleted quota object therefore races an unlocked list_add_tail() against list_del() + kfree_skb() on another CPU. The WRITE_ONCE(prev->next, new) in __list_add() then stores through an sk_buff that has already been freed: BUG: KASAN: slab-use-after-free in __nft_obj_notify+0x2c5/0x2d0 Write of size 8 at addr ff110001047183c0 by task poc/76 CPU: 0 UID: 1000 PID: 76 Comm: poc Tainted: G W 7.2.0-rc6-kasan72rc6 #4 Call Trace: <IRQ> __nft_obj_notify (include/linux/list.h:164 include/linux/list.h:191 net/netfilter/nf_tables_api.c:1211 net/netfilter/nf_tables_api.c:8743) nft_quota_obj_eval (net/netfilter/nft_quota.c:68) nft_do_chain_inet nf_hook_slow __ip_local_out ip_push_pending_frames udp_send_skb udp_sendmsg __x64_sys_sendto Allocated by task 77: __alloc_skb (net/core/skbuff.c:704) __nft_obj_notify (include/net/netlink.h:1055 net/netfilter/nf_tables_api.c:8731) nft_quota_obj_eval (net/netfilter/nft_quota.c:68) nft_do_chain Freed by task 79: nf_tables_commit (include/linux/skbuff.h:1332 net/netfilter/nf_tables_api.c:10759 net/netfilter/nf_tables_api.c:11185) nfnetlink_rcv_batch (net/netfilter/nfnetlink.c:574) netlink_unicast netlink_sendmsg The buggy address belongs to the cache skbuff_head_cache of size 232 Queueing from the packet path is wrong even leaving the race aside: notify_list is only drained by nft_commit_notify() from nf_tables_commit() (:11185), so a notification enqueued outside a transaction is not sent until some later netlink batch commits, if one ever does. The gfp argument that nft_obj_notify() still takes is a leftover of the pre-67cc570edaa0 behaviour, where this path called nfnetlink_send() directly. Restore that: split the message construction out into nft_obj_notify_alloc() and let each caller decide what to do with the skb. nft_obj_notify(), the exported one reached from the packet path, sends it straight away; nf_tables_obj_notify(), which runs under commit_mutex, keeps queueing it, so transaction notifications are still coalesced.
Timeline
ID reserved
By Linux
- 9 days later
· 9 days later
Published
- 56 days later
· 56 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 67cc570edaa02016a8685a06a0ee91f05a6277d9 – < f010756ed75ac003146a1cbc93501092343bb3a3
- affected 67cc570edaa02016a8685a06a0ee91f05a6277d9 – < 6989f298103f575a768a85e4b19d2384709237f8
- affected 67cc570edaa02016a8685a06a0ee91f05a6277d9 – < df86c0e84025be8b6dd572a20852698927aa666b
- affected 67cc570edaa02016a8685a06a0ee91f05a6277d9 – < 6fa88d11983c6fe693c13ed7c5b3b75ae9f39de6
- affected 67cc570edaa02016a8685a06a0ee91f05a6277d9 – < e97e2d6d0b150fd78be573f9fdf193f204d9334e
- affected 67cc570edaa02016a8685a06a0ee91f05a6277d9 – < 68de7f3a38acab355c24114f77bf00d3094ce4da
- affected 67cc570edaa02016a8685a06a0ee91f05a6277d9 – < 7904b94768e983bcb2be34a8d6d1f3450f5b838b
- affected 5.9
- unaffected < 5.9
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.108 – ≤ 6.12.*
- unaffected 6.18.49 – ≤ 6.18.*
- unaffected 7.1.13 – ≤ 7.1.*
- unaffected 7.2.3 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References7
- https://git.kernel.org/stable/c/f010756ed75ac003146a1cbc93501092343bb3a3 (opens in a new tab)
- https://git.kernel.org/stable/c/6989f298103f575a768a85e4b19d2384709237f8 (opens in a new tab)
- https://git.kernel.org/stable/c/df86c0e84025be8b6dd572a20852698927aa666b (opens in a new tab)
- https://git.kernel.org/stable/c/6fa88d11983c6fe693c13ed7c5b3b75ae9f39de6 (opens in a new tab)
- https://git.kernel.org/stable/c/e97e2d6d0b150fd78be573f9fdf193f204d9334e (opens in a new tab)
- https://git.kernel.org/stable/c/68de7f3a38acab355c24114f77bf00d3094ce4da (opens in a new tab)
- https://git.kernel.org/stable/c/7904b94768e983bcb2be34a8d6d1f3450f5b838b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-71287 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80837)Record last updated .