{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-43113",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-43113"
  ],
  "published": "2026-05-06T07:41:37Z",
  "summary": "wifi: wl1251: validate packet IDs before indexing tx_frames",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: wl1251: validate packet IDs before indexing tx_frames\n\nwl1251_tx_packet_cb() uses the firmware completion ID directly to index\nthe fixed 16-entry wl->tx_frames[] array. The ID is a raw u8 from the\ncompletion block, and the callback does not currently verify that it\nfits the array before dereferencing it.\n\nReject completion IDs that fall outside wl->tx_frames[] and keep the\nexisting NULL check in the same guard. This keeps the fix local to the\ntrust boundary and avoids touching the rest of the completion flow.",
  "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: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.175",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-43113"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/6509dbece7339dbc8980c706b9d623119a6de105"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a8a11a876f0a97061ee5d9e61d0f5a0df7e241c7"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/e0dc1ad870d6788b049bfe1511ac75b2333a7550"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b6ba1eacf276063ebeefbbae8056043c24f2efaf"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/df15adc692a802636dd3f258fc7cca8bf7a0ed9a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8d7465be5163a923ee5d7459719ef5a021c1584a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/26ee518695c484f75e3606d631278e84bd24ae02"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/0fd56fad9c56356e7fa7a7c52e7ecbf807a44eb0"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T13:16:28Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 8.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:A - The vulnerable completion path belongs to a Wi-Fi driver and is reached through wl1251 transmit-completion processing after wireless activity. The highest defensible scenario is a radio-adjacent attacker influencing firmware TX results on the local Wi-Fi medium.\nAC:L - There is no race or hard timing requirement in the vulnerable callback. Once the TX-result path is reached, one completion record with an out-of-range u8 packet ID is enough to trigger the out-of-bounds access.\nPR:N - The TX completion interrupt path performs no attacker credential or authorization check before trusting the firmware completion ring. A radio-adjacent attacker does not need an account or local privileges on the victim.\nUI:N - Completion records are processed automatically by the driver when the device raises a TX-result interrupt. Exploitation does not require the victim to open a file, mount anything, or perform a deliberate action.\nS:U - The vulnerable component is a kernel Wi-Fi driver and the impacts are to the same kernel security authority. This is not a VM escape, IOMMU bypass, or cross-authority boundary crossing.\nC:H - The unchecked u8 index can read a pointer outside the fixed 16-entry tx_frames array and then treat that memory as an skb. As kernel memory corruption, this is defensibly scoreable as high confidentiality impact.\nI:H - The old code can write NULL back through wl->tx_frames[result->id] out of bounds and can also mutate fields through a bogus skb pointer. That is kernel memory corruption with potential control-flow or data-integrity impact.\nA:H - An out-of-bounds pointer dereference or write in this kernel path can readily cause an oops, panic, or device/driver failure. Availability impact is therefore high."
    }
  }
}