{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-80634",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-80634"
  ],
  "published": "2026-08-28T06:50:33Z",
  "summary": "netfilter: flowtable: avoid num_encaps underflow on bridge VLAN untag",
  "details": "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 ].",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": null,
            "compiled_filter": false
          }
        }
      }
    },
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:13",
        "name": "linux"
      },
      "versions": [
        "1:6.18.50-1+rpt1"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.18.50+rpt-rpi-2712",
            "binary_version": "1:6.18.50-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.50+rpt-rpi-v6",
            "binary_version": "1:6.18.50-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.50+rpt-rpi-v7",
            "binary_version": "1:6.18.50-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.50+rpt-rpi-v8",
            "binary_version": "1:6.18.50-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.50+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.50-1+rpt1"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.18.50-1+rpt1": {
            "linux_commit": "cff533aec2fa601846766b32ff57204e0a61bed7",
            "upstream_version": "6.18.50",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": null
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-80634"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/2f55fa28011c97d6495d5787808db10a8c2d690d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/e052f920773b73be49eb4d8702a9f85de7464363"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-29T06:25:05Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 9.8,
      "cvss_v3_severity": "Critical",
      "scenario": "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."
    }
  }
}
