LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash affected systems if Intel SOF HDA audio firmware sends an IPC reply before the expected firmware-ready signal. The sources describe a NULL pointer dereference, not data theft or remote takeover. Business urgency depends on whether your Linux fleet uses the affected kernel range and this audio firmware path.

Executive priority

Track as a targeted kernel reliability issue. Prioritize patching where Linux endpoints or embedded devices depend on Intel SOF audio firmware. Without evidence of active exploitation or a CVSS score, this should not outrank confirmed exploited vulnerabilities unless critical affected systems are present.

Technical view

In the ASoC SOF Intel hda-ipc path, reply_data is allocated only after FW_READY. A malformed or faulty firmware sequence can send a reply first, causing NULL pointer dereference. The condition is described for IPC4 firmware and also present for IPC3. Stable kernel commits are referenced as fixes.

Likely exposure

Exposure appears limited to Linux systems in the affected kernel range using the Intel SOF HDA IPC audio firmware path. The provided affected data names Linux kernel versions including 5.2 through 5.19.4 and 6.0, but distribution-specific backports are not identified in the bundle.

Exploitation context

The bundle does not show CISA KEV listing, active exploitation, public exploit code, or remote attack details. The described trigger involves unexpected firmware message ordering before FW_READY. Treat exploitation status as unconfirmed and avoid assuming internet-facing risk from these sources alone.

Researcher notes

The core evidence is the kernel fix description: reply processing before FW_READY can dereference unallocated reply_data. The bundle lacks CVSS, CWE, exploitability analysis, and distro-specific advisories. Validation should focus on code presence, kernel lineage, and whether deployed systems exercise this Intel SOF HDA IPC path.

Mitigation direction

  • Update affected Linux kernels to versions containing the referenced stable fixes.
  • Check your Linux distribution advisories for backported fixes and supported package versions.
  • Prioritize systems using Intel SOF HDA audio firmware paths.
  • If no vendor package is available, follow kernel or distribution guidance before custom patching.

Validation and detection

  • Inventory Linux kernel versions across endpoints, servers, and embedded systems.
  • Identify systems using Intel SOF HDA audio support or related firmware paths.
  • Confirm whether vendor kernel packages include the two referenced stable commits.
  • Review kernel logs for SOF firmware boot or IPC ordering errors.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50015 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6e9cde974863dc9d9c6cdb178f625e410c5be3d0, 6e9cde974863dc9d9c6cdb178f625e410c5be3d0unaffected
LinuxLinux5.2, 0, 5.19.4, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.