CVE-2024-40937
Linux Kernel vulnerability
- Published12 Jul 2024
Description
In the Linux kernel, the following vulnerability has been resolved: gve: Clear napi->skb before dev_kfree_skb_any() gve_rx_free_skb incorrectly leaves napi->skb referencing an skb after it is freed with dev_kfree_skb_any(). This can result in a subsequent call to napi_get_frags returning a dangling pointer. Fix this by clearing napi->skb before the skb is freed.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
- https://git.kernel.org/stable/c/2ce5341c36993b776012601921d7688693f8c037
- https://git.kernel.org/stable/c/6f4d93b78ade0a4c2cafd587f7b429ce95abb02e
- https://git.kernel.org/stable/c/75afd8724739ee5ed8165acde5f6ac3988b485cc
- https://git.kernel.org/stable/c/a68184d5b420ea4fc7e6b7ceb52bbc66f90d3c50
- https://git.kernel.org/stable/c/d221284991118c0ab16480b53baecd857c0bc442
References
- https://git.kernel.org/stable/c/2ce5341c36993b776012601921d7688693f8c037
- https://git.kernel.org/stable/c/6f4d93b78ade0a4c2cafd587f7b429ce95abb02e
- https://git.kernel.org/stable/c/75afd8724739ee5ed8165acde5f6ac3988b485cc
- https://git.kernel.org/stable/c/a68184d5b420ea4fc7e6b7ceb52bbc66f90d3c50
- https://git.kernel.org/stable/c/d221284991118c0ab16480b53baecd857c0bc442
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Frequently asked
Is CVE-2024-40937 being actively exploited?
CVE-2024-40937 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.74%.
How severe is CVE-2024-40937?
CVE-2024-40937 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.74% probability of exploitation.
Which products are affected by CVE-2024-40937?
Affected products include Linux Kernel.
How do I fix CVE-2024-40937?
Upgrade affected software to a fixed version, for example Linux Kernel 5.15.162 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-40937 against the real software inventory on every managed device, as each hourly inventory arrives. 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.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.