LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27026: vmxnet3: Fix missing reserved tailroom

In the Linux kernel, the following vulnerability has been resolved: vmxnet3: Fix missing reserved tailroom Use rbi->len instead of rcd->len for non-dataring packet. Found issue: XDP_WARN: xdp_update_frame_from_buff(line:278): Driver BUG: missing reserved tailroom WARNING: CPU: 0 PID: 0 at net/core/xdp.c:586 xdp_warn+0xf/0x20 CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W O 6.5.1 #1 RIP: 0010:xdp_warn+0xf/0x20 ... ? xdp_warn+0xf/0x20 xdp_do_redirect+0x15f/0x1c0 vmxnet3_run_xdp+0x17a/0x400 [vmxnet3] vmxnet3_process_xdp+0xe4/0x760 [vmxnet3] ? vmxnet3_tq_tx_complete.isra.0+0x21e/0x2c0 [vmxnet3] vmxnet3_rq_rx_complete+0x7ad/0x1120 [vmxnet3] vmxnet3_poll_rx_only+0x2d/0xa0 [vmxnet3] __napi_poll+0x20/0x180 net_rx_action+0x177/0x390

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux vmxnet3 network-driver flaw can mishandle packet-buffer length information during XDP processing, leaving insufficient reserved space. The supplied CVSS score is 7.5 because network input may disrupt system availability without privileges or user interaction. The evidence does not indicate confidentiality or integrity impact.

Executive priority

Treat this as a high-priority availability issue after confirming vmxnet3 and XDP exposure. Accelerate remediation for critical network services, but avoid assuming every Linux host is vulnerable. There is no supplied evidence of active exploitation, data theft, or data modification.

Technical view

For a non-data-ring packet, vmxnet3 used rcd->len instead of rbi->len. This could produce an XDP “missing reserved tailroom” driver warning in the receive and redirect path. The supplied vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Stable-kernel commits are provided as resolutions.

Likely exposure

Prioritize Linux systems running affected kernel revisions where the vmxnet3 driver and XDP receive processing are in use. The bundle lists affected 6.6-and-later version data, but its normalized version list does not clearly express exact ranges. Confirm exposure against distribution or kernel-vendor advisories.

Exploitation context

The supplied record is not in CISA KEV, and no cited source establishes active exploitation or a public exploit. Network reachability and low attack complexity increase theoretical risk, but the bundle does not document a demonstrated attack, trigger packet, or real-world incident.

Researcher notes

The evidence shows a buffer-length accounting defect and an XDP warning trace, but supplies no CWE, reproducer, root-cause depth, or exploitation demonstration. Four stable-kernel commits are referenced. Exact affected-to-fixed range interpretation is incomplete in the normalized bundle, so validate commit inclusion through authoritative kernel or distribution metadata.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable stable vmxnet3 fix.
  • Consult the Linux or distribution advisory to map the fix to your exact kernel build.
  • Prioritize internet-facing or availability-critical systems confirmed to use vmxnet3 with XDP.
  • If updating is delayed, review vendor guidance for supported configuration-level mitigations.

Validation and detection

  • Record each system’s kernel build and compare it with official vendor guidance.
  • Verify whether the vmxnet3 driver is present and active on each candidate system.
  • Determine whether XDP processing is configured on vmxnet3 interfaces.
  • Search kernel logs for “missing reserved tailroom,” XDP_WARN, and vmxnet3 receive-path warnings.
  • After updating, confirm the running kernel includes the vendor-designated fix.
Prepared
Confidence
medium
Sources
6

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-27026 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
2ADP providers
5Source 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.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux54f00cce11786742bd11e5e68c3bf85e6dc048c9, 54f00cce11786742bd11e5e68c3bf85e6dc048c9, 54f00cce11786742bd11e5e68c3bf85e6dc048c9, 54f00cce11786742bd11e5e68c3bf85e6dc048c9unaffected
LinuxLinux6.6, 0, 6.6.23, 6.7.11, 6.8.2, 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.