Linux Kernel: Out-of-Bounds Access (CVE-2026-80910)
Published Last modified Sources: Ubuntu, HKCERT, Debian LTS, SUSE, BSI, EUVD, CVE.org, Msrc Update Guide
What is affected, what to do
In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: lpass-wsa-macro: Fix enum kcontrol accesses EAR SPKR PA Gain" and the four "WSA RX* Mux" controls are enumerated, but their get and put callbacks access the value through ucontrol->value.integer.value[0] (a long) instead of ucontrol->value.enumerated.item[0] (an unsigned int). This same pattern was fixed in the sibling drivers by commit bcfe5f76cc40 ("ASoC: codecs: rx-macro: fix accessing array out of bounds for enum type") and commit 0ea5eff7c606 ("ASoC: codecs: va-macro: fix accessing array out of bounds for enum type"), but wsa-macro was missed.
Update Linux Kernel to version 5.15.217, Linux Kernel to version 6.1.184, Linux Kernel to version 6.6.153.
- Affected
- Linux Kernel
lt 5.11..5.15.217 - Linux Kernel
lt 5.16..6.1.184 - Linux Kernel
lt 6.2..6.6.153 - Linux Kernel
lt 6.7..6.12.105 - Linux Kernel
lt 6.13..6.18.46 - Linux Kernel
lt 6.19..7.1.10
- Linux Kernel
- Fixed in
- Linux Kernel
5.15.217 - Linux Kernel
6.1.184 - Linux Kernel
6.6.153 - Linux Kernel
6.12.105 - Linux Kernel
6.18.46 - Linux Kernel
7.1.10 - Linux Kernel
7.2
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
3.3
XIEM Effective CVSS
Highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
3.3
CVSS v3
Severity Low on the scale from 0 to 10.
Source: Ubuntu, HKCERT, Debian LTS, SUSE, BSI, EUVD, CVE.org, Msrc Update Guide
0.2 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 5.3
Show all metrics
- Severity
- Low
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 40.59 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 3.3 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 3.3
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.2 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 5.3
- Low — this CVE sits in the lower 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: lpass-wsa-macro: Fix enum kcontrol accesses EAR SPKR PA Gain" and the four "WSA RX* Mux" controls are enumerated, but their get and put callbacks access the value through ucontrol->value.integer.value[0] (a long) instead of ucontrol->value.enumerated.item[0] (an unsigned int). This same pattern was fixed in the sibling drivers by commit bcfe5f76cc40 ("ASoC: codecs: rx-macro: fix accessing array out of bounds for enum type") and commit 0ea5eff7c606 ("ASoC: codecs: va-macro: fix accessing array out of bounds for enum type"), but wsa-macro was missed. On 64-bit kernels with CONFIG_SND_CTL_DEBUG this trips the elem value sanity check and every read of these controls fails with -EINVAL.
Source: Ubuntu Security Notices, HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, Debian LTS Advisories, suse_csaf, BSI WID Portal, BSI CSAF, ENISA EUVD, cvelistv5, CVE.org (MITRE), Microsoft Security Update Guide
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
| Red Hat | OpenShift |
|
|
Vendors and products
Affected operating systems
| Linux | debian | linux | bookworm |
| Linux | ubuntu | linux | jammy |
| Linux | ubuntu | linux | noble |
| Linux | ubuntu | linux | resolute |
| Linux | debian | linux-6.12 | bookworm |
| Linux | ubuntu | linux-aws | jammy |
| Linux | ubuntu | linux-aws | noble |
| Linux | ubuntu | linux-aws | resolute |
| Linux | ubuntu | linux-aws-5.15 | focal |
| Linux | ubuntu | linux-aws-6.8 | jammy |
| Linux | ubuntu | linux-aws-7.0 | noble |
| Linux | ubuntu | linux-aws-fips | jammy |
| Linux | ubuntu | linux-aws-fips | noble |
| Linux | ubuntu | linux-azure | jammy |
| Linux | ubuntu | linux-azure | noble |
| Linux | ubuntu | linux-azure | resolute |
| Linux | ubuntu | linux-azure-5.15 | focal |
| Linux | ubuntu | linux-azure-6.8 | jammy |
| Linux | ubuntu | linux-azure-fde | noble |
| Linux | ubuntu | linux-azure-fde | resolute |
| Linux | ubuntu | linux-azure-fde-5.15 | focal |
| Linux | ubuntu | linux-azure-fde-6.8 | jammy |
| Linux | ubuntu | linux-azure-fde-7.0 | noble |
| Linux | ubuntu | linux-azure-fips | jammy |
References & sources
- git.kernel.orgstable/c/bd4e5f9c3b764dc0e2a5662f92d63d2f3767a78deuvd
- git.kernel.orgstable/c/4bcac4bf304a3ec746192e49a669c236aaf27dbfeuvd
- git.kernel.orgstable/c/891129df5de79cd533ae335c6eab24df2ff2b0fdeuvd
- git.kernel.orgstable/c/524aa7b9954b0a43dd13f71ecbbac52a151c326deuvd
- git.kernel.orgstable/c/2fe7a89b2b5b73be35c1e493d0246314ba54e427euvd
- git.kernel.orgstable/c/7bcdde412e6c744f6135e02b12a735e2e37b639feuvd
- git.kernel.orgstable/c/56f24311fd5607588a47e44675195a9efb200f29euvd
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
ReceivedLinux
Description added or changed
New references:- https://git.kernel.org/stable/c/2fe7a89b2b5b73be35c1e493d0246314ba54e427
- https://git.kernel.org/stable/c/4bcac4bf304a3ec746192e49a669c236aaf27dbf
- https://git.kernel.org/stable/c/524aa7b9954b0a43dd13f71ecbbac52a151c326d
- https://git.kernel.org/stable/c/56f24311fd5607588a47e44675195a9efb200f29
and 3 more references
Show 9 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: lpass-wsa-macro: Fix enum kcontrol accesses EAR SPKR PA Gain" and the four "WSA RX* Mux" controls are enumerated, but their get and put callbacks access the value through ucontrol->value.integer.value[0] (a long) instead of ucontrol->value.enumerated.item[0] (an unsigned int). This same pattern was fixed in the sibling drivers by commit bcfe5f76cc40 ("ASoC: codecs: rx-macro: fix accessing array out of bounds for enum type") and commit 0ea5eff7c606 ("ASoC: codecs: va-macro: fix accessing array out of bounds for enum type"), but wsa-macro was missed. On 64-bit kernels with CONFIG_SND_CTL_DEBUG this trips the elem value sanity check and every read of these controls fails with -EINVAL.Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80910.json">CVE-2026-80910</a>Reference added —https://git.kernel.org/stable/c/2fe7a89b2b5b73be35c1e493d0246314ba54e427Reference added —https://git.kernel.org/stable/c/4bcac4bf304a3ec746192e49a669c236aaf27dbfReference added —https://git.kernel.org/stable/c/524aa7b9954b0a43dd13f71ecbbac52a151c326dReference added —https://git.kernel.org/stable/c/56f24311fd5607588a47e44675195a9efb200f29Reference added —https://git.kernel.org/stable/c/7bcdde412e6c744f6135e02b12a735e2e37b639fReference added —https://git.kernel.org/stable/c/891129df5de79cd533ae335c6eab24df2ff2b0fdReference added —https://git.kernel.org/stable/c/bd4e5f9c3b764dc0e2a5662f92d63d2f3767a78dSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-80910"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-80910.svg?lang=en" alt="CVE-2026-80910 – NEOSEC Intel" height="20"></a>