CVE-2026-31779
Linux kernel wifi driver fix for potential out-of-bounds read in iwl_mvm_nd_match_info_handler.
Is CVE-2026-31779 being exploited?
Not confirmed. CVE-2026-31779 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.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-31779?
CVE-2026-31779 is rated High with a CVSS score of 8.1. 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-31779?
Yes. A fix has been recorded for CVE-2026-31779. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-31779 affect?
CVE-2026-31779 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-31779?
Apply the fixed kernel update
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Out-of-bounds read in iwlwifi could leak kernel memory via crafted Wi-Fi frames, risk of info disclosure or crash.
Patch when possible
- affected>= 5ac54afd4d97ad8d94fe250c83b1924eb6d2268c and < f6abac936a0dfd31d6c3e49205ec0ee75a8f887f
- affected>= 5ac54afd4d97ad8d94fe250c83b1924eb6d2268c and < ffbed27ba15ef80d1c622eeedbfef03e501ae134
- affected>= 5ac54afd4d97ad8d94fe250c83b1924eb6d2268c and < e67d8c626ace80b0fa2b48c8ec0a46b508c93442
- affected>= 5ac54afd4d97ad8d94fe250c83b1924eb6d2268c and < dd90880eb5ec5442b37eb2b95688f4a63f4883e3
- affected>= 5ac54afd4d97ad8d94fe250c83b1924eb6d2268c and < ca0e9491b98ca4c5b44204b0b3dd8062a3b5fba2
- affected>= 5ac54afd4d97ad8d94fe250c83b1924eb6d2268c and < 744fabc338e87b95c4d1ff7c95bc8c0f834c6d99
- affected6.1
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.