ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s SOF Intel hda-ipc code can dereference a NULL pointer if firmware sends an IPC reply before the FW_READY message. This condition was reported with IPC4 firmware and is also present for IPC3. The input does not establish an attacker path, authentication requirement, or user interaction requirement.
Engineers running the Linux kernel with SOF Intel hda-ipc should check their deployments; affected versions are not specified.