CVE-2026-90399
Linux · Kernel (ath12k driver)
A heap-based buffer overflow exists in the Linux kernel ath12k driver due to a stride mismatch during mac_phy_caps_parse, potentially allowing memory corruption.
Executive summary
A heap-based buffer overflow vulnerability in the Linux kernel ath12k driver may allow a local attacker to achieve system compromise or denial of service.
Vulnerability
The vulnerability is a heap-based buffer overflow occurring within the ath12k_wmi_mac_phy_caps_parse function. The driver incorrectly calculates the memory allocation size compared to the pointer arithmetic used for writing data, leading to out-of-bounds memory writes when processing firmware-provided TLVs.
Business impact
Successful exploitation of this vulnerability could lead to arbitrary code execution or a system crash, resulting in significant service disruption. Given the CVSS score of 8.4, this flaw presents a high risk to system integrity and availability, particularly for environments relying on wireless connectivity hardware supported by the ath12k driver.
Remediation
Immediate Action: Update the Linux kernel to version 6.12.110, 6.18.52, 7.2.6, or a later stable release to incorporate the necessary memory allocation fixes.
Proactive Monitoring: Monitor system logs for kernel panic events or hardware-related error messages associated with the ath12k driver that may indicate memory corruption attempts.
Compensating Controls: Restrict access to the system to authorized users only, as the vulnerability requires local access to trigger the driver-level flaw.
Exploitation status
Public Exploit Available: No
Analyst recommendation
This vulnerability represents a high-severity memory safety issue within the Linux kernel. System administrators should prioritize testing and deploying the provided kernel patches to their affected environments immediately. Failure to address this flaw could leave systems vulnerable to local privilege escalation or persistent denial of service attacks.
More Linux CVEs all →
History
CVE Brief tracked this CVE 2 days before it had a CVSS score.
- Disclosed CVE record published
- Collected by CVE Brief No CVSS score yet; tracked as early warning
- CVSS score assigned 8.4 (3.1)
- Analyst report written