{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-74323",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-74323"
  ],
  "published": "2026-08-15T06:04:33Z",
  "summary": "wifi: mt76: mt7996: Fix possible token leak in mt7996_tx_prepare_skb()",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: mt7996: Fix possible token leak in mt7996_tx_prepare_skb()\n\nIf link_conf or link_sta lookup fails in mt7996_tx_prepare_skb routine,\nmt7996 driver leaks an already allocated tx token. Fix the issue\nreleasing the token in case of error.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:13",
        "name": "linux"
      },
      "versions": [
        "1:6.18.29-1+rpt1",
        "1:6.18.33-1+rpt1",
        "1:6.18.34-1+rpt1",
        "1:6.18.39-1+rpt1"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-2712",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v6",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v7",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v8",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-2712",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v6",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v7",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v8",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-2712",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v6",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v7",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v8",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.39+rpt-rpi-2712",
            "binary_version": "1:6.18.39-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.39+rpt-rpi-v6",
            "binary_version": "1:6.18.39-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.39+rpt-rpi-v7",
            "binary_version": "1:6.18.39-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.39+rpt-rpi-v8",
            "binary_version": "1:6.18.39-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.39+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.39-1+rpt1"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.18.29-1+rpt1": {
            "linux_commit": "66318c5b5cd8145a662303af12ed39ac07eb27cc",
            "upstream_version": "6.18.29",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.40"
          },
          "1:6.18.33-1+rpt1": {
            "linux_commit": "95b85bebbedcaedfa7ca79116ed38b7376fba412",
            "upstream_version": "6.18.33",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.40"
          },
          "1:6.18.34-1+rpt1": {
            "linux_commit": "c8c7494100e99ee05b11aaa4f0588a223a63d1af",
            "upstream_version": "6.18.34",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.40"
          },
          "1:6.18.39-1+rpt1": {
            "linux_commit": "60ea684a8ace97bb0db1a16e20753bdd6ab371ff",
            "upstream_version": "6.18.39",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.40"
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-74323"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/06e65d6cf80490bc0457d339595d1ed5a89e8899"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/fa0e9aa92a7bc97fc42014c5efaaf1278fa92723"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/831074096d0450308357271fc0ffd3f600a2487e"
    }
  ],
  "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": 8.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:A - The flaw is in mt7996 TX preparation for EAPOL frames on MLO stations; a nearby WiFi attacker can trigger WPA authentication/rekey traffic that drives this driver TX path on APs, routers, and clients using MediaTek mt7996 hardware.\nAC:L - An attacker can repeatedly initiate or tear down MLO associations and EAPOL exchanges to hit the narrow window where link_conf/link_sta are NULL during TX, reliably leaking tokens without depending on uncontrollable system state.\nPR:N - Exploitation requires only an unauthenticated adjacent WiFi peer initiating or disrupting MLO WPA handshakes that cause EAPOL transmission; no local account, capability, or init-namespace root access is needed on the victim.\nUI:N - No victim user action such as opening files or clicking prompts is required; the attacker alone can generate the authentication traffic needed to reach the vulnerable EAPOL TX path.\nS:U - Impact is confined to the kernel wireless subsystem on the affected host (token exhaustion and potential memory corruption); it does not cross VM, container, or IOMMU security boundaries.\nC:H - Leaked tokens leave stale idr entries pointing at txwi_cache structures that dma.c returns to the free pool, enabling reuse of the same cache while orphaned entries retain dangling skb pointers that can be dereferenced on later token operations.\nI:H - Reusing txwi_cache buffers still referenced by leaked token IDs can corrupt in-flight TX metadata and skb associations, providing a plausible path to controlled memory corruption and kernel code execution beyond simple resource loss.\nA:H - Each leak permanently consumes one of 16384 TX tokens; sustained triggering exhausts the pool, invokes __mt76_set_tx_blocked(), and halts all wireless transmission on the interface, constituting a repeatable denial of service."
    }
  }
}
