CVE-2024-53104
Linux Kernel Out-of-Bounds Write Vulnerability
Linux Kernel
In the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_format This can lead to out of bounds writes since frames of this type were not taken into account when calculating the size of the frames buffer in uvc_parse_streaming.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 5 February 2025. US federal agencies were required to remediate it by 26 February 2025.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 3.4%, which is higher than 88.9% 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:H/A:H
Frequently asked questions
Is CVE-2024-53104 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2024-53104.
What does CVE-2024-53104 affect?
CVE-2024-53104 affects Linux Kernel. In the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_format This can lead to out of bounds writes since frames of this type were not taken into account when calculating the size of the frames buffer in uvc_parse_streaming.
How severe is CVE-2024-53104?
CVE-2024-53104 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 3.4%, higher than 88.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 26 February 2025.
How should organisations respond to CVE-2024-53104?
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.