How severe is CVE-2013-2596?

CVE-2013-2596 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2013-2596?

Affected package information for CVE-2013-2596 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2013-2596?

No fixed release is recorded for CVE-2013-2596 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2013-2596 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2013-2596 if there is no patch (or I can't update yet)?

Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Is CVE-2013-2596 actively exploited in the wild?

Yes. There are 9 known exploit references for CVE-2013-2596, including 8 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-2596?

CVE-2013-2596 has an EPSS (Exploit Prediction Scoring System) score of 3.2%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2013-2596 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2013-2596 (Linux Kernel Integer Overflow Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-09-15. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-10-06. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2013-2596?

CVE-2013-2596 is classified as CWE-190 (CWE-190). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-2596 published, and has it been updated?

CVE-2013-2596 was published on April 13, 2013 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

CVE-2013-2596 — Red Hat

HIGHFix: torvalds/linux@b4cbb19

CVE-2013-2596 is a high-severity (CVSS 7.8) CWE-190 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-09-15) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Published

Apr 13, 2013

Updated

Apr 10, 2026

Affected

2 products

Patched

See advisory

Exploits

9 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-09-15. Federal agencies were required to remediate by 2022-10-06.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2013-2596.

EPSS Exploitation Probability

via FIRST.org ↗

3.2%probability of exploitation in next 30 days

Lower Risk-0.12%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2013-2596 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

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.

Affected Products

2 products · 5 configurations

linux kernellinux

≥ 3.5 && < 3.8.9

range

androidmotorola

1 version

4.1.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.