CVE-2024-44940
What it is
In the Linux kernel, the following vulnerability has been resolved: fou: remove warn in gue_gro_receive on unsupported protocol Drop the WARN_ON_ONCE inn gue_gro_receive if the encapsulated type is not known or does not have a GRO handler. Such a packet is easily constructed. Syzbot generates them and sets off this warning. Remove the warning as it is expected and not actionable. The warning was previously reduced from WARN_ON to WARN_ON_ONCE in commit 270136613bf7 ("fou: Do WARN_ON_ONCE in gue_gro_receive for bad proto callbacks").
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of service disruption.
- Exploit odds
- 0.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.8% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.8% · EPSS, next 30 days
- Record status
- Modified
Affected
- Debian Linux 11.0
- Linux Kernel < 5.10.234
- Linux Kernel < 5.15.174
- Linux Kernel < 6.1.107
- Linux Kernel < 6.6.47
- Linux Kernel < 6.10.6
Attack profile CVSS 3.1 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-44940.md and follow it. Check whether this project is affected by CVE-2024-44940. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/3db4395332e7050ef9ddeb3052e6b5019f2a2a59
- https://git.kernel.org/stable/c/440ab7f97261bc28501636a13998e1b1946d2e79
- https://git.kernel.org/stable/c/a925a200299a6dfc7c172f54da6f374edc930053
- https://git.kernel.org/stable/c/b1453a5616c7bd8acd90633ceba4e59105ba3b51
- https://git.kernel.org/stable/c/dd89a81d850fa9a65f67b4527c0e420d15bf836c
References
- https://git.kernel.org/stable/c/3db4395332e7050ef9ddeb3052e6b5019f2a2a59
- https://git.kernel.org/stable/c/440ab7f97261bc28501636a13998e1b1946d2e79
- https://git.kernel.org/stable/c/5a2e37bc648a2503bf6d687aed27b9f4455d82eb
- https://git.kernel.org/stable/c/a925a200299a6dfc7c172f54da6f374edc930053
- https://git.kernel.org/stable/c/b1453a5616c7bd8acd90633ceba4e59105ba3b51
- https://git.kernel.org/stable/c/dd89a81d850fa9a65f67b4527c0e420d15bf836c
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html