dbcve.org
Linux KernelOperating system · Linux

CVE-2014-9410

CRITICAL · 9.8 CVSS v3.1 Published 2016-08-07
Fix available
A fix is available. Upgrade to after 3.19.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The vfe31_proc_general function in drivers/media/video/msm/vfe/msm_vfe31.c in the MSM-VFE31 driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not validate a certain id value, which allows attackers to gain privileges or cause a denial of service (memory corruption) via an application that makes a crafted ioctl call.

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 · high confidence

Missing validation vulnerability in the Linux kernel's MSM-VFE31 camera/video driver (msm_vfe31.c). The vfe31_proc_general function does not validate an id value from userspace ioctl calls, allowing attackers to trigger memory corruption or escalate privileges via crafted ioctl calls.

MitigationApply vendor kernel patch that adds proper validation of the id parameter in vfe31_proc_general function; restrict access to /dev/video* nodes and monitor for suspicious ioctl activity until patched.

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
Linux KernelOperating system
Affected:>= 3.0, <= 3.19.8

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check your kernel version
    Run `uname -r` or `cat /proc/version` to obtain the running kernel version
    Affected if The kernel version is between 3.0 and 3.19.8 inclusive (e.g., 3.4.0, 3.10.25, 3.18.5)
  2. Verify the MSM-VFE31 driver is present
    Check for the existence of the msm_vfe31 driver by searching kernel modules with `lsmod | grep -i vfe` or checking for related video driver files in /sys/module/ or /drivers/media/
    Affected if The msm_vfe31, vfe31, or related MSM camera driver module is loaded or compiled into the kernel
  3. Identify video device nodes
    List video device nodes with `ls -la /dev/video*` or check /dev/ for video0, video1, etc.
    Affected if Video device nodes exist under /dev/video* and are accessible
  4. Confirm hardware platform is Qualcomm MSM
    Check hardware info via `cat /proc/cpuinfo` for ARM processor info, or check `lspci`/`lsusb` output, or check /sys/bus/ for platform devices. The msm_vfe31 driver is specific to Qualcomm MSM chipsets.
    Affected if The system uses a Qualcomm Snapdragon or MSM chipset (common in older Android phones, some embedded devices)
  5. Test for accessible ioctl interface
    Attempt to list available ioctl commands on video devices if you have access: use `v4l2-ctl --list-devices` or check device permissions with `ls -la /dev/video*`
    Affected if The /dev/video* nodes are readable/writable by the user or group, allowing direct ioctl calls

You are affected if your kernel version is 3.0-3.19.8, the msm_vfe31 camera driver is present, and you are running on Qualcomm MSM hardware with accessible video device nodes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.19.8
Interim mitigation

Apply vendor kernel patch that adds proper validation of the id parameter in vfe31_proc_general function; restrict access to /dev/video* nodes and monitor for suspicious ioctl activity until patched.

Recommended fix High confidence

Linux Kernel 4.0 or later (or the relevant vendor kernel release that includes this fix)

  1. Upgrade the Linux kernel to version 4.0 or later. This vulnerability was in the MSM-VFE31 driver (drivers/media/video/msm/vfe/msm_vfe31.c) which has been fixed in mainline kernel 4.0 and later releases.
  2. If kernel 4.x is not immediately feasible, apply the vendor-specific patch from Qualcomm's CodeAurora repository for the msm_vfe31.c driver.
  3. After patching or upgrading, verify the fix by ensuring the vfe31_proc_general function now properly validates the id parameter before use.
  4. Reboot the system into the new/patched kernel and test video capture functionality on affected MSM devices.
Caveat Kernel major version upgrades (e.g., 3.x to 4.x) may introduce driver compatibility changes or require updates to device-specific firmware; ensure dependent drivers and hardware support the target kernel version before deployment.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-9410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-9410 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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