CVE-2013-2596

CRITICALNVD 7.89.0▲
EchelonGraph scoreHIGH confidence

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.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 3%CVSS: 7.8Exploit: cisa kev · ssvc active · public exploitExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

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 computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
3%
EPSS %ILE
88%
KEV
⚠ Exploited

Published

April 13, 2013

Last Modified

April 21, 2026

Advisory Details (6)

Auto-updated May 19, 2026
No patch confirmed yet.
generic

Root 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/
generic
http://rhn.redhat.com/errata/RHSA-2015-0803.html
generic
http://rhn.redhat.com/errata/RHSA-2015-0782.html
generic
http://rhn.redhat.com/errata/RHSA-2015-0695.html
generic

'Device driver memory 'mmap()' function helper cleanup' - MARC

http://marc.info/?l=linux-kernel&m=136616837923938&w=2
generic

CEC Juniper Community

http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10761

Vendor 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.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:2.6.18-409.el52016-03-15redhat
redhatkernel-0:2.6.32-358.59.1.el62015-04-14redhat
redhatkernel-0:2.6.32-431.53.2.el62015-04-07redhat
redhatkernel-0:2.6.32-220.60.2.el62015-03-17redhat
redhatkernel-0:2.6.32-504.el62014-10-13redhat

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)
PackageVulnerable rangeFixed inDependents
linux—3.9-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—3.9-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—3.9-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—3.9-1—

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 98× in last 7d / 369× 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,117 total refreshes for this CVE.

  1. 2026-08-21 23:52 UTCEG score recompute
  2. 2026-08-21 23:52 UTCVendor advisory
  3. 2026-08-21 23:51 UTCGHSA enrichment
  4. 2026-08-21 23:44 UTCEPSS rescore
  5. 2026-08-21 19:41 UTCVendor advisory
  6. 2026-08-21 19:41 UTCGHSA enrichment
  7. 2026-08-21 16:49 UTCCISA KEV update
  8. 2026-08-21 15:30 UTCVendor advisory
  9. 2026-08-21 15:30 UTCGHSA enrichment
  10. 2026-08-21 11:19 UTCVendor advisory
  11. 2026-08-21 11:18 UTCGHSA enrichment
  12. 2026-08-21 07:05 UTCVendor advisory
  13. 2026-08-21 07:05 UTCGHSA enrichment
  14. 2026-08-21 02:54 UTCEG score recompute
  15. 2026-08-21 02:54 UTCVendor advisory
  16. 2026-08-21 02:54 UTCGHSA enrichment
  17. 2026-08-20 22:50 UTCEPSS rescore
  18. 2026-08-20 22:42 UTCVendor advisory
  19. 2026-08-20 22:42 UTCGHSA enrichment
  20. 2026-08-20 18:31 UTCVendor advisory
  21. 2026-08-20 18:31 UTCGHSA enrichment
  22. 2026-08-20 17:06 UTCCISA KEV update
  23. 2026-08-20 14:20 UTCVendor advisory
  24. 2026-08-20 14:20 UTCGHSA enrichment
  25. 2026-08-20 10:09 UTCVendor advisory
