CVE-2026-74340 Linux CVE debrief

Who should care

Linux kernel maintainers, Linux distribution maintainers, and users of Linux systems with wifi wcn36xx drivers should assess exposure and verify versions. This includes reviewing Linux kernel versions, verifying the Linux kernel version being used, and applying patches from Linux kernel maintainers as they become available. Additionally, operators, platforms, vulnerability-management teams, and security teams should be aware of the potential impact and be

Why it matters

This vulnerability in the Linux kernel's wifi wcn36xx driver could allow attackers to perform out-of-bounds reads, potentially leading to information disclosure or system crashes. Linux kernel maintainers, Linux distribution maintainers, and users of Linux systems with wifi wcn36xx drivers should assess exposure and verify versions.

• Verify Linux kernel versions for exposure.
• Apply patches to prevent potential out-of-bounds reads.
• Monitor for potential firmware-related issues.

Technical summary

The Linux kernel's wifi wcn36xx driver has a vulnerability that allows for out-of-bounds reads from firmware count in PRINT_REG_INFO indication. This is due to a lack of validation of the firmware-controlled rsp->count field used as a loop bound for indexing into the flexible rsp->regs[] array. The vulnerability is resolved in various kernel commits. Linux kernel maintainers, Linux distribution maintainers, and users of Linux systems with wifi wcn36xx drivers should assess exposure and verify versions. The issue can be mitigated by reviewing Linux kernel versions, verifying the Linux kernel version being used, and applying patches from Linux kernel maintainers as they become available.

Defensive priority

Medium

Recommended defensive actions

• Review Linux kernel versions and ensure they are up-to-date with the latest security patches.
• Verify the Linux kernel version being used and check if it is affected by this vulnerability.
• Apply patches from Linux kernel maintainers as they become available.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description and affected versions. However, the corpus does not establish specific exploitation or impact 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.