{"api_version":"1","generated_at":"2026-08-29T12:13:31+00:00","cve":"CVE-2026-80634","urls":{"html":"https://cve.report/CVE-2026-80634","api":"https://cve.report/api/cve/CVE-2026-80634.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80634","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80634"},"summary":{"title":"netfilter: flowtable: avoid num_encaps underflow on bridge VLAN untag","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: flowtable: avoid num_encaps underflow on bridge VLAN untag\n\nThe DEV_PATH_BR_VLAN_UNTAG case post-decrements info->num_encaps\ninside WARN_ON_ONCE(). num_encaps is u8, so if it's already 0 the\ndecrement still happens and wraps it to 255. The break only leaves\nthe inner switch -- a later path entry can set info->indev back to\na real device, and we end up returning with num_encaps == 255.\n\nnft_dev_forward_path() then walks info.encap[] (size 2) up to\nnum_encaps, which means an OOB stack read and a bogus count copied\ninto the route descriptor.\n\nShould only happen on a malformed bridge path stack, hence the WARN,\nbut worth handling sanely. Move the decrement out of the WARN.\n\n[ While at this, remove the WARN_ON_ONCE since this can only happen\n  with a buggy bridge path stack --pablo ].","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-28 08:16:48","updated_at":"2026-08-29 07:16:47"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"9.8","severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":9.8,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"9.8","severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":9.8,"baseSeverity":"CRITICAL","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/2f55fa28011c97d6495d5787808db10a8c2d690d","name":"https://git.kernel.org/stable/c/2f55fa28011c97d6495d5787808db10a8c2d690d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e052f920773b73be49eb4d8702a9f85de7464363","name":"https://git.kernel.org/stable/c/e052f920773b73be49eb4d8702a9f85de7464363","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80634","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80634","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e990cef6516daa4e1e236433579e333f74fd38cb 2f55fa28011c97d6495d5787808db10a8c2d690d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e990cef6516daa4e1e236433579e333f74fd38cb e052f920773b73be49eb4d8702a9f85de7464363 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.13","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.13 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"80634","cve":"CVE-2026-80634","epss":"0.001550000","percentile":"0.049800000","score_date":"2026-08-28","updated_at":"2026-08-29 00:12:17"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/netfilter/nf_flow_table_path.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"2f55fa28011c97d6495d5787808db10a8c2d690d","status":"affected","version":"e990cef6516daa4e1e236433579e333f74fd38cb","versionType":"git"},{"lessThan":"e052f920773b73be49eb4d8702a9f85de7464363","status":"affected","version":"e990cef6516daa4e1e236433579e333f74fd38cb","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/netfilter/nf_flow_table_path.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.13"},{"lessThan":"5.13","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.5","versionStartIncluding":"5.13","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"5.13","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: flowtable: avoid num_encaps underflow on bridge VLAN untag\n\nThe DEV_PATH_BR_VLAN_UNTAG case post-decrements info->num_encaps\ninside WARN_ON_ONCE(). num_encaps is u8, so if it's already 0 the\ndecrement still happens and wraps it to 255. The break only leaves\nthe inner switch -- a later path entry can set info->indev back to\na real device, and we end up returning with num_encaps == 255.\n\nnft_dev_forward_path() then walks info.encap[] (size 2) up to\nnum_encaps, which means an OOB stack read and a bogus count copied\ninto the route descriptor.\n\nShould only happen on a malformed bridge path stack, hence the WARN,\nbut worth handling sanely. Move the decrement out of the WARN.\n\n[ While at this, remove the WARN_ON_ONCE since this can only happen\n  with a buggy bridge path stack --pablo ]."}],"metrics":[{"cvssV3_1":{"baseScore":9.8,"baseSeverity":"CRITICAL","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:N - The bug is hit in nft_flow_offload_eval on NF_INET_FORWARD when remotely sourced TCP/UDP packets matching a conntrack flow trigger nft_flow_route() and nft_dev_forward_path() during softirq packet processing on nftables flowtable routers/gateways, not via netlink configuration APIs.\nAC:L - Once an nftables flowtable with bridge VLAN filtering is deployed, an attacker can establish confirmed TCP/UDP flows and steer traffic through the affected bridge/VLAN topology to reach nft_dev_path_info() without races or other conditions outside the attacker's control.\nPR:N - Flowtable and bridge VLAN setup are administrator deployment prerequisites; a remote sender needs no local account, authentication, or CAP_NET_ADMIN on the victim to trigger flow offload path resolution while forwarding traffic through the configured bridge.\nUI:N - Exploitation requires only sending network packets processed automatically on the forwarding path; no victim must open files, mount filesystems, or take any interactive action beyond normal traffic through the router.\nS:U - Out-of-bounds stack reads and writes in nft_dev_forward_path() corrupt kernel stack memory and route descriptors on the affected host only; this is standard kernel compromise within one security authority, not a VM escape or cross-boundary sandbox break.\nC:H - When num_encaps underflows to 255, nft_dev_forward_path() loops up to 255 times over info.encap[2], performing out-of-bounds stack reads of adjacent kernel stack memory that can disclose pointers and other sensitive data.\nI:H - The same loop writes attacker-influenced encap values past route->tuple[].in.encap[2] on the stack, corrupting adjacent route fields and stack data in ways that can be leveraged for arbitrary kernel writes and control-flow hijack.\nA:H - Massive out-of-bounds stack corruption during flow offload setup in softirq context can cause immediate kernel oops/panic and reliable denial of service on forwarding routers processing malicious traffic through vulnerable bridge VLAN paths."}]}],"providerMetadata":{"dateUpdated":"2026-08-29T06:21:33.944Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/2f55fa28011c97d6495d5787808db10a8c2d690d"},{"url":"https://git.kernel.org/stable/c/e052f920773b73be49eb4d8702a9f85de7464363"}],"title":"netfilter: flowtable: avoid num_encaps underflow on bridge VLAN untag","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80634","datePublished":"2026-08-28T06:48:49.022Z","dateReserved":"2026-08-26T14:34:25.777Z","dateUpdated":"2026-08-29T06:21:33.944Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-28 08:16:48","lastModifiedDate":"2026-08-29 07:16:47","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":9.8,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":3.9,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80634","Ordinal":"1","Title":"netfilter: flowtable: avoid num_encaps underflow on bridge VLAN ","CVE":"CVE-2026-80634","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80634","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: flowtable: avoid num_encaps underflow on bridge VLAN untag\n\nThe DEV_PATH_BR_VLAN_UNTAG case post-decrements info->num_encaps\ninside WARN_ON_ONCE(). num_encaps is u8, so if it's already 0 the\ndecrement still happens and wraps it to 255. The break only leaves\nthe inner switch -- a later path entry can set info->indev back to\na real device, and we end up returning with num_encaps == 255.\n\nnft_dev_forward_path() then walks info.encap[] (size 2) up to\nnum_encaps, which means an OOB stack read and a bogus count copied\ninto the route descriptor.\n\nShould only happen on a malformed bridge path stack, hence the WARN,\nbut worth handling sanely. Move the decrement out of the WARN.\n\n[ While at this, remove the WARN_ON_ONCE since this can only happen\n  with a buggy bridge path stack --pablo ].","Type":"Description","Title":"netfilter: flowtable: avoid num_encaps underflow on bridge VLAN "}]}}}