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 version has been published for CVE-2014-0196 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

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 49.9%, placing it in the 98th 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·Added 2023-05-12 — agencies required to remediate by 2023-06-02

CVE-2014-0196

Published

May 7, 2014

Updated

Apr 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

8 known

EPSS Exploitation Probability

via FIRST.org ↗

49.9%probability of exploitation in next 30 days

High Risk98th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-0196 in your stack?

O3 detects CVE-2014-0196 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works