Skip to content
major vulnerability· requires attention

Affects widely used Linux kernel wifi driver; could enable local privilege escalation across many systems.

Systems

CVE-2026-43113

8.8
High
EPSS 0.24%Patch availableMay 8, 2026

Linux kernel wl1251 wifi: fix out-of-bounds indexing of tx_frames by completion IDs.

common questions

Is CVE-2026-43113 being exploited?

Not confirmed. CVE-2026-43113 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.

How severe is CVE-2026-43113?

CVE-2026-43113 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-43113?

Yes. A fix has been recorded for CVE-2026-43113. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-43113 affect?

CVE-2026-43113 affects Linux kernel (wl1251 wifi driver). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-43113?

Upgrade to patched kernel with wl1251 fix.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (wl1251 wifi driver)
impact

Local kernel memory corruption and potential privilege escalation via unvalidated wl1251 completion IDs.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and < 6509dbece7339dbc8980c706b9d623119a6de105
  • affected>= 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and < a8a11a876f0a97061ee5d9e61d0f5a0df7e241c7
  • affected>= 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and < e0dc1ad870d6788b049bfe1511ac75b2333a7550
  • affected>= 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and < b6ba1eacf276063ebeefbbae8056043c24f2efaf
  • affected>= 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and < df15adc692a802636dd3f258fc7cca8bf7a0ed9a
  • affected>= 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and < 8d7465be5163a923ee5d7459719ef5a021c1584a
  • affected>= 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and < 26ee518695c484f75e3606d631278e84bd24ae02
  • affected>= 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and < 0fd56fad9c56356e7fa7a7c52e7ecbf807a44eb0
  • affected2.6.31
vendor says fixed in< 2.6.31, >= 5.10.258 and <= 5.10.*, >= 5.15.209 and <= 5.15.*, >= 6.1.175 and <= 6.1.*, >= 6.6.136 and <= 6.6.*, >= 6.12.83 and <= 6.12.*, >= 6.18.24 and <= 6.18.*, >= 6.19.14 and <= 6.19.*, >= 7.0 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free