dbcve.org
Debian LinuxOperating system · Debian

CVE-2024-1151

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-11
Fix available
A fix is available. Upgrade to after 6.7.8 or later.
See remediation →
57/100
Remediation priority · Elevated
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
A vulnerability was reported in the Open vSwitch sub-component in the Linux Kernel. The flaw occurs when a recursive operation of code push recursively calls into the code block. The OVS module does not validate the stack depth, pushing too many frames and causing a stack overflow. As a result, this can lead to a crash or other related issues.

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-121

Data overflows a fixed-size buffer allocated on the stack, overwriting adjacent stack memory — including saved return addresses — which is the classic route to redirecting execution into attacker-supplied code. Crafted input is all it takes. Remediation is strict length checks, safe bounded string and memory functions, and modern stack-protection mitigations.

General guidance for the stack-based 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
Debian LinuxOperating system
Affected:= 10.0
FedoraOperating system
Affected:= 38= 39
Enterprise LinuxOperating system
Affected:= 8.0= 9.0
Linux KernelOperating system
Affected:<= 6.7.8= 6.8

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 a release after 6.7.8
Vendor patch lore.kernel.org →
Recommended fix High confidence

Linux Kernel 6.7.9 or later, or 6.8.1 or later; alternatively distributions like Debian 11+, Fedora 38+, RHEL 8.10+/9.4+

  1. 1. Identify current kernel version using 'uname -r' command
  2. 2. Check if running a vulnerable kernel version (<=6.7.8 or 6.8 without patch)
  3. 3. For Debian 10.0: Update to a newer Debian release (Debian 11 or 12) which includes patched kernel
  4. 4. For Fedora 38/39: Run 'dnf update kernel' to install latest patched kernel
  5. 5. For Enterprise Linux 8/9: Run 'dnf update kernel' or 'yum update kernel' to get latest kernel
  6. 6. After kernel update, reboot the system to load the new kernel: 'systemctl reboot'
  7. 7. Verify the fix is applied by checking kernel version 'uname -r' matches a fixed release
Caveat Kernel upgrades may require system reboot and could have compatibility issues with custom kernel modules or specific hardware drivers; test in staging environment before production deployment

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1151 — 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-1151 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