dbcve.org
Linux KernelOperating system · Linux

CVE-2024-27395

HIGH · 7.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 4.19.313 / 5.4.275 or later.
See remediation →
80/100
Remediation priority · High
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: net: openvswitch: Fix Use-After-Free in ovs_ct_exit Since kfree_rcu, which is called in the hlist_for_each_entry_rcu traversal of ovs_ct_limit_exit, is not part of the RCU read critical section, it is possible that the RCU grace period will pass during the traversal and the key will be free. To prevent this, it should be changed to hlist_for_each_entry_safe.

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

Memory is used after it has been freed, so its contents — now potentially attacker-controlled — drive the program's behaviour. With careful heap grooming this becomes code execution. The fix requires disciplined ownership of memory and often a targeted rework of the object lifecycle.

General guidance for the use after free 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:>= 4.18, < 4.19.313>= 4.20, < 5.4.275>= 5.5, < 5.10.216>= 5.11, < 5.15.158>= 5.16, < 6.1.90>= 6.2, < 6.6.30>= 6.7, < 6.8.9= 6.9
Debian LinuxOperating system
Affected:= 10.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 4.19.313 / 5.4.275 / 5.10.216 or later
Fixed in 4.19.3135.4.2755.10.216
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux Kernel 4.19.313+, 5.4.275+, 5.10.216+, or 5.15.158+ (depending on your branch); Debian 10 users should migrate to Debian 11/12

  1. 1. Identify the currently running kernel version using 'uname -r'
  2. 2. Determine which kernel branch your system is running (e.g., 4.19.x, 5.4.x, 5.10.x, or 5.15.x)
  3. 3. For Debian 10.0 systems, upgrade to a kernel version that includes the fix; Debian 10 (Buster) reached end-of-life in June 2022, so consider upgrading to Debian 11 or 12 which include newer kernels
  4. 4. For upstream kernel users, upgrade to the appropriate fixed version: 4.19.313 or later for 4.19.y, 5.4.275 or later for 5.4.y, 5.10.216 or later for 5.10.y, or 5.15.158 or later for 5.15.y
  5. 5. Apply the vendor patch from commit 2db9a8c0a01fa1c762c1e61a13c212c492752994 if building a custom kernel: https://git.kernel.org/stable/c/2db9a8c0a01fa1c762c1e61a13c212c492752994
  6. 6. After kernel upgrade, reboot the system to load the fixed kernel
Caveat Kernel upgrade requires system reboot and may require recompilation of third-party kernel modules; Debian 10 reached end-of-life and users should migrate to a supported Debian release

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-27395 — 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-27395 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