CVE-2026-72303 (GCVE-0-2026-72303)

Vulnerability from cvelistv5 – Published: 2026-08-15 05:55 – Updated: 2026-10-16 18:55
VLAI
Title
ASoC: SOF: ipc4-control: Validate notification payload size
Summary
In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc4-control: Validate notification payload size Validate MODULE_NOTIFICATION payload length before reading bytes/channel data in control update handling.
SSVC
Exploitation: none Automatable: no Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-10-16 18:46 UTC
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: 2a28b5240f2b328495c6565d277f438dbc583d61 , < c29f5b4498894aebb2f87b1a29bb320e2f9348f9 (git)
Affected: 2a28b5240f2b328495c6565d277f438dbc583d61 , < 5bdfeccb7fbf6e000fc783cd8412732e67c1ad0c (git)
Create a notification for this product.
Linux Linux Affected: 7.0
Unaffected: 0 , < 7.0 (semver)
Unaffected: 7.1.5 , ≤ 7.1.* (semver)
Unaffected: 7.2 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-72303",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-10-16T18:46:16.232770Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-10-16T18:55:16.397Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "sound/soc/sof/ipc4-control.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "c29f5b4498894aebb2f87b1a29bb320e2f9348f9",
              "status": "affected",
              "version": "2a28b5240f2b328495c6565d277f438dbc583d61",
              "versionType": "git"
            },
            {
              "lessThan": "5bdfeccb7fbf6e000fc783cd8412732e67c1ad0c",
              "status": "affected",
              "version": "2a28b5240f2b328495c6565d277f438dbc583d61",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "sound/soc/sof/ipc4-control.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.0"
            },
            {
              "lessThan": "7.0",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.5",
                  "versionStartIncluding": "7.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "7.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: ipc4-control: Validate notification payload size\n\nValidate MODULE_NOTIFICATION payload length before reading\nbytes/channel data in control update handling."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The flaw is reached when the on-chip SOF DSP delivers IPC4 MODULE_NOTIFICATION messages to the host via mailbox/IRQ; exploitation requires local access to a SOF-equipped system using the ALSA control interface, not remote network delivery.\nAC:L - A local attacker can repeatedly issue ALSA control ioctls that cause the DSP to emit control-change notifications; no race or victim state beyond attacker-driven audio IPC is needed to supply inconsistent num_elems versus event_data_size.\nPR:L - Only an unprivileged local user able to open ALSA control devices on SOF hardware (typical on Intel laptop/desktop audio stacks) is required; root or init-namespace capabilities are not needed to drive the vulnerable notification path.\nUI:N - No action by a separate victim is required; the attacker triggers DSP notifications through their own ALSA control operations and the kernel processes malformed firmware payloads automatically.\nS:U - Impact stays within the host kernel audio subsystem on the same machine; heap disclosure or control-cache corruption does not cross VM, container, or IOMMU boundaries into another security authority.\nC:H - Missing payload-length validation lets num_elems drive memcpy and chanv parsing beyond the kmalloc IPC notification buffer, causing out-of-bounds kernel heap reads that can disclose adjacent memory contents.\nI:H - Untrusted num_elems values cause kernel memory corruption by copying out-of-bounds firmware/heap bytes into control caches via memcpy and chanv updates, providing bounded but attacker-influenced kernel writes usable in further exploitation.\nA:H - Large num_elems values trigger extensive out-of-bounds accesses during IRQ-threaded IPC notification handling, which can provoke KASAN faults, unhandled page faults, kernel oops, or panic under realistic SOF workloads."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:42:35.730Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/c29f5b4498894aebb2f87b1a29bb320e2f9348f9"
        },
        {
          "url": "https://git.kernel.org/stable/c/5bdfeccb7fbf6e000fc783cd8412732e67c1ad0c"
        }
      ],
      "title": "ASoC: SOF: ipc4-control: Validate notification payload size",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-72303",
    "datePublished": "2026-08-15T05:55:21.667Z",
    "dateReserved": "2026-08-09T03:40:39.918Z",
    "dateUpdated": "2026-10-16T18:55:16.397Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-72303",
      "date": "2026-11-19",
      "epss": "0.00165",
      "percentile": "0.05815"
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-05T22:35:13+00:00",
      "cve": "CVE-2026-72303",
      "id": "CVE-2026-72303",
      "initial_release_date": "2026-08-15T00:00:00+00:00",
      "product_status:known_affected": "108",
      "product_status:known_not_affected": "92",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: ASoC: SOF: ipc4-control: Validate notification payload size",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-72303.json",
      "version": "3"
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-72303",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "total"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-10-16T18:46:16.232770Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-10-16T18:46:16.816Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "defaultStatus": "unaffected",
              "product": "Linux",
              "programFiles": [
                "sound/soc/sof/ipc4-control.c"
              ],
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "vendor": "Linux",
              "versions": [
                {
                  "lessThan": "c29f5b4498894aebb2f87b1a29bb320e2f9348f9",
                  "status": "affected",
                  "version": "2a28b5240f2b328495c6565d277f438dbc583d61",
                  "versionType": "git"
                },
                {
                  "lessThan": "5bdfeccb7fbf6e000fc783cd8412732e67c1ad0c",
                  "status": "affected",
                  "version": "2a28b5240f2b328495c6565d277f438dbc583d61",
                  "versionType": "git"
                }
              ]
            },
            {
              "defaultStatus": "affected",
              "product": "Linux",
              "programFiles": [
                "sound/soc/sof/ipc4-control.c"
              ],
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "vendor": "Linux",
              "versions": [
                {
                  "status": "affected",
                  "version": "7.0"
                },
                {
                  "lessThan": "7.0",
                  "status": "unaffected",
                  "version": "0",
                  "versionType": "semver"
                },
                {
                  "lessThanOrEqual": "7.1.*",
                  "status": "unaffected",
                  "version": "7.1.5",
                  "versionType": "semver"
                },
                {
                  "lessThanOrEqual": "*",
                  "status": "unaffected",
                  "version": "7.2",
                  "versionType": "original_commit_for_fix"
                }
              ]
            }
          ],
          "cpeApplicability": [
            {
              "nodes": [
                {
                  "cpeMatch": [
                    {
                      "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                      "versionEndExcluding": "7.1.5",
                      "versionStartIncluding": "7.0",
                      "vulnerable": true
                    },
                    {
                      "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                      "versionEndExcluding": "7.2",
                      "versionStartIncluding": "7.0",
                      "vulnerable": true
                    }
                  ],
                  "negate": false,
                  "operator": "OR"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: ipc4-control: Validate notification payload size\n\nValidate MODULE_NOTIFICATION payload length before reading\nbytes/channel data in control update handling."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 7.8,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
                "version": "3.1"
              },
              "scenarios": [
                {
                  "lang": "en",
                  "value": "AV:L - The flaw is reached when the on-chip SOF DSP delivers IPC4 MODULE_NOTIFICATION messages to the host via mailbox/IRQ; exploitation requires local access to a SOF-equipped system using the ALSA control interface, not remote network delivery.\nAC:L - A local attacker can repeatedly issue ALSA control ioctls that cause the DSP to emit control-change notifications; no race or victim state beyond attacker-driven audio IPC is needed to supply inconsistent num_elems versus event_data_size.\nPR:L - Only an unprivileged local user able to open ALSA control devices on SOF hardware (typical on Intel laptop/desktop audio stacks) is required; root or init-namespace capabilities are not needed to drive the vulnerable notification path.\nUI:N - No action by a separate victim is required; the attacker triggers DSP notifications through their own ALSA control operations and the kernel processes malformed firmware payloads automatically.\nS:U - Impact stays within the host kernel audio subsystem on the same machine; heap disclosure or control-cache corruption does not cross VM, container, or IOMMU boundaries into another security authority.\nC:H - Missing payload-length validation lets num_elems drive memcpy and chanv parsing beyond the kmalloc IPC notification buffer, causing out-of-bounds kernel heap reads that can disclose adjacent memory contents.\nI:H - Untrusted num_elems values cause kernel memory corruption by copying out-of-bounds firmware/heap bytes into control caches via memcpy and chanv updates, providing bounded but attacker-influenced kernel writes usable in further exploitation.\nA:H - Large num_elems values trigger extensive out-of-bounds accesses during IRQ-threaded IPC notification handling, which can provoke KASAN faults, unhandled page faults, kernel oops, or panic under realistic SOF workloads."
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-17T05:42:35.730Z",
            "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "shortName": "Linux"
          },
          "references": [
            {
              "url": "https://git.kernel.org/stable/c/c29f5b4498894aebb2f87b1a29bb320e2f9348f9"
            },
            {
              "url": "https://git.kernel.org/stable/c/5bdfeccb7fbf6e000fc783cd8412732e67c1ad0c"
            }
          ],
          "title": "ASoC: SOF: ipc4-control: Validate notification payload size",
          "x_generator": {
            "engine": "bippy-1.2.0"
          }
        }
      },
      "cveMetadata": {
        "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "assignerShortName": "Linux",
        "cveId": "CVE-2026-72303",
        "datePublished": "2026-08-15T05:55:21.667Z",
        "dateReserved": "2026-08-09T03:40:39.918Z",
        "dateUpdated": "2026-10-16T18:55:16.397Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.