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.
CVE-2013-2596
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-09-15), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 9.0(high)
- EPSS
- 87.3%
- KEV
- ⚠ Exploited
Published
April 13, 2013
Last Modified
April 21, 2026
Advisory Details (6)
Auto-updated May 19, 2026Root Method Released for DROID RAZR HD Running Android 4.1.2, Other Devices Too
http://www.droid-life.com/2013/04/09/root-method-released-for-droid-razr-hd-running-android-4-1-2-other-devices-too/'Device driver memory 'mmap()' function helper cleanup' - MARC
http://marc.info/?l=linux-kernel&m=136616837923938&w=2Vendor Advisories for CVE-2013-2596(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2015:0803Red Hat Product SecurityHigh
Red Hat Security Advisory: kernel security and bug fix update
- RHSA-2015:0782Red Hat Product SecurityHigh
Red Hat Security Advisory: kernel security and bug fix update
- RHSA-2015:0695Red Hat Product SecurityHigh
Red Hat Security Advisory: kernel security and bug fix update
Patch Availability(5)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | kernel-0:2.6.18-409.el5 | 2016-03-15 | redhat |
| redhat | kernel-0:2.6.32-358.59.1.el6 | 2015-04-14 | redhat |
| redhat | kernel-0:2.6.32-431.53.2.el6 | 2015-04-07 | redhat |
| redhat | kernel-0:2.6.32-220.60.2.el6 | 2015-03-17 | redhat |
| redhat | kernel-0:2.6.32-504.el6 | 2014-10-13 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 128× in last 7d / 562× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 744 total refreshes for this CVE.
- 2026-07-07 02:41 UTCEG score recompute
- 2026-07-07 02:41 UTCVendor advisory
- 2026-07-07 02:41 UTCGHSA enrichment
- 2026-07-06 22:30 UTCEG score recompute
- 2026-07-06 22:30 UTCVendor advisory
- 2026-07-06 22:30 UTCGHSA enrichment
- 2026-07-06 18:19 UTCEG score recompute
- 2026-07-06 18:19 UTCVendor advisory
- 2026-07-06 18:18 UTCGHSA enrichment
- 2026-07-06 14:07 UTCEG score recompute
- 2026-07-06 14:07 UTCVendor advisory
- 2026-07-06 14:07 UTCGHSA enrichment
- 2026-07-06 09:55 UTCEG score recompute
- 2026-07-06 09:55 UTCVendor advisory
- 2026-07-06 09:55 UTCGHSA enrichment
- 2026-07-06 05:43 UTCEG score recompute
- 2026-07-06 05:43 UTCVendor advisory
- 2026-07-06 05:42 UTCGHSA enrichment
- 2026-07-06 02:19 UTCEPSS rescore
- 2026-07-06 02:19 UTCEPSS rescore
- 2026-07-06 01:29 UTCEG score recompute
- 2026-07-06 01:29 UTCVendor advisory
- 2026-07-06 01:29 UTCGHSA enrichment
- 2026-07-05 21:18 UTCEG score recompute
- 2026-07-05 21:18 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-05 21:18 UTCGHSA enrichment
- 2026-07-05 17:06 UTCEG score recompute
- 2026-07-05 17:06 UTCVendor advisory
- 2026-07-05 17:06 UTCGHSA enrichment
- 2026-07-05 12:55 UTCEG score recompute
- 2026-07-05 12:55 UTCVendor advisory
- 2026-07-05 12:55 UTCGHSA enrichment
- 2026-07-05 08:45 UTCEG score recompute
- 2026-07-05 08:45 UTCVendor advisory
- 2026-07-05 08:44 UTCGHSA enrichment
- 2026-07-05 04:34 UTCEG score recompute
- 2026-07-05 04:34 UTCVendor advisory
- 2026-07-05 04:33 UTCGHSA enrichment
- 2026-07-05 02:26 UTCEPSS rescore
- 2026-07-05 00:23 UTCEG score recompute
- 2026-07-05 00:23 UTCVendor advisory
- 2026-07-05 00:22 UTCGHSA enrichment
- 2026-07-04 20:10 UTCEG score recompute
- 2026-07-04 20:10 UTCVendor advisory
- 2026-07-04 20:09 UTCGHSA enrichment
- 2026-07-04 15:58 UTCEG score recompute
- 2026-07-04 15:58 UTCVendor advisory
- 2026-07-04 15:57 UTCGHSA enrichment
- 2026-07-04 11:46 UTCEG score recompute
- 2026-07-04 11:46 UTCVendor advisory
- 2026-07-04 11:46 UTCGHSA enrichment
- 2026-07-04 07:34 UTCEG score recompute
- 2026-07-04 07:34 UTCVendor advisory
- 2026-07-04 07:33 UTCGHSA enrichment
- 2026-07-04 06:27 UTCEPSS rescore
- 2026-07-04 03:21 UTCEG score recompute
- 2026-07-04 03:21 UTCVendor advisory
- 2026-07-04 03:20 UTCGHSA enrichment
- 2026-07-03 23:08 UTCEG score recompute
- 2026-07-03 23:08 UTCVendor advisory
- 2026-07-03 23:08 UTCGHSA enrichment
- 2026-07-03 18:53 UTCEG score recompute
- 2026-07-03 18:53 UTCVendor advisory
- 2026-07-03 18:53 UTCGHSA enrichment
- 2026-07-03 14:43 UTCEG score recompute
- 2026-07-03 14:43 UTCVendor advisory
- 2026-07-03 14:42 UTCGHSA enrichment
- 2026-07-03 10:31 UTCEG score recompute
- 2026-07-03 10:31 UTCVendor advisory
- 2026-07-03 10:30 UTCGHSA enrichment
- 2026-07-03 06:18 UTCEG score recompute
- 2026-07-03 06:18 UTCVendor advisory
- 2026-07-03 06:18 UTCGHSA enrichment
- 2026-07-03 02:06 UTCEG score recompute
- 2026-07-03 02:06 UTCVendor advisory
- 2026-07-03 02:06 UTCGHSA enrichment
- 2026-07-02 21:55 UTCEG score recompute
- 2026-07-02 21:55 UTCVendor advisory
- 2026-07-02 21:55 UTCGHSA enrichment
- 2026-07-02 17:44 UTCEG score recompute
- 2026-07-02 17:44 UTCVendor advisory
- 2026-07-02 17:43 UTCGHSA enrichment
- 2026-07-02 13:33 UTCEG score recompute
- 2026-07-02 13:33 UTCVendor advisory
- 2026-07-02 13:32 UTCGHSA enrichment
- 2026-07-02 09:21 UTCEG score recompute
- 2026-07-02 09:21 UTCVendor advisory
- 2026-07-02 09:21 UTCGHSA enrichment
- 2026-07-02 05:10 UTCEG score recompute
- 2026-07-02 05:10 UTCVendor advisory
- 2026-07-02 05:10 UTCGHSA enrichment
- 2026-07-02 00:59 UTCEG score recompute
- 2026-07-02 00:59 UTCVendor advisory
- 2026-07-02 00:59 UTCGHSA enrichment
- 2026-07-01 20:45 UTCEG score recompute
- 2026-07-01 20:45 UTCVendor advisory
- 2026-07-01 20:45 UTCGHSA enrichment
- 2026-07-01 19:16 UTCCISA KEV update
- 2026-07-01 16:34 UTCEG score recompute
- 2026-07-01 16:34 UTCVendor advisory
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoChiikezoe/libfb_mem_exploitFirst seen Jul 16, 2013
CVE-2013-2596 exploit for android
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-190
- CVE-2009-0947EG 9.8CRITICAL
- CVE-2013-3493EG 9.8CRITICAL
- CVE-2013-2729EG 9.8 KEVEPSS 99%CRITICAL
- CVE-2005-1141EG 9.8CRITICAL
- CVE-2005-0102EG 9.8CRITICAL
- CVE-2002-0391EG 9.8EPSS 99%CRITICAL
- CVE-2002-0639EG 9.8EPSS 97%CRITICAL
- CVE-2013-3486EG 9.6CRITICAL
- CVE-2012-5054NVD 8.8EG 9.0 KEVEPSS 97%HIGH
- CVE-2011-1823NVD 7.8EG 9.0 KEVEPSS 99%HIGH
Frequently asked(6)
What is CVE-2013-2596?
When was CVE-2013-2596 disclosed?
Is CVE-2013-2596 actively exploited?
What is the CVSS score of CVE-2013-2596?
Which products are affected by CVE-2013-2596?
How do I remediate CVE-2013-2596?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2013-2596
Is Your Infrastructure Affected by CVE-2013-2596?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.