Skip to content
Systems

CVE-2026-43110

8.8
High
EPSS 0.24%Patch availableMay 8, 2026

Linux kernel brcmfmac: fix for IF event bsscfg index out-of-bounds

common questions

Is CVE-2026-43110 being exploited?

Not confirmed. CVE-2026-43110 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-43110?

CVE-2026-43110 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-43110?

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

What does CVE-2026-43110 affect?

CVE-2026-43110 affects Linux kernel brcmfmac WiFi driver. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-43110?

Apply patched kernel update; reboot to enforce.

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

executive summary
technical analysis
affected
Linux kernel brcmfmac WiFi driver
impact

Out-of-bounds access in brcmfmac IF events; could crash kernel or memory corruption.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 2880b86859967af710c72f7d34fb421a86a71e22 and < b329fbcf075949a038045d8e9b86ae3d5bbd8a54
  • affected>= 2880b86859967af710c72f7d34fb421a86a71e22 and < 2ae3ccb78c0a9ef5ee3d80d02ab319ac1d5af734
  • affected>= 2880b86859967af710c72f7d34fb421a86a71e22 and < 9c81bcc2c695e0082012a2a3d36a0eefaa51579c
  • affected>= 2880b86859967af710c72f7d34fb421a86a71e22 and < 3ec7437e9d11374105c2c4e47ae671537729d7e6
  • affected>= 2880b86859967af710c72f7d34fb421a86a71e22 and < 9fca68c2512a362cad258e4df12a307bb2ee4b8e
  • affected>= 2880b86859967af710c72f7d34fb421a86a71e22 and < 1ae1e1caa428844e481231f6dbe9b4f475f1d52d
  • affected>= 2880b86859967af710c72f7d34fb421a86a71e22 and < b427c2b05222db36d32ee141609de6128e9091bb
  • affected>= 2880b86859967af710c72f7d34fb421a86a71e22 and < 304950a467d83678bd0b0f46331882e2ac23b12d
  • affected3.9
vendor says fixed in< 3.9, >= 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