Threats / Linux / CVE-2013-6282
CVE-2013-6282
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Linux Kernel vulnerability
The Linux kernel's get_user and put_user API functions fail to validate target addresses on ARM v6k/v7 platforms, allowing applications to read and write kernel memory.
Verdict
Today item — known-exploited.
A local attacker can exploit improper input validation in kernel memory access functions to read and write arbitrary kernel memory, enabling privilege escalation from unprivileged user context to kernel-level access.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-09-15).
Probability (EPSS)
EPSS 0.39711 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Linux, Kernel. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a user-space application that calls get_user or put_user with an unvalidated kernel memory address.
Business
An unprivileged user gains the ability to access kernel memory without proper authorization checks.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I read sensitive kernel data structures or write to kernel memory to modify security-critical state.
Business
Kernel integrity is compromised, enabling further exploitation and system compromise.
3
Lateral reach — past segmentation narrative 3
Attacker
I escalate my privileges by modifying kernel structures or injecting code into kernel execution context.
Business
The attacker gains root-level control of the affected system, leading to complete system compromise.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05