LiveActive security incident?Get immediate response
CVE Record

CVE-2024-57932: gve: guard XDP xmit NDO on existence of xdp queues

In the Linux kernel, the following vulnerability has been resolved: gve: guard XDP xmit NDO on existence of xdp queues In GVE, dedicated XDP queues only exist when an XDP program is installed and the interface is up. As such, the NDO XDP XMIT callback should return early if either of these conditions are false. In the case of no loaded XDP program, priv->num_xdp_queues=0 which can cause a divide-by-zero error, and in the case of interface down, num_xdp_queues remains untouched to persist XDP queue count for the next interface up, but the TX pointer itself would be NULL. The XDP xmit callback also needs to synchronize with a device transitioning from open to close. This synchronization will happen via the GVE_PRIV_FLAGS_NAPI_ENABLED bit along with a synchronize_net() call, which waits for any RCU critical sections at call-time to complete.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-57932 is a Linux kernel gve network-driver flaw in XDP transmit handling. Under conditions described by the kernel fix, the driver can hit divide-by-zero or NULL pointer behavior instead of returning safely. The provided sources do not include CVSS, confirmed exploitation, or a named advisory beyond upstream stable fixes.

Executive priority

Treat as a targeted kernel reliability issue, not a confirmed widespread emergency. Prioritize patching where gve and XDP are used, and let vendor advisories guide broader fleet scheduling because exploitation and severity evidence are incomplete.

Technical view

The gve NDO XDP XMIT callback did not guard against missing XDP queues when no XDP program is loaded or the interface is down. The fix adds early returns and synchronization using the NAPI-enabled flag with synchronize_net() during close transitions. Impact is most consistent with kernel/network-driver denial of service, but severity is not scored in the bundle.

Likely exposure

Exposure appears limited to Linux systems running affected kernels with the gve driver present, especially where XDP is used or interfaces transition state. The bundle does not identify distributions, cloud platforms, CPEs, or exact package versions, so organizations should verify vendor backports.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source claims active exploitation. The public description explains fault conditions but does not establish remote reachability, privilege requirements, or a practical exploit path.

Researcher notes

Key conditions are absence of loaded XDP program, interface-down state with persisted queue count, and open-to-close synchronization. The source bundle provides upstream commit references but no CVSS, CWE, exploit report, distro advisory, or detailed affected-version matrix.

Mitigation direction

  • Update to a kernel containing the referenced upstream stable fixes.
  • Check Linux distribution advisories for backported gve driver fixes.
  • Prioritize systems using gve interfaces with XDP enabled.
  • Plan maintenance windows for kernel updates where reboot is required.
  • Avoid assuming upstream version numbers prove distro exposure.

Validation and detection

  • Inventory Linux kernel versions across hosts using the gve driver.
  • Check whether affected hosts load XDP programs on gve interfaces.
  • Confirm vendor kernel packages include the referenced stable commits.
  • Review crash logs for divide-by-zero or NULL pointer faults in gve.
  • Track remediation status separately for upstream and distro kernels.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-57932 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux39a7f4aa3e4a7947614cf1d5c27abba3300adb1e, 39a7f4aa3e4a7947614cf1d5c27abba3300adb1e, 39a7f4aa3e4a7947614cf1d5c27abba3300adb1eunaffected
LinuxLinux6.4, 0, 6.6.70, 6.12.9, 6.13affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.