{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-40929",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-40929"
  ],
  "published": "2024-07-12T12:27:31Z",
  "summary": "wifi: iwlwifi: mvm: check n_ssids before accessing the ssids",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: iwlwifi: mvm: check n_ssids before accessing the ssids\n\nIn some versions of cfg80211, the ssids poinet might be a valid one even\nthough n_ssids is 0. Accessing the pointer in this case will cuase an\nout-of-bound access. Fix this by checking n_ssids first.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.95",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-40929"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3c4771091ea8016c8601399078916f722dd8833b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/f777792952d03bbaf8329fdfa99393a5a33e2640"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9e719ae3abad60e245ce248ba3f08148f375a614"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/29a18d56bd64b95bd10bda4afda512558471382a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/62e007bdeb91c6879a4652c3426aef1cd9d2937b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/60d62757df30b74bf397a2847a6db7385c6ee281"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T11:52:36Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.1,
      "cvss_v3_severity": "High",
      "scenario": "AV:A - The vulnerable branch is only reached through cfg80211's split 6 GHz scan, whose request layout and channel count are built from co-located-AP (RNR) information carried in beacons/probe responses received over the air, so an attacker within WiFi radio range shapes the allocation that is read out of bounds. Per WiFi-frame guidance this is Adjacent rather than Local.\nAC:L - The attacker can beacon crafted RNR elements continuously and vary the advertised co-located-AP count to sweep allocation layouts, while 6 GHz-capable iwlwifi clients perform passive scans routinely, so the condition can be retried until it hits.\nPR:N - An adjacent attacker needs no account or credentials on the target; the passive 6 GHz scan that walks the buggy code is initiated automatically by the system's normal background scanning rather than by any attacker-held privilege.\nUI:N - Periodic passive scanning by NetworkManager/wpa_supplicant drives the vulnerable path with no action from the logged-in user.\nS:U - The out-of-bounds read stays inside the kernel's own memory and security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:L - The read is a single byte at a fixed offset 32 past the ssids pointer and is never copied to userspace or the air; it only selects between two hard-coded dwell budgets (100 vs 300 TU), which yields at most a timing-observable one-bit oracle on adjacent kernel heap memory.\nI:N - Nothing is written out of bounds \u2014 the only side effect is that one of two legitimate constant values is placed in the firmware scan command's adwell_max_budget field.\nA:H - The access reads up to 33 bytes past the end of a kzalloc'd scan request; on KASAN or hardened kernels this is a slab-out-of-bounds report that panics under panic_on_warn/kasan.fault=panic, and a page-order allocation ending on a page boundary can fault and oops."
    }
  }
}