Vulnerability-Lookup

GHSA-5RGW-CXHJ-RMHQ

Vulnerability from github – Published: 2026-08-27 15:31 – Updated: 2026-08-27 15:31

Details

In the Linux kernel, the following vulnerability has been resolved:

ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout

Ignore IPC errors for pipeline state change if the firmware state is crashed or the IPC has timed out.

If the firmware has crashed the kernel still needs to go through the state changes to reset its internal to be able to correctly work the next time the DSP is booted up.

The case with IPC timeout is a bit more problematic, but it has been rootcaused to be the result of system scheduling blockage and the firmware did actually received and handled the message, but the reply handling got blocked by issues outside of the SOF stack. So far the best way to handle this is to continue with setting the state.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-80581"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-26T15:17:14Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout\n\nIgnore IPC errors for pipeline state change if the firmware state is\ncrashed or the IPC has timed out.\n\nIf the firmware has crashed the kernel still needs to go through the state\nchanges to reset its internal to be able to correctly work the next time\nthe DSP is booted up.\n\nThe case with IPC timeout is a bit more problematic, but it has been\nrootcaused to be the result of system scheduling blockage and the firmware\ndid actually received and handled the message, but the reply handling got\nblocked by issues outside of the SOF stack.\nSo far the best way to handle this is to continue with setting the state.",
  "id": "GHSA-5rgw-cxhj-rmhq",
  "modified": "2026-08-27T15:31:33Z",
  "published": "2026-08-27T15:31:33Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80581"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/17661c67b206612cb3ba65d5ae726cd2015d0a53"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4931c09d83877dc350106bae745321c3f295129b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/6b512a5330ef1a41db7aff4b80c4e952b8d52f17"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/f2435a46dfa1a5693cf2664afd022db66ee58121"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-80581 (GCVE-0-2026-80581)

Vulnerability from cvelistv5 – Published: 2026-08-26 14:37 – Updated: 2026-08-27 12:40

Title

ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout

Summary

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout Ignore IPC errors for pipeline state change if the firmware state is crashed or the IPC has timed out. If the firmware has crashed the kernel still needs to go through the state changes to reset its internal to be able to correctly work the next time the DSP is booted up. The case with IPC timeout is a bit more problematic, but it has been rootcaused to be the result of system scheduling blockage and the firmware did actually received and handled the message, but the reply handling got blocked by issues outside of the SOF stack. So far the best way to handle this is to continue with setting the state.

Severity

No CVSS data available.

Assigner

Linux mitre root

References

4 references

URL	Tags
https://git.kernel.org/stable/c/4931c09d83877dc35…
https://git.kernel.org/stable/c/f2435a46dfa1a5693…
https://git.kernel.org/stable/c/6b512a5330ef1a41d…
https://git.kernel.org/stable/c/17661c67b206612cb…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 3cac6eebea9b4bc5f041e157e45c76e212ad6759 , < 4931c09d83877dc350106bae745321c3f295129b (git) Affected: c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 , < f2435a46dfa1a5693cf2664afd022db66ee58121 (git) Affected: c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 , < 6b512a5330ef1a41db7aff4b80c4e952b8d52f17 (git) Affected: c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 , < 17661c67b206612cb3ba65d5ae726cd2015d0a53 (git) Affected: d153e8b154f9746ac969c85a4e6474760453647c (git) Affected: 6.6.23 , < 6.6.154 (semver) Affected: 6.7.11 , < 6.8 (semver)
Linux	Linux	Affected: 6.8 Unaffected: 0 , < 6.8 (semver) Unaffected: 6.6.154 , ≤ 6.6.* (semver) Unaffected: 6.18.46 , ≤ 6.18.* (semver) Unaffected: 7.1.10 , ≤ 7.1.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "sound/soc/sof/ipc4-pcm.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "4931c09d83877dc350106bae745321c3f295129b",
              "status": "affected",
              "version": "3cac6eebea9b4bc5f041e157e45c76e212ad6759",
              "versionType": "git"
            },
            {
              "lessThan": "f2435a46dfa1a5693cf2664afd022db66ee58121",
              "status": "affected",
              "version": "c40aad7c81e5fba34b70123ed7ce3397fa62a4d2",
              "versionType": "git"
            },
            {
              "lessThan": "6b512a5330ef1a41db7aff4b80c4e952b8d52f17",
              "status": "affected",
              "version": "c40aad7c81e5fba34b70123ed7ce3397fa62a4d2",
              "versionType": "git"
            },
            {
              "lessThan": "17661c67b206612cb3ba65d5ae726cd2015d0a53",
              "status": "affected",
              "version": "c40aad7c81e5fba34b70123ed7ce3397fa62a4d2",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "d153e8b154f9746ac969c85a4e6474760453647c",
              "versionType": "git"
            },
            {
              "lessThan": "6.6.154",
              "status": "affected",
              "version": "6.6.23",
              "versionType": "semver"
            },
            {
              "lessThan": "6.8",
              "status": "affected",
              "version": "6.7.11",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "sound/soc/sof/ipc4-pcm.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.8"
            },
            {
              "lessThan": "6.8",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.154",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.46",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.10",
              "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": "6.6.154",
                  "versionStartIncluding": "6.6.23",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.46",
                  "versionStartIncluding": "6.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.10",
                  "versionStartIncluding": "6.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "6.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "6.7.11",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout\n\nIgnore IPC errors for pipeline state change if the firmware state is\ncrashed or the IPC has timed out.\n\nIf the firmware has crashed the kernel still needs to go through the state\nchanges to reset its internal to be able to correctly work the next time\nthe DSP is booted up.\n\nThe case with IPC timeout is a bit more problematic, but it has been\nrootcaused to be the result of system scheduling blockage and the firmware\ndid actually received and handled the message, but the reply handling got\nblocked by issues outside of the SOF stack.\nSo far the best way to handle this is to continue with setting the state."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-27T12:40:20.576Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/4931c09d83877dc350106bae745321c3f295129b"
        },
        {
          "url": "https://git.kernel.org/stable/c/f2435a46dfa1a5693cf2664afd022db66ee58121"
        },
        {
          "url": "https://git.kernel.org/stable/c/6b512a5330ef1a41db7aff4b80c4e952b8d52f17"
        },
        {
          "url": "https://git.kernel.org/stable/c/17661c67b206612cb3ba65d5ae726cd2015d0a53"
        }
      ],
      "title": "ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-80581",
    "datePublished": "2026-08-26T14:37:38.510Z",
    "dateReserved": "2026-08-26T14:34:25.769Z",
    "dateUpdated": "2026-08-27T12:40:20.576Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

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.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

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.