CVE-2024-26803
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2024-26803
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-26803.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2024-26803
- Downstream
- Published
- 2024-04-04T08:20:30Z
- Modified
- 2025-10-21T20:12:43.477856Z
- Summary
- net: veth: clear GRO when clearing XDP even when down
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
net: veth: clear GRO when clearing XDP even when down
veth sets NETIFFGRO automatically when XDP is enabled, because both features use the same NAPI machinery.
The logic to clear NETIFFGRO sits in vethdisablexdp() which is called both on ndostop and when XDP is turned off. To avoid the flag from being cleared when the device is brought down, the clearing is skipped when IFFUP 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 ndoopen / ndoclose paths.
- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/16edf51f33f52dff70ed455bc40a6cc443c04664
- https://git.kernel.org/stable/c/7985d73961bbb4e726c1be7b9cd26becc7be8325
- https://git.kernel.org/stable/c/8f7a3894e58e6f5d5815533cfde60e3838947941
- https://git.kernel.org/stable/c/f011c103e654d83dc85f057a7d1bd0960d02831c
- https://git.kernel.org/stable/c/fe9f801355f0b47668419f30f1fac1cf4539e736
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedd3256efd8e8b234a6251e4d4580bd2c3c31fdc4cFixedf011c103e654d83dc85f057a7d1bd0960d02831c
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedd3256efd8e8b234a6251e4d4580bd2c3c31fdc4cFixed7985d73961bbb4e726c1be7b9cd26becc7be8325
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedd3256efd8e8b234a6251e4d4580bd2c3c31fdc4cFixed16edf51f33f52dff70ed455bc40a6cc443c04664
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedd3256efd8e8b234a6251e4d4580bd2c3c31fdc4cFixed8f7a3894e58e6f5d5815533cfde60e3838947941
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedd3256efd8e8b234a6251e4d4580bd2c3c31fdc4cFixedfe9f801355f0b47668419f30f1fac1cf4539e736