LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27395: net: openvswitch: Fix Use-After-Free in ovs_ct_exit

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel memory-safety flaw affects Open vSwitch connection-tracking cleanup. A low-privileged local attacker may be able to trigger serious confidentiality, integrity, or availability impact. It is not described as remotely exploitable, and the supplied evidence does not show active exploitation.

Executive priority

Treat this as a high-priority kernel update, especially on multi-user or multi-tenant systems using Open vSwitch connection tracking. Accelerate remediation where untrusted users can execute local code. It does not warrant the same response as an unauthenticated internet-facing critical vulnerability based on the supplied evidence.

Technical view

During ovs_ct_limit_exit traversal, kfree_rcu may complete outside an RCU read-side critical section, allowing a key to be freed while still being traversed. The correction uses hlist_for_each_entry_safe. The supplied CVSS 3.1 score is 7.8: local access, low complexity, low privileges, no user interaction, and high impact across confidentiality, integrity, and availability.

Likely exposure

Exposure concerns Linux systems containing the affected Open vSwitch connection-tracking code. The bundle identifies affected boundaries spanning kernel 4.18 through 6.9, but its normalized version list does not preserve precise range operators. Confirm exposure using distribution or appliance advisories and backport information rather than version numbers alone.

Exploitation context

The KEV flag is false, and the supplied sources provide no evidence of active exploitation or public exploit availability. The CVSS vector requires local access and low privileges, with low complexity and no user interaction. This is principally a post-access risk rather than unauthenticated remote compromise.

Researcher notes

The root cause and corrective traversal change are explicit. Exact affected ranges are less certain because the supplied version data appears normalized, includes a zero value, and loses range semantics. Review the upstream stable commits and vendor backports before declaring a specific build vulnerable or fixed. No supplied evidence establishes practical exploitation.

Mitigation direction

  • Inventory Linux systems using Open vSwitch connection tracking.
  • Apply vendor-supported kernel updates containing the referenced upstream fix or an equivalent backport.
  • Prioritize systems permitting untrusted or low-privileged local code execution.
  • If updates are delayed, consult the relevant vendor for supported mitigations; none are specified in the bundle.

Validation and detection

  • Identify each deployed kernel package, running version, and distribution backport status.
  • Determine whether Open vSwitch connection-tracking functionality is present and operational.
  • Confirm the running kernel includes a referenced stable fix or vendor-equivalent backport.
  • After updating, verify the system booted into the vendor-designated fixed kernel.
  • Review kernel telemetry for ovs_ct-related faults, while recognizing that no faults do not prove safety.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-27395 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
3ADP providers
13Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-27395Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux11efd5cb04a184eea4f57b68ea63dddd463158d1, 11efd5cb04a184eea4f57b68ea63dddd463158d1, 11efd5cb04a184eea4f57b68ea63dddd463158d1, 11efd5cb04a184eea4f57b68ea63dddd463158d1, 11efd5cb04a184eea4f57b68ea63dddd463158d1, 11efd5cb04a184eea4f57b68ea63dddd463158d1, 11efd5cb04a184eea4f57b68ea63dddd463158d1, 11efd5cb04a184eea4f57b68ea63dddd463158d1unaffected
LinuxLinux4.18, 0, 4.19.313, 5.4.275, 5.10.216, 5.15.158, 6.1.90, 6.6.30, 6.8.9, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.