Linux kernel (ath11k Wi‑Fi driver) is widely deployed; kernel memory corruption can disrupt systems and enable privilege escalation across organizations.
CVE-2026-90398
Heap overflow in Linux ath11k driver due to TLV length/stride mismatch
do firstUpgrade to a fixed release: < 5.6, >= 6.12.110 and <= 6.12.*, >= 6.18.52 and <= 6.18.*, >= 7.2.6 and <= 7.2.* (+1 more below).
Is CVE-2026-90398 being exploited?
Not confirmed. CVE-2026-90398 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.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-90398?
CVE-2026-90398 is rated High with a CVSS score of 8.4. 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-90398?
Yes. A fix has been recorded for CVE-2026-90398. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-90398 affect?
CVE-2026-90398 affects Linux kernel (ath11k Wi-Fi driver), Devices with Qualcomm/ath11k firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-90398?
Apply kernel update containing the ath11k fix ASAP
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Kernel memory corruption from out‑of‑bounds writes; can cause local privilege escalation or kernel crash; triggered by malicious firmware/firmware TLVs.
Patch when possible
- affected>= 5b90fc760db5a969ed26d70f8e62c91915f012bd and < bbb3b3334a9ed850c5b332eedea107796e691237
- affected>= 5b90fc760db5a969ed26d70f8e62c91915f012bd and < 75185e2b214e842b7e0af29e5d1fef155662b8b1
- affected>= 5b90fc760db5a969ed26d70f8e62c91915f012bd and < acff2713c3212ade15051e7b421f15c89927e70f
- affected>= 5b90fc760db5a969ed26d70f8e62c91915f012bd and < 7a246c72132eb943b5844ba79dad597b47429dba
- affected5.6
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.
timeline
- 17 Sept 2026Published
- 19 Sept 2026Analysed by vulneraibility.com · 2 days later
- 30 Oct 2026CVE record last updated · 41 days later
- Linkgit.kernel.org /stable/c/deb14c9932509c0defaa0620c9ca8d20b385a6bd
- Linkgit.kernel.org /stable/c/b2ecd548f89a4a6c14b5eb4abc825f92b3068dda
- Linkgit.kernel.org /stable/c/bbb3b3334a9ed850c5b332eedea107796e691237
- Linkgit.kernel.org /stable/c/75185e2b214e842b7e0af29e5d1fef155662b8b1
- Linkgit.kernel.org /stable/c/acff2713c3212ade15051e7b421f15c89927e70f
- Linkgit.kernel.org /stable/c/7a246c72132eb943b5844ba79dad597b47429dba
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.