ASoC: dapm: Fix off-by-one check on the second enum channel
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.270, 5.15.221, 6.1.188, 6.12.110, 6.18.52, 6.6.157, 7.2.6
- CVEs
- CVE-2026-90068
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 01:59 UTC · Revision 1
Source evidence
ASoC: dapm: Fix off-by-one check on the second enum channel
core-osv · Original sourcePublished 17 Sept 2026, 16:05 UTC
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.
osv:CVE-2026-90068
Kernel
Fixed versions: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
Complete source record
{
"id": "80cdc4644d10c27adb198fe909100081175e04f42a5dd22c4589dc85306a0542",
"url": "https://osv.dev/vulnerability/CVE-2026-90068",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "ASoC: dapm: Fix off-by-one check on the second enum channel",
"summary": "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.",
"evidence": "osv:CVE-2026-90068",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.270",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.221",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.188",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.157",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.110",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.52",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-90068",
"aliases": [
"CVE-2026-90068"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "3727b4968453dbab8fe18f979d67285eb6b66801"
},
{
"fixed": "57ab955bde747327fb2042516ae1b7192c30e881"
},
{
"fixed": "806fa4e1f2bf73c54bc4b6360790ecc69d095ca5"
},
{
"fixed": "496081b4edc1f6e662418831c5b14cddd8d7920c"
},
{
"fixed": "faf539af1a595a26e5a081a4e512caee2bc2f4c5"
},
{
"fixed": "32fc048391112559c34cb88d13594546939a4cd6"
},
{
"fixed": "10a36512c21f861a03fba461a7ead09023df9c1b"
},
{
"fixed": "55126ef66298e43c69f192acebae8c7cc0022cf6"
},
{
"fixed": "14511c9b54ceeeef487409d73947c89ee8563590"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90068.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.15.0"
},
{
"fixed": "5.10.270"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.221"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.188"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.157"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.110"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.52"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90068.json"
}
}
],
"modified": "2026-10-28T02:30:48.868678004Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/10a36512c21f861a03fba461a7ead09023df9c1b",
"https://git.kernel.org/stable/c/14511c9b54ceeeef487409d73947c89ee8563590",
"https://git.kernel.org/stable/c/32fc048391112559c34cb88d13594546939a4cd6",
"https://git.kernel.org/stable/c/496081b4edc1f6e662418831c5b14cddd8d7920c",
"https://git.kernel.org/stable/c/55126ef66298e43c69f192acebae8c7cc0022cf6",
"https://git.kernel.org/stable/c/57ab955bde747327fb2042516ae1b7192c30e881",
"https://git.kernel.org/stable/c/806fa4e1f2bf73c54bc4b6360790ecc69d095ca5",
"https://git.kernel.org/stable/c/faf539af1a595a26e5a081a4e512caee2bc2f4c5",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90068.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-90068",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90068.json"
}
},
"related_cves": [
{
"value": "CVE-2026-90068",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 517182,
"published_at": "2026-09-17T16:05:50.251+00:00"
}