CVE-2026-53220: Linux kernel · netfilter: revalidate bridge ports
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d4b1301fd3c9e5e105fd3767c68bc4ba558bb228 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in d4b1301fd3c9e5e105fd3767c68bc4ba558bb228, ccb9fd4b87538ccf19ccff78ee26700526d94867, 43330a1e8aace6b5a8de9aba127e9e394ab49b0f +2
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: netfilter: revalidate bridge ports ebt_redirect_tg() dereferences br_port_get_rcu() return without a NULL check, causing a kernel panic when the bridge port has been removed between the original hook invocation and an NFQUEUE reinject. A mere NULL check isn't sufficient, however. As sashiko review points out userspace can not only remove the port from the bridge, it could also place the device in a different virtual device, e.g. macvlan. If this happens, we must drop the packet, there is no way for us to reinject it into the bridge path. Switch to _upper API, we don't need the bridge port structure. Also, this fix keeps another bug intact: Both nfnetlink_log and nfnetlink_queue use CONFIG_BRIDGE_NETFILTER too aggressive, which prevents certain logging features when queueing in bridge family: NETFILTER_FAMILY_BRIDGE can be enabled while the old CONFIG_BRIDGE_NETFILTER cruft is off. Fixes tag is a common ancestor, this was always broken.
References
- git.kernel.org/stable/c/98cc0403f546c52104d654fa24d86e9bcac964d3 (opens in a new tab)
- git.kernel.org/stable/c/43330a1e8aace6b5a8de9aba127e9e394ab49b0f (opens in a new tab)
- git.kernel.org/stable/c/4beffcd726e2a731cea4dc18e1fbc55c8d76f1a0 (opens in a new tab)
- git.kernel.org/stable/c/d4b1301fd3c9e5e105fd3767c68bc4ba558bb228 (opens in a new tab)
- git.kernel.org/stable/c/ccb9fd4b87538ccf19ccff78ee26700526d94867 (opens in a new tab)