Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80910ASoC: codecs: lpass-wsa-macro: Fix enum kcontrol accesses

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 809bcbcecebff86003e13f07444d21b9d6652a64 – < bd4e5f9c3b764dc0e2a5662f92d63d2f3767a78d
    • affected 809bcbcecebff86003e13f07444d21b9d6652a64 – < 4bcac4bf304a3ec746192e49a669c236aaf27dbf
    • affected 809bcbcecebff86003e13f07444d21b9d6652a64 – < 891129df5de79cd533ae335c6eab24df2ff2b0fd
    • affected 809bcbcecebff86003e13f07444d21b9d6652a64 – < 524aa7b9954b0a43dd13f71ecbbac52a151c326d
    • affected 809bcbcecebff86003e13f07444d21b9d6652a64 – < 2fe7a89b2b5b73be35c1e493d0246314ba54e427
    • affected 809bcbcecebff86003e13f07444d21b9d6652a64 – < 7bcdde412e6c744f6135e02b12a735e2e37b639f
    • affected 809bcbcecebff86003e13f07444d21b9d6652a64 – < 56f24311fd5607588a47e44675195a9efb200f29
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.153 – ≤ 6.6.*
    • unaffected 6.12.105 – ≤ 6.12.*
    • unaffected 6.18.46 – ≤ 6.18.*
    • unaffected 7.1.10 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80910 badge
[![CVE-2026-80910](https://cveledger.app/badge/CVE-2026-80910.svg)](https://cveledger.app/cve/CVE-2026-80910)

Record last updated .