CVE-2026-72255netfilter: nf_queue: pin bridge device while NFQUEUE holds fake dst
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: netfilter: nf_queue: pin bridge device while NFQUEUE holds fake dst The br_netfilter fake rtable is embedded in struct net_bridge and is attached to bridged packets with skb_dst_set_noref(). If such a packet is queued to NFQUEUE, __nf_queue() upgrades that fake dst with skb_dst_force(). At that point the queued skb can hold a real dst reference after bridge teardown has started. The problem is not that every bridged packet needs its own dst reference. The problem is that NFQUEUE can keep the bridge private fake dst alive after unregister begins. Fix this by keeping the bridge fake dst model unchanged and pinning the bridge master device only while the packet sits in NFQUEUE. Record the bridge device in nf_queue_entry when the queued skb carries a bridge fake dst, take a device reference for the queue lifetime, and drop it when the queue entry is freed. Also make sure queued entries are reaped when that bridge device goes down, and drop the redundant nf_bridge_info_exists() test from the fake dst detection. This keeps netdev_priv(br->dev) alive until verdict completion, so the embedded fake rtable and its metrics backing storage cannot be freed out from under dst_release(). It also avoids the constant refcount bump and avoids using ipv4-specific dst helpers for IPv6 bridge traffic.
- 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) | 34666d467cbf1e2e3c7bb15a63eccfb582cdd71f builds before 4e56d3d60d3192ef0a0c08e8b433636690189384; 34666d467cbf1e2e3c7bb15a63eccfb582cdd71f builds before 8dc51351472825500145eed5bddfb88b2ec32008; from 34666d467cbf1e2e3c7bb15a63eccfb582cdd71f before 430521af7fe8a9c08f5a2554224a35f11f51d99e; 34666d467cbf1e2e3c7bb15a63eccfb582cdd71f builds before 3f03a2d225c668283110ad5f9ff159ba4591e2c7; 34666d467cbf1e2e3c7bb15a63eccfb582cdd71f builds before 01ace27af47801dd7f6b839e782b62863af979cc; 34666d467cbf1e2e3c7bb15a63eccfb582cdd71f builds before 0ca505346c5e2905ab7b5313af801fcf38f594a8; 34666d467cbf1e2e3c7bb15a63eccfb582cdd71f builds before 47b3af24de5fbed4bf2952de0f5294ef1a338a26; from 34666d467cbf1e2e3c7bb15a63eccfb582cdd71f before c9c9b37f8c5505224e8d206184df3bb668ee00cf | CNA record |
References
- https://git.kernel.org/stable/c/4e56d3d60d3192ef0a0c08e8b433636690189384
- https://git.kernel.org/stable/c/8dc51351472825500145eed5bddfb88b2ec32008
- https://git.kernel.org/stable/c/430521af7fe8a9c08f5a2554224a35f11f51d99e
- https://git.kernel.org/stable/c/3f03a2d225c668283110ad5f9ff159ba4591e2c7
- https://git.kernel.org/stable/c/01ace27af47801dd7f6b839e782b62863af979cc
- https://git.kernel.org/stable/c/0ca505346c5e2905ab7b5313af801fcf38f594a8
- https://git.kernel.org/stable/c/47b3af24de5fbed4bf2952de0f5294ef1a338a26
- https://git.kernel.org/stable/c/c9c9b37f8c5505224e8d206184df3bb668ee00cf
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.