CVE-2026-90381 Linux CVE debrief

Who should care

Defenders responsible for Linux kernel-based systems, particularly those using the mt76 module, should assess exposure and apply patches to mitigate potential risks. They should prioritize verification of affected systems and monitor for any advisories or updates from the Linux kernel community. This includes reviewing compensating controls for exposed systems and tracking exceptions, retesting remediated assets, and closing the item only after evidence is

Why it matters

Defenders should prioritize verification and patching of Linux kernel-based systems using the mt76 module to mitigate potential risks associated with this vulnerability.

• Verification of affected systems and patch application priority
• Potential disruption of wireless network operations if not patched

Technical summary

The Linux kernel's mt76 module has a vulnerability related to handling channel contexts with different bands in the mt76_switch_vif_chanctx() function. This has been resolved through a rework of the function to properly handle channel switches on different radios within a short timeframe, addressing potential risks associated with this vulnerability in Linux kernel-based systems using the mt76 module. Defenders should prioritize verification of affected systems and apply patches to mitigate potential risks. The vulnerability has been addressed through updates provided by the Linux kernel maintainers.

Defensive priority

Defenders should prioritize verification of affected systems and apply patches to mitigate potential risks.

Recommended defensive actions

• Verify if the system uses the affected mt76 module and assess exposure
• Apply patches or updates provided by the Linux kernel maintainers
• Monitor for any advisories or updates from the Linux kernel community
• 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. However, the scope of affected systems and versions requires further verification by defenders. They should check for any additional advisories or updates from the Linux kernel community and verify if the system uses the affected mt76 module. Evidence from the CVE Program and NVD should be reviewed for source-provided CVE metadata and official vulnerability assessment.

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.