Skip to main content
VulnerabilityPublished Updated

CVE-2026-80634: Linux kernel · netfilter: flowtable: avoid num_encaps underflow on bridge VLAN untag

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in ee8440bb000fff4ef8acbfc99652851e9ca0a35b : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 13:07 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in ee8440bb000fff4ef8acbfc99652851e9ca0a35b, e052f920773b73be49eb4d8702a9f85de7464363, 547ea9f567498e4accc89e7816264f15a1a0629f +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Aug 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
  • ≥ e990cef6516daa4e1e236433579e333f74fd38cb, < ee8440bb000fff4ef8acbfc99652851e9ca0a35b
Fixed in
  • ee8440bb000fff4ef8acbfc99652851e9ca0a35b
LinuxLinuxAffected
  • ≥ e990cef6516daa4e1e236433579e333f74fd38cb, < e052f920773b73be49eb4d8702a9f85de7464363
Fixed in
  • e052f920773b73be49eb4d8702a9f85de7464363
LinuxLinuxAffected
  • ≥ e990cef6516daa4e1e236433579e333f74fd38cb, < 547ea9f567498e4accc89e7816264f15a1a0629f
Fixed in
  • 547ea9f567498e4accc89e7816264f15a1a0629f
LinuxLinuxAffected
  • ≥ e990cef6516daa4e1e236433579e333f74fd38cb, < 2f55fa28011c97d6495d5787808db10a8c2d690d
Fixed in
  • 2f55fa28011c97d6495d5787808db10a8c2d690d
LinuxLinuxAffected
  • ≥ e990cef6516daa4e1e236433579e333f74fd38cb, < 1b52aeb40c9f04bf50eeb4ea09142139d163e239
Fixed in
  • 1b52aeb40c9f04bf50eeb4ea09142139d163e239
LinuxLinuxAffected
  • =5.13
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: flowtable: avoid num_encaps underflow on bridge VLAN untag The DEV_PATH_BR_VLAN_UNTAG case post-decrements info->num_encaps inside WARN_ON_ONCE(). num_encaps is u8, so if it's already 0 the decrement still happens and wraps it to 255. The break only leaves the inner switch -- a later path entry can set info->indev back to a real device, and we end up returning with num_encaps == 255. nft_dev_forward_path() then walks info.encap[] (size 2) up to num_encaps, which means an OOB stack read and a bogus count copied into the route descriptor. Should only happen on a malformed bridge path stack, hence the WARN, but worth handling sanely. Move the decrement out of the WARN. [ While at this, remove the WARN_ON_ONCE since this can only happen with a buggy bridge path stack --pablo ].

References

Community reviews

Loading reviews…