Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2014-9683

kernel: buffer overflow in eCryptfs

Overview

Published
3 Mar 2015
Modified
6 May 2026
Low CVE
0 Registry packages
9 OS packages
4 Linux distributions
Yes Fix available

Description

Off-by-one error in the ecryptfs_decode_from_filename function in fs/ecryptfs/crypto.c in the eCryptfs subsystem in the Linux kernel before 3.18.2 allows local users to cause a denial of service (buffer overflow and system crash) or possibly gain privileges via a crafted filename.

Source: OX vulnerability database

Severity

3.6 · LOW

CVSS 2.0 base score, scored by NVD.

Access vector
Local
Access complexity
Low
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
Partial

AV:L/AC:L/Au:N/C:N/I:P/A:P

Weakness: CWE-189

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 10 fixes

Oracle Linux 1 release · 2 packages

fixed 2
dtrace-modules-3-8-13-68-3-5-el7uek kernel-uek
Oracle Linux fixes for CVE-2014-9683
ReleasePackageFixed in
7 dtrace-modules-3-8-13-68-3-5-el7uek 0.4.3-4.el7
7 kernel-uek +5 3.8.13-68.3.5.el7uek

debian 4 releases · 1 package

fixed 4
linux
debian fixes for CVE-2014-9683
ReleasePackageFixed in
11 linux 3.16.7-ckt4-1
12 linux 3.16.7-ckt4-1
13 linux 3.16.7-ckt4-1
14 linux 3.16.7-ckt4-1

echo 1 release · 1 package

fixed 1
linux
echo fixes for CVE-2014-9683
ReleasePackageFixed in
linux 3.16.7-ckt4-1

root.io debian 3 releases · 1 package

fixed 3
rootio-linux
root.io debian fixes for CVE-2014-9683
ReleasePackageFixed in
11 rootio-linux 3.16.7-ckt4-1
12 rootio-linux 3.16.7-ckt4-1
13 rootio-linux 3.16.7-ckt4-1

References

Show all 29 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.