Skip to content
Noroxi
CVE-2025-37799· NVD / CVE Program· CNA Linux

vmxnet3: Fix malformed packet sizing in vmxnet3_process_xdp

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 33e131a10459d16f181c8184d3f17f1c318c7002, 4c2227656d9003f4d77afc76f34dd81b95e4c2c4, 6.6.89.
  • Severity is disputed: the assigning authority (CNA) scores it 8.6, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 33e131a10459d16f181c8184d3f17f1c318c7002, 4c2227656d9003f4d77afc76f34dd81b95e4c2c4, 6.6.89 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: vmxnet3: Fix malformed packet sizing in vmxnet3_process_xdp vmxnet3 driver's XDP handling is buggy for packet sizes using ring0 (that is, packet sizes between 128 - 3k bytes). We noticed MTU-related connectivity issues with Cilium's service load- balancing in case of vmxnet3 as NIC underneath. A simple curl to a HTTP backend service where the XDP LB was doing IPIP encap led to overly large packet sizes but only for *some* of the packets (e.g. HTTP GET request) while others (e.g. the prior TCP 3WHS) looked completely fine on the wire. In fact, the pcap recording on the backend node actually revealed that the node with the XDP LB was leaking uninitialized kernel data onto the wire for the affected packets, for example, while the packets should have been 152 bytes their actual size was 1482 bytes, so the remainder after 152 bytes was padded with whatever other data was in that page at the time (e.g. we saw user/payload data from prior processed packets). We only noticed this through an MTU issue, e.g. when the XDP LB node and the backend node both had the same MTU (e.g. 1500) then the curl request got dropped on the backend node's NIC given the packet was too large even though the IPIP-encapped packet normally would never even come close to the MTU limit. Lowering the MTU on the XDP LB (e.g. 1480) allowed to let the curl request succeed (which also indicates that the kernel ignored the padding, and thus the issue wasn't very user-visible). Commit e127ce7699c1 ("vmxnet3: Fix missing reserved tailroom") was too eager to also switch xdp_prepare_buff() from rcd->len to rbi->len. It really needs to stick to rcd->len which is the actual packet length from the descriptor. The latter we also feed into vmxnet3_process_xdp_small(), by the way, and it indicates the correct length needed to initialize the xdp->{data,data_end} parts. For e127ce7699c1 ("vmxnet3: Fix missing reserved tailroom") the relevant part was adapting xdp_init_buff() to address the warning given the xdp_data_hard_end() depends on xdp->frame_sz. With that fixed, traffic on the wire looks good again.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 3, 2025
Updated
Aug 5, 2026
EPSS
0.3% · 28th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CNA vs NVD score

NVD
5.5
CNA · Linux
8.6
3.1 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-37799

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.6.23 and later · before 6.6.89
  • linux linux kernel6.7.11 and later · before 6.8
  • linux linux kernel6.8.2 and later · before 6.12.26
  • linux linux kernel6.13 and later · before 6.14.5
  • linux linux kernel6.15

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 7c8505ecc2d15473d679b8e06335434b84fffe86, 91d017d19d5a9ad153e2dc23ed3c0e2e79ef5262, 6.9affected
    • aba8659caf88017507419feea06069f529329ea6 and later · before c4312c4d244aa58e811ff0297e013124d115e793affected · git
    • e127ce7699c1e05279ee5ee61f00893e7bfa9671 and later · before 33e131a10459d16f181c8184d3f17f1c318c7002affected · git
    • e127ce7699c1e05279ee5ee61f00893e7bfa9671 and later · before e3ad76e36a37b0ff4a71b06d5b33530ee8c3a177affected · git
    • e127ce7699c1e05279ee5ee61f00893e7bfa9671 and later · before 4c2227656d9003f4d77afc76f34dd81b95e4c2c4affected · git
    • 6.6.23 and later · before 6.6.89affected · semver
    • 6.7.11 and later · before 6.8affected · semver
    • 6.8.2 and later · before 6.9affected · semver
    • before 6.9not affected · semver
    • 6.6.89 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-55.20.1.el10_06.12.0-55.20.1.el10_0
AlmaLinux:10kernel-docbefore 6.12.0-55.20.1.el10_06.12.0-55.20.1.el10_0
AlmaLinux:9kernelbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64kbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64k-corebefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64k-debugbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64k-develbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-corebefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-cross-headersbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-debugbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-debug-corebefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-debug-develbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-570.25.1.el9_65.14.0-570.25.1.el9_6

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-53116May 2, 2025 · nvmet: avoid potential UAF in nvmet_req_complete()
    31Monitor
  • ← EarlierCVE-2022-21546May 2, 2025 · scsi: target: Fix WRITE_SAME No Data Buffer crash
    31Monitor
  • Later →CVE-2024-58098May 5, 2025 · bpf: track changes_pkt_data property for global functions
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux33e131a10459d16f181c8184d3f17f1c318c7002Vendor (CNA)
Linux Linux4c2227656d9003f4d77afc76f34dd81b95e4c2c4Vendor (CNA)
Linux Linux6.6.89Vendor (CNA)
Linux Linux6.8Vendor (CNA)
Linux Linux6.9Vendor (CNA)
Linux Linuxc4312c4d244aa58e811ff0297e013124d115e793Vendor (CNA)
Linux Linuxe3ad76e36a37b0ff4a71b06d5b33530ee8c3a177Vendor (CNA)
almalinux:kernel5.14.0-570.25.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-570.25.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-570.25.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-570.25.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-570.25.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-570.25.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-570.25.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-570.25.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-570.25.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-570.25.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-abi-stablelists6.12.0-55.20.1.el10_0 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-doc6.12.0-55.20.1.el10_0 · AlmaLinux:10Package registry (OSV)
debian:linux6.12.27-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-55.20.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-55.20.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-55.20.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-55.20.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-55.20.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-55.20.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-55.20.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-55.20.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-55.20.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-55.20.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)

+3

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records