{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-37799 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-37799 is a high-severity vulnerability in Linux kernel, published on 3 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-37799 and fix it if it is affected.\n\nWhat it is: CVE-2025-37799 is a high-severity vulnerability in Linux kernel, published on 3 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-37799 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-37799/ (Markdown: https://insights.sbomify.com/CVE-2025-37799/index.md)","id":"CVE-2025-37799","markdown":"https://insights.sbomify.com/CVE-2025-37799/index.md","name":"CVE-2025-37799","record":{"aliases":["BELL-CVE-2025-37799","DEBIAN-CVE-2025-37799","GHSA-5w6m-x8hm-6jcv","RHSA-2025:10674","ROOT-OS-DEBIAN-11-CVE-2025-37799","ROOT-OS-DEBIAN-12-CVE-2025-37799","ROOT-OS-UBUNTU-2404-CVE-2025-37799","UBUNTU-CVE-2025-37799"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A flaw in the vmxnet3 driver leaks uninitialized kernel memory onto the network, allowing attackers to read sensitive data from the host.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nvmxnet3: Fix malformed packet sizing in vmxnet3_process_xdp\n\nvmxnet3 driver's XDP handling is buggy for packet sizes using ring0 (that\nis, packet sizes between 128 - 3k bytes).\n\nWe noticed MTU-related connectivity issues with Cilium's service load-\nbalancing in case of vmxnet3 as NIC underneath. A simple curl to a HTTP\nbackend service where the XDP LB was doing IPIP encap led to overly large\npacket sizes but only for *some* of the packets (e.g. HTTP GET request)\nwhile others (e.g. the prior TCP 3WHS) looked completely fine on the wire.\n\nIn fact, the pcap recording on the backend node actually revealed that the\nnode with the XDP LB was leaking uninitialized kernel data onto the wire\nfor the affected packets, for example, while the packets should have been\n152 bytes their actual size was 1482 bytes, so the remainder after 152 bytes\nwas padded with whatever other data was in that page at the time (e.g. we\nsaw user/payload data from prior processed packets).\n\nWe only noticed this through an MTU issue, e.g. when the XDP LB node and\nthe backend node both had the same MTU (e.g. 1500) then the curl request\ngot dropped on the backend node's NIC given the packet was too large even\nthough the IPIP-encapped packet normally would never even come close to\nthe MTU limit. Lowering the MTU on the XDP LB (e.g. 1480) allowed to let\nthe curl request succeed (which also indicates that the kernel ignored the\npadding, and thus the issue wasn't very user-visible).\n\nCommit e127ce7699c1 (\"vmxnet3: Fix missing reserved tailroom\") was too eager\nto also switch xdp_prepare_buff() from rcd-\u003elen to rbi-\u003elen. It really needs\nto stick to rcd-\u003elen which is the actual packet length from the descriptor.\nThe latter we also feed into vmxnet3_process_xdp_small(), by the way, and\nit indicates the correct length needed to initialize the xdp-\u003e{data,data_end}\nparts. For e127ce7699c1 (\"vmxnet3: Fix missing reserved tailroom\") the\nrelevant part was adapting xdp_init_buff() to address the warning given the\nxdp_data_hard_end() depends on xdp-\u003eframe_sz. With that fixed, traffic on\nthe wire looks good again.","ecosystems":["Red Hat:enterprise_linux:9::baseos"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"vmxnet3: Fix malformed packet sizing in vmxnet3_process_xdp","id":"CVE-2025-37799","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"information_disclosure","year":"2025"},"n_packages":3,"n_references":4,"next":{"headline":"driver core: fix potential NULL pointer dereference in dev_uevent()","id":"CVE-2025-37800"},"packages":[{"ecosystem":"Red Hat:enterprise_linux:9::baseos","fixed":["0:1-3.el9_6"],"introduced":["0"],"last_affected":[],"package":"kpatch-patch-5_14_0-570_17_1","purl":"pkg:rpm/redhat/kpatch-patch-5_14_0-570_17_1","source":"RHSA-2025:10674"},{"ecosystem":"Red Hat:enterprise_linux:9::baseos","fixed":["0:1-3.el9_6"],"introduced":["0"],"last_affected":[],"package":"kpatch-patch-5_14_0-570_17_1-debuginfo","purl":"pkg:rpm/redhat/kpatch-patch-5_14_0-570_17_1-debuginfo","source":"RHSA-2025:10674"},{"ecosystem":"Red Hat:enterprise_linux:9::baseos","fixed":["0:1-3.el9_6"],"introduced":["0"],"last_affected":[],"package":"kpatch-patch-5_14_0-570_17_1-debugsource","purl":"pkg:rpm/redhat/kpatch-patch-5_14_0-570_17_1-debugsource","source":"RHSA-2025:10674"}],"prev":{"headline":"codel: remove sch-\u003eq.qlen check before qdisc_tree_reduce_backlog()","id":"CVE-2025-37798"},"products":["Linux"],"published":"2025-05-03","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"A flaw in the vmxnet3 driver leaks uninitialized kernel memory onto the network, allowing attackers to read sensitive data from the host.","url":"https://insights.sbomify.com/CVE-2025-37799/"}