5.5

CVE-2024-26803: linux Incomplete Cleanup

CVSS: 5.5v3.1MediumAnalyzed
AliasesUBUNTU-CVE-2024-26803DEBIAN-CVE-2024-26803
Published 04-04-2024Last modified 11-05-2026
Open JSON

Vulnerability summary

CVE-2024-26803 is a medium (CVSS 5.5) Incomplete Cleanup vulnerability in linux. EPSS estimates a 0.22% chance of exploitation in the next 30 days, higher than 12.2% of scored vulnerabilities.

Overall risk
22/100
0100
Low · default modelHow is this calculated?
CVSS score
5.5/10
010
Medium · v3.1 (NVD)
EPSS score
0.22%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 16 · Related 15
RHSA-2024:9315USN-6820-1USN-6820-2USN-6821-1USN-6821-2USN-6821-3

Timeline

  1. 04-04-2024
    PublishedVulnerability first disclosed.
  2. 11-05-2026
    Last modifiedVulnerability information updated.

Description

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.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.22%

Chance of exploitation in the next 30 days

Percentile

12%

Versus all other CVEs

30-day change

0.00 pp

From 0.22% on 18-09-2026

18-09-202618-10-2026
EPSS score
0.22%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Ubuntu104 products
  • linux< 5.15.0-112.122
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws< 5.15.0-1063.69
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Linux2 products
  • linux≥ d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c, < f011c103e654d83dc85f057a7d1bd0960d02831c | ≥ d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c, < 7985d73961bbb4e726c1be7b9cd26becc7be8325 | ≥ d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c, < 16edf51f33f52dff70ed455bc40a6cc443c04664 | ≥ d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c, < 8f7a3894e58e6f5d5815533cfde60e3838947941 | ≥ d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c, < fe9f801355f0b47668419f30f1fac1cf4539e736 | 5.13
  • linux_kernel≥ 5.13, < 5.15.151 | ≥ 5.16, < 6.1.81 | ≥ 6.2, < 6.6.21 | ≥ 6.7, < 6.7.9 | 6.8:rc1 | 6.8:rc2 | 6.8:rc3 | 6.8:rc4 | 6.8:rc5 | 6.8:rc6
Debian1 product
  • linux< 6.1.82-1 | < 6.7.9-1

3 vendors · 107 products

References

23 links
Show all 23 references