{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.0.12-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: capture fast-RX rate before mesh reuses skb-\u003ecb  ieee80211_invoke_fast_rx() reads RX status through IEEE80211_SKB_RXCB(skb), which aliases the same skb-\u003ecb storage that ieee80211_rx_mesh_data() reuses as IEEE80211_TX_INFO.  In the unicast forward path, mesh_data does:  \tinfo = IEEE80211_SKB_CB(fwd_skb); \tmemset(info, 0, sizeof(*info));  on the same skb the caller still names via rx-\u003eskb, then either queues the skb for TX (success) or kfree_skb()'s it (no-route) before returning RX_QUEUED.  The caller's RX_QUEUED arm then calls sta_stats_encode_rate(status) on memory that is either zeroed (success path) or freed (no-route path).  The latter is KASAN slab-use-after-free in ieee80211_prepare_and_rx_handle.  Fix by encoding the rate from status before invoking ieee80211_rx_mesh_data(), so the RX_QUEUED arm consumes a value captured while status was still backed by valid memory.",
  "id": "DEBIAN-CVE-2026-64117",
  "modified": "2026-09-14T16:47:39.807632703Z",
  "published": "2026-07-19T16:17:53.217Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-64117"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-64117"
  ]
}