CVE-2024-26927·Kernel vulnerability
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.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.8.2
- Published
- 2024-04-28
Affected versions
From: 6.8
Until: 6.8.2
Fixed in: 6.8.2
How to fix this CVE
Update your Linux kernel to version 6.8.2 or later to resolve this vulnerability in the Sound Open Firmware (SOF) driver. The fix adds proper boundary validation when parsing firmware data structures, preventing potential integer underflow and memory safety issues. Kernel updates should be applied promptly followed by a system reboot to activate the patched code.
sudo dnf update kernelDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your kernel version by running 'uname -r' and verify it is 6.8.2 or later
- Step 2: Confirm SOF audio driver is loaded by checking 'lsmod | grep snd_sof' to see if the vulnerable component is active
- Step 3: Review system logs for firmware parsing errors with 'journalctl -u kernel | grep -i "sof\|firmware\|bounds"' to identify potential exploitation attempts
- Step 4: Verify the patch is applied by checking 'cat /proc/version' and confirm kernel build includes the SOF bounds checking fix
FAQ
What is CVE-2024-26927?
This vulnerability affects the Linux kernel's Sound Open Firmware (SOF) driver, where insufficient bounds checking during firmware data parsing could allow integer underflow conditions to occur, potentially leading to memory corruption or denial of service.
Is CVE-2024-26927 being actively exploited?
No, this vulnerability is not listed on the CISA KEV catalog and has no publicly available exploits. However, it should still be patched promptly as it represents a kernel-level memory safety issue.
What versions of Kernel are affected by CVE-2024-26927?
Linux kernel versions 6.8 through 6.8.1 are vulnerable. The fix is available in kernel 6.8.2 and all subsequent stable releases.
How do I check if my server is vulnerable to CVE-2024-26927?
Run 'uname -r' to display your kernel version; if it reports 6.8.0 or 6.8.1, your system is vulnerable. Additionally, verify if SOF audio driver is in use with 'lsmod | grep snd_sof'.
Does Defensia detect CVE-2024-26927?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server running version 6.8.0 or 6.8.1, CVE-2024-26927 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/044e220667157fb9d59320341badec59cf45ba48
- https://git.kernel.org/stable/c/98f681b0f84cfc3a1d83287b77697679e0398306
- https://git.kernel.org/stable/c/9eeb8e1231f6450c574c1db979122e171a1813ab
- https://git.kernel.org/stable/c/ced7df8b3c5c4751244cad79011e86cf1f809153
- https://git.kernel.org/stable/c/d133d67e7e724102d1e53009c4f88afaaf3e167c
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-26927. Free for 1 server.
Get started free