← All Advisories
Reported from OT-Advisories.com as of

Critical Linux Kernel Netfilter Vulnerability Scores 9.8 CVSS

Last refreshed2026-10-15

Status: UPDATED  |  Advisory ID: CVE-2026-80634

Key Details

CVECVE-2026-80634
CVSS Score / Version
9.8 (Critical) / CVSS v3.1
Updated2026-10-15
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel
Exploitation prediction (EPSS)
0.55% probability of exploitation in the next 30 days (45% percentile) -- FIRST.org's EPSS model.

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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 ]. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-80634
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-80634
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.