CVE-2013-6282
Linux Kernel Improper Input Validation Vulnerability
Linux Kernel
The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addresses, which allows attackers to read or modify the contents of arbitrary kernel memory locations via a crafted application, as exploited in the wild against Android devices in October and November 2013.
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 39.7%, which is higher than 98.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:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2013-6282 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2013-6282.
What does CVE-2013-6282 affect?
CVE-2013-6282 affects Linux Kernel. The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addresses, which allows attackers to read or modify the contents of arbitrary kernel memory locations via a crafted application, as exploited in the wild against Android devices in October and November 2013.
How severe is CVE-2013-6282?
CVE-2013-6282 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 39.7%, higher than 98.6% 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-6282?
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.