Linux Kernel ASoC SDCA ge_put_enum_double item out-of-bounds

Summaryinfo

A vulnerability classified as problematic was found in Linux Kernel. This vulnerability affects the function ge_put_enum_double of the component ASoC SDCA. The manipulation of the argument item results in out-of-bounds. This vulnerability is known as CVE-2026-72415. Attacking locally is a requirement. No exploit is available.

Detailsinfo

A vulnerability was found in Linux Kernel (version unknown). It has been classified as problematic. Affected is the function ge_put_enum_double of the component ASoC SDCA. The manipulation of the argument item with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: ASoC: SDCA: Validate written enum value in ge_put_enum_double() ge_put_enum_double() passes the user-supplied enumeration index item[0] to snd_soc_enum_item_to_val() without checking it against the number of items in the enum: ret = snd_soc_enum_item_to_val(e, item[0]); snd_soc_enum_item_to_val() indexes the heap-allocated e->values[] array with that index (e->values is set from a devm_kcalloc() of e->items entries), so a control write with an out-of-range item[0] reads past the end of the values buffer. The bounds check in snd_soc_dapm_put_enum_double() only runs afterwards, so it does not prevent the read here. Reject an out-of-range item before using it, matching the other enum put handlers. This issue was pointed out by the Sashiko AI review bot while reviewing a related enum-validation series: https://lore.kernel.org/all/[email protected]/

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-72415 since 08/09/2026. The exploitability is told to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available.

Applying the patch 33387bf9bb6116a0429f823f8dab3accf8f8e09c is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion