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-90068ASoC: dapm: Fix off-by-one check on the second enum channel

Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: dapm: Fix off-by-one check on the second enum channel The snd_soc_dapm_put_enum_double() rejects item[0] once it reaches e->items, but it lets item[1] be equal to it. Both go on to snd_soc_enum_item_to_val(), which indexes e->values with no bound of its own, so an enum with a value table reads one element past the end. The indexing arrived with the MUX consolidation, which relaxed the item[1] check in the same hunk. The value MUX handler it deleted used >= there, and the snd_soc_put_enum_double() in soc-ops.c still does. Only adav80x pairs a value table with two shifts, and its second channel looks accidental, but the control does report two values. Writing three into it reads off the end of adav80x_mux_values. The core catches that only under CONFIG_SND_CTL_INPUT_VALIDATION, which defaults off.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

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.22% · top 88% of all CVEs (13 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 3727b4968453dbab8fe18f979d67285eb6b66801 – < 57ab955bde747327fb2042516ae1b7192c30e881
    • affected 3727b4968453dbab8fe18f979d67285eb6b66801 – < 806fa4e1f2bf73c54bc4b6360790ecc69d095ca5
    • affected 3727b4968453dbab8fe18f979d67285eb6b66801 – < 496081b4edc1f6e662418831c5b14cddd8d7920c
    • affected 3727b4968453dbab8fe18f979d67285eb6b66801 – < faf539af1a595a26e5a081a4e512caee2bc2f4c5
    • affected 3727b4968453dbab8fe18f979d67285eb6b66801 – < 32fc048391112559c34cb88d13594546939a4cd6
    • affected 3727b4968453dbab8fe18f979d67285eb6b66801 – < 10a36512c21f861a03fba461a7ead09023df9c1b
    • affected 3727b4968453dbab8fe18f979d67285eb6b66801 – < 55126ef66298e43c69f192acebae8c7cc0022cf6
    • affected 3727b4968453dbab8fe18f979d67285eb6b66801 – < 14511c9b54ceeeef487409d73947c89ee8563590
  • Linux · Linux

    • affected 3.15
    • unaffected < 3.15
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .