{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-53059",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-53059"
  ],
  "published": "2024-11-19T17:20:22Z",
  "summary": "wifi: iwlwifi: mvm: Fix response handling in iwl_mvm_send_recovery_cmd()",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: iwlwifi: mvm: Fix response handling in iwl_mvm_send_recovery_cmd()\n\n1. The size of the response packet is not validated.\n2. The response buffer is not freed.\n\nResolve these issues by switching to iwl_mvm_send_cmd_status(),\nwhich handles both size validation and frees the buffer.",
  "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.116",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-53059"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9c98ee7ea463a838235e7a0e35851b38476364f2"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/45a628911d3c68e024eed337054a0452b064f450"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3f45d590ccbae6dfd6faef54efe74c30bd85d3da"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/64d63557ded6ff3ce72b18ab87a6c4b1b652161c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3eb986c64c6bfb721950f9666a3b723cf65d043f"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9480c3045f302f43f9910d2d556d6cf5a62c1822"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/07a6e3b78a65f4b2796a8d0d4adb1a15a81edead"
    }
  ],
  "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 code is only entered through the iwlwifi firmware-error/HW-restart recovery flow, which an attacker within Wi-Fi radio range can drive by sending malformed 802.11 frames that provoke firmware asserts. This requires being on the same radio segment, not routable network access.\nAC:L - Once a recovery cycle occurs the response page is leaked deterministically on every invocation, and an adjacent attacker can repeat the stimulus to re-enter the path arbitrarily often. No memory-layout grooming or uncontrollable victim state is needed.\nPR:N - The adjacent radio attacker needs no credentials on the target host and no association is required to emit frames that provoke firmware errors. Nothing along the path from `iwl_mvm_nic_error()` to `iwl_mvm_send_recovery_cmd()` performs a privilege check.\nUI:N - The device only needs its Wi-Fi interface up; the recovery path is entered automatically by the driver's error handler with no victim action.\nS:U - The out-of-bounds read, the leaked page, and the forced disconnect all stay within the kernel's own security authority on the affected host. No VM, IOMMU, or sandbox boundary is crossed.\nC:L - The unvalidated `*(__le32 *)host_cmd.resp_pkt->data` read can pull up to 4 bytes of adjacent kernel memory from beyond the declared payload, and that value is emitted to the kernel log by `IWL_ERR`. The disclosure is strictly bounded to a fixed 4 bytes rather than an arbitrary read.\nI:N - There is no out-of-bounds or attacker-controlled write anywhere in the flow \u2014 the defect is a read of an unvalidated length plus a missing free. No kernel data or control flow can be corrupted.\nA:H - Every recovery cycle leaks an entire RX page (`iwl_free_resp()` is never called), so repeated attacker-induced firmware restarts cause unbounded kernel memory exhaustion, which is serious on the embedded/IoT/automotive systems this driver runs on. Additionally, a garbage non-zero status read out of bounds triggers `ieee80211_hw_restart_disconnect()` on every station interface, tearing down all Wi-Fi connectivity on a host where Wi-Fi is often the only link."
    }
  }
}