Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43113wifi: wl1251: validate packet IDs before indexing tx_frames

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: wl1251: validate packet IDs before indexing tx_frames wl1251_tx_packet_cb() uses the firmware completion ID directly to index the fixed 16-entry wl->tx_frames[] array. The ID is a raw u8 from the completion block, and the callback does not currently verify that it fits the array before dereferencing it. Reject completion IDs that fall outside wl->tx_frames[] and keep the existing NULL check in the same guard. This keeps the fix local to the trust boundary and avoids touching the rest of the completion flow.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43113, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.24% · top 84% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 – < 6509dbece7339dbc8980c706b9d623119a6de105
    • affected 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 – < a8a11a876f0a97061ee5d9e61d0f5a0df7e241c7
    • affected 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 – < e0dc1ad870d6788b049bfe1511ac75b2333a7550
    • affected 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 – < b6ba1eacf276063ebeefbbae8056043c24f2efaf
    • affected 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 – < df15adc692a802636dd3f258fc7cca8bf7a0ed9a
    • affected 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 – < 8d7465be5163a923ee5d7459719ef5a021c1584a
    • affected 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 – < 26ee518695c484f75e3606d631278e84bd24ae02
    • affected 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 – < 0fd56fad9c56356e7fa7a7c52e7ecbf807a44eb0
  • Linux · Linux

    • affected 2.6.31
    • unaffected < 2.6.31
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.136 – ≤ 6.6.*
    • unaffected 6.12.83 – ≤ 6.12.*
    • unaffected 6.18.24 – ≤ 6.18.*
    • unaffected 6.19.14 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43113 badge
[![CVE-2026-43113](https://cveledger.app/badge/CVE-2026-43113.svg)](https://cveledger.app/cve/CVE-2026-43113)

Record last updated .