CVE-2013-2596
Linux Kernel Integer Overflow Vulnerability
Linux Kernel
Integer overflow in the fb_mmap function in drivers/video/fbmem.c in the Linux kernel before 3.8.9, as used in a certain Motorola build of Android 4.1.2 and other products, allows local users to create a read-write memory mapping for the entirety of kernel memory, and consequently gain privileges, via crafted /dev/graphics/fb0 mmap2 system calls, as demonstrated by the Motochopper pwn program.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 15 September 2022. US federal agencies were required to remediate it by 6 October 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 3.2%, which is higher than 87.8% 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-2013-2596 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2013-2596.
What does CVE-2013-2596 affect?
CVE-2013-2596 affects Linux Kernel. Integer overflow in the fb_mmap function in drivers/video/fbmem.c in the Linux kernel before 3.8.9, as used in a certain Motorola build of Android 4.1.2 and other products, allows local users to create a read-write memory mapping for the entirety of kernel memory, and consequently gain privileges, via crafted /dev/graphics/fb0 mmap2 system calls, as demonstrated by the Motochopper pwn program.
How severe is CVE-2013-2596?
CVE-2013-2596 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 3.2%, higher than 87.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 6 October 2022.
How should organisations respond to CVE-2013-2596?
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.