{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.5-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "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:  \tret = snd_soc_enum_item_to_val(e, item[0]);  snd_soc_enum_item_to_val() indexes the heap-allocated e-\u003evalues[] array with that index (e-\u003evalues is set from a devm_kcalloc() of e-\u003eitems 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/20260609125735.CEB651F00893@smtp.kernel.org/",
  "id": "DEBIAN-CVE-2026-72415",
  "modified": "2026-09-14T16:47:40.149081325Z",
  "published": "2026-08-15T06:22:15.127Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-72415"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-72415"
  ]
}