Skip to main content
VulnerabilityPublished Updated

CVE-2026-53220: Linux kernel · netfilter: revalidate bridge ports

Source GCVE Database

0
Authoritative record:CVE-2026-53220

Not known to be exploited · CVSS 5.5 Medium · fixed in d4b1301fd3c9e5e105fd3767c68bc4ba558bb228 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
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
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ f350a0a87374418635689471606454abc7beaa3a, < d4b1301fd3c9e5e105fd3767c68bc4ba558bb228
Fixed in
  • d4b1301fd3c9e5e105fd3767c68bc4ba558bb228
LinuxLinuxAffected
  • ≥ f350a0a87374418635689471606454abc7beaa3a, < ccb9fd4b87538ccf19ccff78ee26700526d94867
Fixed in
  • ccb9fd4b87538ccf19ccff78ee26700526d94867
LinuxLinuxAffected
  • ≥ f350a0a87374418635689471606454abc7beaa3a, < 43330a1e8aace6b5a8de9aba127e9e394ab49b0f
Fixed in
  • 43330a1e8aace6b5a8de9aba127e9e394ab49b0f
LinuxLinuxAffected
  • ≥ f350a0a87374418635689471606454abc7beaa3a, < 98cc0403f546c52104d654fa24d86e9bcac964d3
Fixed in
  • 98cc0403f546c52104d654fa24d86e9bcac964d3
LinuxLinuxAffected
  • ≥ f350a0a87374418635689471606454abc7beaa3a, < 4beffcd726e2a731cea4dc18e1fbc55c8d76f1a0
Fixed in
  • 4beffcd726e2a731cea4dc18e1fbc55c8d76f1a0
LinuxLinuxAffected
  • =2.6.36
Fixed in–

AI-suggested

The vulnerability has been resolved in the Linux kernel by switching to the _upper API and adding appropriate checks to prevent kernel panic. If you cannot patch yet, avoid scenarios where bridge ports may be removed or moved during packet reinjection. Monitor vendor advisories for official fixes.

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

Community reviews

Loading reviews…