Show 75 more
  1. 2026-08-20 10:09 UTCGHSA enrichment
  2. 2026-08-20 05:58 UTCVendor advisory
  3. 2026-08-20 05:58 UTCGHSA enrichment
  4. 2026-08-20 01:47 UTCVendor advisory
  5. 2026-08-20 01:46 UTCGHSA enrichment
  6. 2026-08-19 21:35 UTCVendor advisory
  7. 2026-08-19 21:35 UTCGHSA enrichment
  8. 2026-08-19 17:33 UTCCISA KEV update
  9. 2026-08-19 17:24 UTCEG score recompute
  10. 2026-08-19 17:24 UTCVendor advisory
  11. 2026-08-19 17:24 UTCGHSA enrichment
  12. 2026-08-19 16:59 UTCEPSS rescore
  13. 2026-08-19 13:13 UTCVendor advisory
  14. 2026-08-19 13:13 UTCGHSA enrichment
  15. 2026-08-19 09:02 UTCVendor advisory
  16. 2026-08-19 09:02 UTCGHSA enrichment
  17. 2026-08-19 04:48 UTCVendor advisory
  18. 2026-08-19 04:48 UTCGHSA enrichment
  19. 2026-08-19 00:37 UTCVendor advisory
  20. 2026-08-19 00:37 UTCGHSA enrichment
  21. 2026-08-18 20:26 UTCVendor advisory
  22. 2026-08-18 20:26 UTCGHSA enrichment
  23. 2026-08-18 16:58 UTCCISA KEV update
  24. 2026-08-18 16:16 UTCEG score recompute
  25. 2026-08-18 16:16 UTCVendor advisory
  26. 2026-08-18 16:15 UTCGHSA enrichment
  27. 2026-08-18 13:42 UTCEPSS rescore
  28. 2026-08-18 12:04 UTCVendor advisory
  29. 2026-08-18 12:04 UTCGHSA enrichment
  30. 2026-08-18 07:48 UTCVendor advisory
  31. 2026-08-18 07:48 UTCGHSA enrichment
  32. 2026-08-18 03:37 UTCVendor advisory
  33. 2026-08-18 03:37 UTCGHSA enrichment
  34. 2026-08-17 23:25 UTCVendor advisory
  35. 2026-08-17 23:25 UTCGHSA enrichment
  36. 2026-08-17 19:14 UTCVendor advisory
  37. 2026-08-17 19:14 UTCGHSA enrichment
  38. 2026-08-17 15:03 UTCEG score recompute
  39. 2026-08-17 15:03 UTCVendor advisory
  40. 2026-08-17 15:03 UTCGHSA enrichment
  41. 2026-08-17 13:56 UTCCISA KEV update
  42. 2026-08-17 10:52 UTCVendor advisory
  43. 2026-08-17 10:52 UTCGHSA enrichment
  44. 2026-08-17 06:41 UTCVendor advisory
  45. 2026-08-17 06:41 UTCGHSA enrichment
  46. 2026-08-17 02:30 UTCVendor advisory
  47. 2026-08-17 02:30 UTCGHSA enrichment
  48. 2026-08-16 22:19 UTCVendor advisory
  49. 2026-08-16 22:19 UTCGHSA enrichment
  50. 2026-08-16 18:08 UTCEG score recompute
  51. 2026-08-16 18:08 UTCVendor advisory
  52. 2026-08-16 18:08 UTCGHSA enrichment
  53. 2026-08-16 13:57 UTCVendor advisory
  54. 2026-08-16 13:57 UTCGHSA enrichment
  55. 2026-08-16 09:45 UTCVendor advisory
  56. 2026-08-16 09:45 UTCGHSA enrichment
  57. 2026-08-16 05:34 UTCEG score recompute
  58. 2026-08-16 05:34 UTCVendor advisory
  59. 2026-08-16 05:34 UTCGHSA enrichment
  60. 2026-08-16 02:09 UTCEPSS rescore
  61. 2026-08-16 01:24 UTCVendor advisory
  62. 2026-08-16 01:24 UTCGHSA enrichment
  63. 2026-08-15 21:13 UTCVendor advisory
  64. 2026-08-15 21:13 UTCGHSA enrichment
  65. 2026-08-15 17:02 UTCVendor advisory
  66. 2026-08-15 17:02 UTCGHSA enrichment
  67. 2026-08-15 12:51 UTCVendor advisory
  68. 2026-08-15 12:51 UTCGHSA enrichment
  69. 2026-08-15 08:40 UTCVendor advisory
  70. 2026-08-15 08:40 UTCGHSA enrichment
  71. 2026-08-15 04:29 UTCEG score recompute
  72. 2026-08-15 04:29 UTCVendor advisory
  73. 2026-08-15 04:29 UTCGHSA enrichment
  74. 2026-08-15 01:25 UTCEPSS rescore
  75. 2026-08-15 00:18 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_exploit
    First seen Jul 16, 2013

    CVE-2013-2596 exploit for android

    Open source ↗

Frequently asked(6)

What is CVE-2013-2596?
CVE-2013-2596 is a critical vulnerability published on April 13, 2013. 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,…
When was CVE-2013-2596 disclosed?
CVE-2013-2596 was first published in the National Vulnerability Database on April 13, 2013, with the most recent update on April 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-2596 actively exploited?
Yes. CISA added CVE-2013-2596 to the Known Exploited Vulnerabilities catalog on September 15, 2022, affecting Linux Kernel. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2013-2596?
CVE-2013-2596 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2013-2596?
CVE-2013-2596 affects Linux Kernel. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2013-2596?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-2596, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-2596

Explore →

Is Your Infrastructure Affected by CVE-2013-2596?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs