dbcve.org
Linux KernelOperating system · Linux

CVE-2024-26927

HIGH · 8.4 CVSS v3.1 Published 2024-04-28
Fix available
A fix is available. Upgrade to 6.1.83 / 6.6.23 or later.
See remediation →
89/100
Remediation priority · High
No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-120

A fixed-size buffer is filled without checking the length of the incoming data, so it overflows into neighbouring memory. This is the classic overflow attackers use to overwrite return addresses and hijack execution. The fix is strict length checks and safe, bounded string and memory functions.

General guidance for the classic buffer overflow class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.19, < 6.1.83>= 6.2, < 6.6.23>= 6.7, < 6.7.11>= 6.8, < 6.8.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.1.83 / 6.6.23 / 6.7.11 or later
Fixed in 6.1.836.6.236.7.11
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux kernel >= 6.8.2 (or >= 6.6.23, >= 6.7.11, or >= 6.1.83 depending on your current kernel branch)

  1. Identify your current kernel version using 'uname -r' or 'cat /proc/version'
  2. Update your package repository metadata (e.g., 'apt-get update' for Debian/Ubuntu, 'dnf check-update' for Fedora/RHEL)
  3. Install the updated kernel package for your distribution. For Debian/Ubuntu: 'apt-get install linux-image-<version>' or 'apt-get upgrade'; For Fedora/RHEL: 'dnf install kernel-<version>' or 'dnf upgrade'; For Alpine: 'apk upgrade linux-lts' or similar
  4. Update bootloader configuration if necessary (e.g., update-grub, grub2-mkconfig)
  5. Reboot the system to load the new kernel: 'systemctl reboot' or 'reboot'
  6. Verify the kernel has been updated by running 'uname -r' and confirming the version is >= 6.8.2 (or >= 6.6.23, >= 6.7.11, or >= 6.1.83 depending on your base version)
Caveat Kernel upgrades may require rebuilding third-party kernel modules (like proprietary GPU drivers) and could introduce compatibility issues with older system utilities; ensure backups and test in non-production environments first

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26927 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-26927 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data