{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-72312",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-72312"
  ],
  "published": "2026-08-15T06:04:33Z",
  "summary": "octeontx2-af: fix VF bringup affecting PF promiscuous state",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nocteontx2-af: fix VF bringup affecting PF promiscuous state\n\nMbox handling of nix_set_rx_mode for a VF with promiscuous and\nall_multi flags set to false causes deletion of the PF's promiscuous\nand allmulti MCAM rules. This occurs because the APIs that\nenable/disable these rules operate only on the PF, even when the\nmbox request is made via a VF interface.\n\nGuard both rvu_npc_enable_allmulti_entry() and\nrvu_npc_enable_promisc_entry() disable paths with an is_vf() check so\nthat a VF bringing up or tearing down its interface cannot inadvertently\nclear the PF's MCAM rules.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/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": "6.1.178",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-72312"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/daa2451640a3e0727fd598f5c2ccb8bb4d5a8b9c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/212c59e5e416859579272288fd325148fc316109"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/53e17d9ed779ad25870abb9c31bc294c71a2278c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3de77d2f34c2bc2acaedabc2c5e0a561b85c283a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3cf83432e0561aef6d7ec2664909d12d0ff0ffc1"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/fabb881df322da25442f98d23f5fa371e3c78ec4"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-17T05:50:24Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.9,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - Exploitation requires local control of an SR-IOV VF netdev on Marvell OcteonTX2/CN10K hardware; the bug is triggered via the VF driver's mailbox to the AF (rvu_mbox_handler_nix_set_rx_mode), not by remote packet delivery.\nAC:L - An attacker with VF netdev access can reliably trigger the flaw by bringing the interface up/down or changing rx_mode (e.g., ip link set up), which sends NIX_SET_RX_MODE with promisc/allmulti cleared; no race or victim timing is required.\nPR:L - Only guest/namespace CAP_NET_ADMIN (or equivalent root in an SR-IOV-assigned VM) is needed to manage the VF netdev; host init-namespace root is not required and user namespaces cannot reach this hardware path without the VF device.\nUI:N - No victim interaction is needed; the attacker initiates VF interface bringup/teardown or rx_mode updates that invoke otx2_do_set_rx_mode/otx2vf_do_set_rx_mode and the AF mbox handler.\nS:C - A VF tenant can alter PF-side NPC MCAM promiscuous/allmulti rules (rvu_npc_enable_promisc_entry/rvu_npc_enable_allmulti_entry mask pcifunc to the PF), crossing the SR-IOV isolation boundary between guest/tenant and host/provider packet filtering.\nC:L - Disabling the PF promiscuous/allmulti MCAM entries can blind host IDS/tcpdump and other monitoring that depends on promiscuous reception, reducing visibility into network traffic on the affected PF (limited confidentiality impact, not arbitrary kernel memory read).\nI:L - The VF causes unauthorized modification of host-side hardware packet-filter state by disabling PF MCAM promisc/allmulti rules; this is limited integrity impact on network policy rather than arbitrary memory or code execution.\nA:H - Clearing PF promiscuous and allmulti MCAM rules can break or degrade PF multicast delivery and promiscuous capture/monitoring on internet-facing cloud/edge servers using these NICs, and can be repeated by cycling the VF interface."
    }
  }
}