CVE-2013-2595
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe device-initialization functionality in the MSM camera driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, enables MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap interface, which allows attackers to gain privileges via a crafted application.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a privilege escalation vulnerability in the MSM camera driver for Linux kernel 2.6.x and 3.x used in Qualcomm-based Android devices. The driver enables the MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl with an unrestricted mmap interface, allowing a local attacker to map arbitrary memory regions and potentially escalate privileges to root.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.6.29= 3.2.54= 3.2.55= 3.2.56= 3.2.57= 3.2.58= 3.2.59= 3.2.60= 3.2.61= 3.2.62= 3.4.72= 3.4.73CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check kernel versionRun 'uname -r' or 'cat /proc/version' to identify the running kernel versionAffected if Kernel version matches 2.6.29, 3.2.54-3.2.62, or 3.4.72-3.4.73
-
Verify MSM camera driver presenceCheck for the MSM camera driver module by running 'lsmod | grep -i msm_camera' or look for camera-related device nodes in /dev/video* or /dev/msm_*Affected if MSM camera driver is loaded or the /dev/msm_* camera device nodes exist
-
Confirm vulnerable ioctl interface existsCheck if the MSM camera device supports the SET_MEM_MAP_INFO ioctl by examining the driver source or using 'cat /sys/class/video4linux/video*/name' to identify camera devicesAffected if The MSM camera driver with the vulnerable ioctl interface is present on the device
-
Check device access permissionsRun 'ls -la /dev/msm_*' or 'ls -la /dev/video*' to check who can access the camera device filesAffected if The camera device is world-readable/writable or accessible by unprivileged users
The system is affected if it runs a matching kernel version and has the MSM camera driver with the unrestricted ioctl interface accessible to unprivileged users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict the mmap interface in the MSM camera driver by implementing proper access controls and validation on the ioctl calls to prevent unprivileged users from mapping restricted memory regions.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2595 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-2595 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data