# ALEA-2022:1551: alsa-sof-firmware bug fix and enhancement update

> This update provides bug fixes and enhancements for Intel SOF firmware, with no specific security vulnerability details provided.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 26 Apr 2022

## What is ALEA-2022:1551?

ALEA-2022:1551 is a vulnerability in alsa-sof-firmware, published on 26 Apr 2022. 

### Official description

The alsa-sof-firmware package contains firmware binaries for the Sound Open Firmware project.

Bug Fix(es) and Enhancement(s):

* Update Intel SOF firmware to 1.9 (BZ#2044420)

## Which versions are affected by ALEA-2022:1551?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `alsa-sof-firmware` | AlmaLinux:8 | All versions | 1.9.3-1.el8_5 |
| `alsa-sof-firmware-debug` | AlmaLinux:8 | All versions | 1.9.3-1.el8_5 |

## How do I fix ALEA-2022:1551?

Upgrade to a fixed version.

## Is ALEA-2022:1551 being exploited?

There is no known exploitation of ALEA-2022:1551 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALEA-2022:1551 and fix it if it is affected.

What it is: ALEA-2022:1551 is a vulnerability in alsa-sof-firmware, published on 26 Apr 2022. 
Exploitation: There is no known exploitation of ALEA-2022:1551 in the wild and no public exploit code.

Affected product: alsa-sof-firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/ALEA-2022-1551/ (Markdown: https://insights.sbomify.com/ALEA-2022-1551/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALEA-2022:1551

---
From sbomify Insights: https://insights.sbomify.com/ALEA-2022-1551/
Summaries are generated and may contain mistakes; the official description above is the record.