Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 45 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26803, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c – < f011c103e654d83dc85f057a7d1bd0960d02831c
    • affected d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c – < 7985d73961bbb4e726c1be7b9cd26becc7be8325
    • affected d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c – < 16edf51f33f52dff70ed455bc40a6cc443c04664
    • affected d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c – < 8f7a3894e58e6f5d5815533cfde60e3838947941
    • affected d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c – < fe9f801355f0b47668419f30f1fac1cf4539e736
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.151 – ≤ 5.15.*
    • unaffected 6.1.81 – ≤ 6.1.*
    • unaffected 6.6.21 – ≤ 6.6.*
    • unaffected 6.7.9 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26803 badge
[![CVE-2024-26803](https://cveledger.app/badge/CVE-2024-26803.svg)](https://cveledger.app/cve/CVE-2024-26803)

Record last updated .