Skip to content
Heist/ feed
Back to feed
UnratedFix available

ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot It is not yet clear, but it is possible to create a firmware so broken that it will send a reply message before a FW_READY message (it is not yet clear if FW_READY will arrive later). Since the reply_data is allocated only after the FW_READY message, this will lead to a NULL pointer dereference if not filtered out. The issue was reported with IPC4 firmware but the same condition is present for IPC3.

Products
Kernel
Affected versions
Not specified
Fixed versions
5.19.4
CVEs
CVE-2022-50015
Confirmed fixed CVEs
Not specified
Updated in this feed
6 Nov 2026, 01:49 UTC · Revision 1

Source evidence

ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot

core-osv · Original source

Published 18 Jun 2025, 11:01 UTC

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot It is not yet clear, but it is possible to create a firmware so broken that it will send a reply message before a FW_READY message (it is not yet clear if FW_READY will arrive later). Since the reply_data is allocated only after the FW_READY message, this will lead to a NULL pointer dereference if not filtered out. The issue was reported with IPC4 firmware but the same condition is present for IPC3.

osv:CVE-2022-50015

Kernel

Fixed versions: 5.19.4

Complete source record
{
  "id": "46843841f7d24fa759df12270516373f3e672a49f84244385c22c7d4b5283de0",
  "url": "https://osv.dev/vulnerability/CVE-2022-50015",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot It is not yet clear, but it is possible to create a firmware so broken that it will send a reply message before a FW_READY message (it is not yet clear if FW_READY will arrive later). Since the reply_data is allocated only after the FW_READY message, this will lead to a NULL pointer dereference if not filtered out. The issue was reported with IPC4 firmware but the same condition is present for IPC3.",
    "evidence": "osv:CVE-2022-50015",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "5.19.4",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2022-50015",
      "aliases": [
        "CVE-2022-50015"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "febf5da81ea80fa01e141e3ad35526865681418b"
                },
                {
                  "fixed": "48945246cf802b9866f3a821103f1a7a196baf68"
                },
                {
                  "fixed": "499cc881b09c8283ab5e75b0d6d21cb427722161"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50015.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.16.0"
                },
                {
                  "fixed": "5.19.4"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50015.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:46.290002792Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/48945246cf802b9866f3a821103f1a7a196baf68",
        "https://git.kernel.org/stable/c/499cc881b09c8283ab5e75b0d6d21cb427722161",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50015.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2022-50015",
        "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/2022/50xxx/CVE-2022-50015.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2022-50015",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 514006,
  "published_at": "2025-06-18T11:01:19.516+00:00"
}