How severe is CVE-2014-0196?

No CVSS score has been assigned to CVE-2014-0196 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-0196?

Affected package information for CVE-2014-0196 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2014-0196?

No fixed release is recorded for CVE-2014-0196 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2014-0196 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2014-0196 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2014-0196 actively exploited in the wild?

Yes. There are 8 known exploit references for CVE-2014-0196, including 1 documented proof-of-concept exploit on Exploit-DB and 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-0196?

CVE-2014-0196 has an EPSS (Exploit Prediction Scoring System) score of 20.3%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2014-0196 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2014-0196 (Linux Kernel Race Condition Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-05-12. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-06-02. The required action was: The impacted product is end-of-life and should be disconnected if still in use. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2014-0196?

CVE-2014-0196 is classified as CWE-362 (CWE-362). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-0196 published, and has it been updated?

CVE-2014-0196 was published on May 7, 2014 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV · ACTIVELY EXPLOITED

CVE-2014-0196 — Oracle

Fix: torvalds/linux@4291086

CVE-2014-0196 is a CWE-362 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-05-12) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Published

May 7, 2014

Updated

Apr 16, 2026

Affected

30 products

Patched

See advisory

Exploits

8 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-05-12. Federal agencies were required to remediate by 2023-06-02.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2014-0196.

EPSS Exploitation Probability

via FIRST.org ↗

20.3%probability of exploitation in next 30 days

Moderate Risk-2.15%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

The n_tty_write function in drivers/tty/n_tty.c in the Linux kernel through 3.14.3 does not properly manage tty driver access in the "LECHO & !OPOST" case, which allows local users to cause a denial of service (memory corruption and system crash) or gain privileges by triggering a race condition involving read and write operations with long strings.

Affected Products

30 products · 50 configurations

ubuntu linuxcanonical

5 versions

10.0412.0412.1013.1014.04

debian linuxdebian

2 versions

6.07.0

Application

big-ip access policy managerf5

≥ 11.1.0 && ≤ 11.5.1

range

Application

big-ip advanced firewall managerf5

≥ 11.3.0 && ≤ 11.5.1

range

Application

big-ip analyticsf5

≥ 11.1.0 && ≤ 11.5.1

range

Application

big-ip application acceleration managerf5

≥ 11.4.0 && ≤ 11.5.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-33516locallinux_x86-64

Linux Kernel 3.14-rc1 < 3.15-rc4 (x64) - Raw Mode PTY Echo Race Condition Privilege Escalation

by Matthew Daley · May 26, 2014

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2014-0196 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This issue did not affect the versions of the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue affected the versions of the Linux kernel packages as shipped with Red Hat Enterprise Linux 6 prior to version kernel-2.6.32-358.6.1.el6, released via RHSA-2013:0744…

Product	Fixed in	Advisory
Red Hat Enterprise Linux 6	`kernel-0:2.6.32-358.6.1.el6`	RHSA-2013:0744
Red Hat Enterprise Linux 6.2 Advanced Update Support	`kernel-0:2.6.32-220.51.1.el6`	RHSA-2014:0520
Red Hat Enterprise Linux 6.3 EUS - Server and Compute Node Only	`kernel-0:2.6.32-279.43.2.el6`	RHSA-2014:0512
Red Hat Enterprise Linux 7	`kernel-0:3.10.0-123.1.2.el7`	RHSA-2014:0678
Red Hat Enterprise MRG 2	`kernel-rt-0:3.10.33-rt32.34.el6rt`	RHSA-2014:0557

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-0196 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2014-0196 — Oracle

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2014-0196 in your dependencies?