Answer in brief
CVE-2022-50015 records a Unknown severity vulnerability in ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=febf5da81ea80fa01e141e3ad35526865681418b <48945246cf802b9866f3a821103f1a7a196baf68 || >=febf5da81ea80fa01e141e3ad35526865681418b <499cc881b09c8283ab5e75b0d6d21cb427722161 | 48945246cf802b9866f3a821103f1a7a196baf68, 499cc881b09c8283ab5e75b0d6d21cb427722161 |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-50015 records a Unknown severity vulnerability in ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=febf5da81ea80fa01e141e3ad35526865681418b <48945246cf802b9866f3a821103f1a7a196baf68 || >=febf5da81ea80fa01e141e3ad35526865681418b <499cc881b09c8283ab5e75b0d6d21cb427722161 | 48945246cf802b9866f3a821103f1a7a196baf68, 499cc881b09c8283ab5e75b0d6d21cb427722161 |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.