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.0CRITICALhigh confidence
- EG Risk
- 81EG Risk 81/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%CISA SSVC: Track at low, Attend at medium and Act at high mission impact.Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact. - EPSS PROB
- 3.2%
- EPSS %ILE
- 87th
- KEV
- ⚠ Exploited
CISA SSVCTrack at low, Attend at medium and Act at high mission impact.
A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
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 | Fix (by version range) / 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.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
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 90× in last 7d / 401× 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 1,723 total refreshes for this CVE.
- 2026-10-06 10:35 UTCVendor advisory
- 2026-10-06 10:35 UTCGHSA enrichment
- 2026-10-06 06:22 UTCVendor advisory
- 2026-10-06 06:22 UTCGHSA enrichment
- 2026-10-06 02:11 UTCVendor advisory
- 2026-10-06 02:11 UTCGHSA enrichment
- 2026-10-05 21:57 UTCVendor advisory
- 2026-10-05 21:57 UTCGHSA enrichment
- 2026-10-05 17:46 UTCEG score recompute
- 2026-10-05 17:46 UTCVendor advisory
- 2026-10-05 17:46 UTCGHSA enrichment
- 2026-10-05 17:38 UTCEPSS rescore
- 2026-10-05 13:36 UTCVendor advisory
- 2026-10-05 13:35 UTCGHSA enrichment
- 2026-10-05 09:24 UTCVendor advisory
- 2026-10-05 09:24 UTCGHSA enrichment
- 2026-10-05 05:13 UTCVendor advisory
- 2026-10-05 05:13 UTCGHSA enrichment
- 2026-10-05 01:02 UTCEG score recompute
- 2026-10-05 01:02 UTCVendor advisory
- 2026-10-05 01:01 UTCGHSA enrichment
- 2026-10-04 23:16 UTCEPSS rescore
- 2026-10-04 20:48 UTCVendor advisory
- 2026-10-04 20:48 UTCGHSA enrichment
- 2026-10-04 16:37 UTCVendor advisory
Show 75 moreShow fewer
- 2026-10-04 16:37 UTCGHSA enrichment
- 2026-10-04 12:26 UTCVendor advisory
- 2026-10-04 12:26 UTCGHSA enrichment
- 2026-10-04 08:15 UTCVendor advisory
- 2026-10-04 08:14 UTCGHSA enrichment
- 2026-10-04 04:03 UTCVendor advisory
- 2026-10-04 04:03 UTCGHSA enrichment
- 2026-10-03 23:52 UTCVendor advisory
- 2026-10-03 23:52 UTCGHSA enrichment
- 2026-10-03 19:40 UTCVendor advisory
- 2026-10-03 19:40 UTCGHSA enrichment
- 2026-10-03 15:30 UTCEG score recompute
- 2026-10-03 15:30 UTCVendor advisory
- 2026-10-03 15:29 UTCGHSA enrichment
- 2026-10-03 11:18 UTCVendor advisory
- 2026-10-03 11:18 UTCGHSA enrichment
- 2026-10-03 07:06 UTCVendor advisory
- 2026-10-03 07:06 UTCGHSA enrichment
- 2026-10-03 02:55 UTCVendor advisory
- 2026-10-03 02:55 UTCGHSA enrichment
- 2026-10-02 22:42 UTCVendor advisory
- 2026-10-02 22:41 UTCGHSA enrichment
- 2026-10-02 18:30 UTCEG score recompute
- 2026-10-02 18:30 UTCVendor advisory
- 2026-10-02 18:30 UTCGHSA enrichment
- 2026-10-02 14:20 UTCVendor advisory
- 2026-10-02 14:20 UTCGHSA enrichment
- 2026-10-02 10:04 UTCVendor advisory
- 2026-10-02 10:04 UTCGHSA enrichment
- 2026-10-02 05:53 UTCVendor advisory
- 2026-10-02 05:53 UTCGHSA enrichment
- 2026-10-02 01:42 UTCVendor advisory
- 2026-10-02 01:42 UTCGHSA enrichment
- 2026-10-01 21:29 UTCEG score recompute
- 2026-10-01 21:29 UTCVendor advisory
- 2026-10-01 21:29 UTCGHSA enrichment
- 2026-10-01 17:18 UTCVendor advisory
- 2026-10-01 17:18 UTCGHSA enrichment
- 2026-10-01 13:06 UTCVendor advisory
- 2026-10-01 13:06 UTCGHSA enrichment
- 2026-10-01 08:56 UTCVendor advisory
- 2026-10-01 08:56 UTCGHSA enrichment
- 2026-10-01 04:45 UTCVendor advisory
- 2026-10-01 04:44 UTCGHSA enrichment
- 2026-10-01 00:31 UTCVendor advisory
- 2026-10-01 00:31 UTCGHSA enrichment
- 2026-09-30 20:16 UTCVendor advisory
- 2026-09-30 20:16 UTCGHSA enrichment
- 2026-09-30 16:05 UTCEG score recompute
- 2026-09-30 16:05 UTCVendor advisory
- 2026-09-30 16:05 UTCGHSA enrichment
- 2026-09-30 14:58 UTCEPSS rescore
- 2026-09-30 11:54 UTCVendor advisory
- 2026-09-30 11:54 UTCGHSA enrichment
- 2026-09-30 07:43 UTCVendor advisory
- 2026-09-30 07:42 UTCGHSA enrichment
- 2026-09-30 03:29 UTCVendor advisory
- 2026-09-30 03:29 UTCGHSA enrichment
- 2026-09-29 23:18 UTCVendor advisory
- 2026-09-29 23:17 UTCGHSA enrichment
- 2026-09-29 19:04 UTCEG score recompute
- 2026-09-29 19:04 UTCVendor advisory
- 2026-09-29 19:04 UTCGHSA enrichment
- 2026-09-29 14:53 UTCVendor advisory
- 2026-09-29 14:53 UTCGHSA enrichment
- 2026-09-29 10:42 UTCVendor advisory
- 2026-09-29 10:42 UTCGHSA enrichment
- 2026-09-29 06:25 UTCVendor advisory
- 2026-09-29 06:25 UTCGHSA enrichment
- 2026-09-29 02:15 UTCVendor advisory
- 2026-09-29 02:15 UTCGHSA enrichment
- 2026-09-28 22:04 UTCEG score recompute
- 2026-09-28 22:04 UTCVendor advisory
- 2026-09-28 22:04 UTCGHSA enrichment
- 2026-09-28 17:52 UTCEG score recompute
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:RHSA-2015:0695 · redhat:RHSA-2015:0782 · redhat:RHSA-2014:1392
Same CWE
10 shownCWE-190
- CVE-2013-1317EG 9.3EPSS p97HIGH
- CVE-2013-2555EG 10.0EPSS p95HIGH
- CVE-2013-2729EG 9.8 KEVEPSS p99CRITICAL
- CVE-2013-0899EG 5.0MEDIUM
- CVE-2013-0891EG 7.5HIGH
- CVE-2013-0750EG 9.3EPSS p93HIGH
- CVE-2012-5143EG 10.0HIGH
- CVE-2012-5835EG 10.0EPSS p95HIGH
- CVE-2013-4391EG 7.5EPSS p92HIGH
- CVE-2012-5054NVD 8.8EG 9.0 KEVEPSS p98CRITICAL
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
See which npm, PyPI, Go, and Maven packages are affected by 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.