NVD / CVE Program· CNA Linux

CVE-2024-26803: net: veth: clear GRO when clearing XDP even when down

MediumCVSS 5.5 · v3.1—No exploit Fix available

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.22% (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 16edf51f33f52dff70ed455bc40a6cc443c04664, 7985d73961bbb4e726c1be7b9cd26becc7be8325, 8f7a3894e58e6f5d5815533cfde60e3838947941.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 16edf51f33f52dff70ed455bc40a6cc443c04664, 7985d73961bbb4e726c1be7b9cd26becc7be8325, 8f7a3894e58e6f5d5815533cfde60e3838947941 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: net: veth: clear GRO when clearing XDP even when down veth sets NETIF_F_GRO automatically when XDP is enabled, because both features use the same NAPI machinery. The logic to clear NETIF_F_GRO sits in veth_disable_xdp() which is called both on ndo_stop and when XDP is turned off. To avoid the flag from being cleared when the device is brought down, the clearing is skipped when IFF_UP is not set. Bringing the device down should indeed not modify its features. Unfortunately, this means that clearing is also skipped when XDP is disabled _while_ the device is down. And there's nothing on the open path to bring the device features back into sync. IOW if user enables XDP, disables it and then brings the device up we'll end up with a stray GRO flag set but no NAPI instances. We don't depend on the GRO flag on the datapath, so the datapath won't crash. We will crash (or hang), however, next time features are sync'ed (either by user via ethtool or peer changing its config). The GRO flag will go away, and veth will try to disable the NAPIs. But the open path never created them since XDP was off, the GRO flag was a stray. If NAPI was initialized before we'll hang in napi_disable(). If it never was we'll crash trying to stop uninitialized hrtimer. Move the GRO flag updates to the XDP enable / disable paths, instead of mixing them with the ndo_open / ndo_close paths.

Denial of service

BDU:2024-09198

Published: Apr 4, 2024
Updated: Jun 17, 2026
EPSS: 0.2% · 13th percentile
CWE: CWE-459

Report tools

JSON

Action score

Monitor

Low priority for now.

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

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

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.

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.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

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
- 5.13affected
- d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c and later · before f011c103e654d83dc85f057a7d1bd0960d02831caffected · git
- d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c and later · before 7985d73961bbb4e726c1be7b9cd26becc7be8325affected · git
- d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c and later · before 16edf51f33f52dff70ed455bc40a6cc443c04664affected · git
- d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c and later · before 8f7a3894e58e6f5d5815533cfde60e3838947941affected · git
- d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c and later · before fe9f801355f0b47668419f30f1fac1cf4539e736affected · git
- before 5.13not affected · semver
- 5.15.151 and later · up to and including 5.15.*not affected · semver
- 6.1.81 and later · up to and including 6.1.*not affected · semver
- 6.6.21 and later · up to and including 6.6.*not affected · semver

Affected versions · NVD (5)

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

linux linux kernel5.13 and later · before 5.15.151
linux linux kernel5.16 and later · before 6.1.81
linux linux kernel6.2 and later · before 6.6.21
linux linux kernel6.7 and later · before 6.7.9
linux linux kernel6.8

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.82-1	6.1.82-1
Debian:13	linux	before 6.7.9-1	6.7.9-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
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

Published before and after this one in the same product

← EarlierCVE-2024-26801Apr 4, 2024 · Bluetooth: Avoid potential use-after-free in hci_error_reset
22Monitor
← EarlierCVE-2024-26802Apr 4, 2024 · stmmac: Clear variable when destroying workqueue
22Monitor
Later →CVE-2024-26804Apr 4, 2024 · net: ip_tunnel: prevent perpetual headroom growth
31Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
Linux Linux	16edf51f33f52dff70ed455bc40a6cc443c04664	Vendor (CNA)
Linux Linux	7985d73961bbb4e726c1be7b9cd26becc7be8325	Vendor (CNA)
Linux Linux	8f7a3894e58e6f5d5815533cfde60e3838947941	Vendor (CNA)
Linux Linux	f011c103e654d83dc85f057a7d1bd0960d02831c	Vendor (CNA)
Linux Linux	fe9f801355f0b47668419f30f1fac1cf4539e736	Vendor (CNA)
debian:linux	6.1.82-1 · Debian:12	Package registry (OSV)

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.

Variant candidates

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

CVE-2025-37908411 days apartmm, slab: clean up slab->obj_exts always
31Monitor
CVE-2022-3238507 days apartA double-free flaw was found in the Linux kernel’s NTFS3 subsystem in how a user triggers remount and umount simultaneously.
31Monitor
CVE-2021-4711020 days apartx86/kvm: Disable kvmclock on all CPUs on shutdown
28Monitor
CVE-2024-47693200 days apartIB/core: Fix ib_cache_setup_one error flow cleanup
26Monitor
CVE-2024-266871 days apartxen/events: close evtchn after mapping cleanup
22Monitor
CVE-2024-267561 days apartmd: Don't register sync_thread for reshape directly
22Monitor