Home/CVE/The mem_write function in the Linux kernel before 3.2.2, when ASLR is disabled, does not properly check permissions when
CVE
CVE-2012-0056
The mem_write function in the Linux kernel before 3.2.2, when ASLR is disabled, does not properly check permissions when
The mem_write function in the Linux kernel before 3.2.2, when ASLR is disabled, does not properly check permissions when writing to /proc/<pid>/mem, which allows local users to gain privileges by modifying process memory, as demonstrated by Mempodipper.
MEDIUM · CVSS 6.9
EPSS 0.64291
Act now
- EPSS ≥ 0.50 - high probability of exploitation in the next 30 days
- EPSS percentile: top 2% of all CVEs by exploitation likelihood
- Public exploit or PoC is available
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2012-0056, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
⬡
Weakness Classification
▤
Affected Products & Versions
2linux kernel>= 2.6.39 and < 3.0.18
linux kernel>= 3.1 and < 3.2.2
⚠
Public Exploits & PoCs
17These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted.
📦
Fixed versions by distribution
36The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
oracle allkernel open
oracle allkernel-debug fixed in 0:2.6.32-220.4.1.el6
oracle allkernel-debug-devel open
oracle allkernel-devel fixed in 0:2.6.32-220.4.1.el6
oracle allkernel-firmware open
oracle allkernel-headers open
oracle allkernel-uek open
oracle allkernel-uek-debug fixed in 0:2.6.32-300.7.1.el6uek
oracle allkernel-uek-debug-devel fixed in 0:2.6.32-300.7.1.el6uek
oracle allkernel-uek-devel fixed in 0:2.6.32-300.7.1.el6uek
oracle allkernel-uek-firmware fixed in 0:2.6.32-300.7.1.el6uek
oracle allkernel-uek-headers open
oracle allmlnx_en-2.6.32-300.7.1.el6uek fixed in 0:1.5.7-0.1
oracle allmlnx_en-2.6.32-300.7.1.el6uekdebug open
oracle allofa-2.6.32-300.7.1.el5uek fixed in 0:1.5.1-4.0.53
oracle allofa-2.6.32-300.7.1.el5uekdebug fixed in 0:1.5.1-4.0.53
oracle allofa-2.6.32-300.7.1.el6uek fixed in 0:1.5.1-4.0.47
oracle allofa-2.6.32-300.7.1.el6uekdebug open
oracle allperf fixed in 0:2.6.32-220.4.1.el6
oracle allpython-perf fixed in 0:2.6.32-220.4.1.el6
suse sle15kernel-default fixed in 0:4.12.14-23.1
suse sle15kernel-default-base open
suse sle15kernel-default-devel open
suse sle15kernel-default-extra fixed in 0:4.12.14-23.1
suse sle15kernel-default-man open
suse sle15kernel-devel open
suse sle15kernel-devel-rt open
suse sle15kernel-docs fixed in 0:4.12.14-23.1
suse sle15kernel-macros open
suse sle15kernel-obs-build fixed in 0:4.12.14-23.1
suse sle15kernel-source open
suse sle15kernel-source-azure open
suse sle15kernel-source-rt open
suse sle15kernel-syms fixed in 0:4.12.14-23.1
suse sle15kernel-vanilla-base fixed in 0:4.12.14-23.1
suse sle15reiserfs-kmp-default fixed in 0:4.12.14-23.1
▣
Scoring & Timeline
6.9
MEDIUM · CVSS v2 (legacy) · [email protected]
This CVE predates CVSS v3; the legacy v2 score is shown so triage still has a severity to work with.
v2 Vector
AV:L/AC:M/Au:N/C:C/I:C/A:C
⚑
Vendor Advisories
7🔗
References & Sources
14Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
http://blog.zx2c4.com/749Third Party Advisory
http://secunia.com/advisories/47708Broken Link
http://ubuntu.com/usn/usn-1336-1Third Party Advisory
http://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.2.2Vendor Advisory