---
id: CVE-2022-50016
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  ASoC: SOF: Intel: cnl: 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 m…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  ASoC: SOF: Intel: cnl: 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 m…
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-476
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 5.2, < 5.19.4'
patched:
  - linux_kernel 5.19.4
published: '2025-06-18'
updated: '2026-08-15'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2022-50016'
references:
  - url: 'https://git.kernel.org/stable/c/230f646085d17a008b609eb8fe8befb8811868f0'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/acacd9eefd0def5a83244d88e5483b5f38ee7287'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.0021
epssPercentile: 0.0991
ingestedAt: '2026-08-15T13:26:44.999Z'
---

## Overview

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

ASoC: SOF: Intel: cnl: 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.

## Affected

- `linux_kernel >= 5.2, < 5.19.4`

## Remediation

Upgrade past the affected range:

- `linux_kernel 5.19.4`