CVE-2026-97474 Linux CVE debrief

Who should care

Defenders responsible for Linux kernel systems utilizing iwlwifi should assess exposure and prioritize patching. They should also monitor for firmware errors and reconfig failures.

Why it matters

This vulnerability in the Linux kernel's iwlwifi component could lead to a kernel panic during reconfig failure. Defenders should prioritize verifying and applying patches, monitoring for firmware errors, and assessing their inventory for exposure.

• Verify and apply patches to prevent potential kernel panics
• Monitor for firmware errors and reconfig failures to detect potential exploitation attempts
• Assess inventory for exposure to prioritize patching

Technical summary

The vulnerability is caused by the failure to purge async notifications upon nic error in the iwlwifi component of the Linux kernel. This can lead to a kernel panic during reconfig failure. The issue arises when a BSS connection and a NAN connection exist, a firmware error occurs, and the reconfig process fails to properly restore the NAN connection. As a result, the async_handlers_wk process may execute, leading to a panic when it accesses a dangling pointer. Defenders should prioritize verifying and applying patches for Linux kernel versions affected by this vulnerability, particularly in environments utilizing iwlwifi. They should also monitor for firmware errors and reconfig failures, and assess their  

Defensive priority

Defenders should prioritize verifying and applying patches for Linux kernel versions affected by this vulnerability, particularly in environments utilizing iwlwifi. They should also monitor for firmware errors and reconfig failures, and assess their inventory for exposure.

Recommended defensive actions

• Verify and apply patches for Linux kernel versions affected by this vulnerability
• Monitor for firmware errors and reconfig failures
• Assess inventory for exposure
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. However, the corpus does not establish specific affected versions or exploitation details, requiring verification from official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.