CVE-2024-50302
Linux Kernel Use of Uninitialized Resource Vulnerability
Linux Kernel
In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 4 March 2025. US federal agencies were required to remediate it by 25 March 2025.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 0.8%, which is higher than 55.6% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Frequently asked questions
Is CVE-2024-50302 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2024-50302.
What does CVE-2024-50302 affect?
CVE-2024-50302 affects Linux Kernel. In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report.
How severe is CVE-2024-50302?
CVE-2024-50302 is rated MEDIUM with a CVSS base score of 5.5. EPSS puts the probability of exploitation in the next 30 days at 0.8%, higher than 55.6% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 25 March 2025.
How should organisations respond to CVE-2024-50302?
Apply the vendor patch for Linux Kernel as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.