CVE-2024-57932: Linux Kernel vulnerability (CVSS 9.8)

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Linux Kernel≥ 6.4 < 6.6.70 · ≥ 6.7 < 6.12.9 · 6.13

Remediation

Fixed in

Linux Kernel≥ 6.6.70

Patch & vendor advisories

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-57932 being actively exploited?

CVE-2024-57932 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.45%.

How severe is CVE-2024-57932?

CVE-2024-57932 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.45% probability of exploitation.

Which products are affected by CVE-2024-57932?

Affected products include Linux Kernel.

How do I fix CVE-2024-57932?

Upgrade affected software to a fixed version, for example Linux Kernel 6.6.70 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-57932 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo