Skip to content
Systems

CVE-2026-43172

8.8
High
EPSS 0.26%Patch availableMay 8, 2026

Linux kernel iwlwifi: firmware LMAC overrun risk in SMEM parsing.

common questions

Is CVE-2026-43172 being exploited?

Not confirmed. CVE-2026-43172 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.26% probability of exploitation in the next 30 days.

How severe is CVE-2026-43172?

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

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

What does CVE-2026-43172 affect?

CVE-2026-43172 affects Linux kernel (iwlwifi). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-43172?

Upgrade to patched kernel version.

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

executive summary
technical analysis
affected
Linux kernel (iwlwifi)
impact

Kernel memory corruption/crash via invalid firmware LMACs; potential privilege escalation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= ebfa7f8ae155c9a0bb2e4038d6b5d8b14881c424 and < 1d49a42717bdc8de77eabeb5b7d3e88d141ffea9
  • affected>= ebfa7f8ae155c9a0bb2e4038d6b5d8b14881c424 and < 2b4b1510aaaf5b9fb57327ecffc20c055f61f205
  • affected>= ebfa7f8ae155c9a0bb2e4038d6b5d8b14881c424 and < 58192b9ce09b0f0f86e2036683bd542130b91a98
  • affected5.8
vendor says fixed in< 5.8, >= 6.18.16 and <= 6.18.*, >= 6.19.6 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