CVE-2014-0196
KEVLinux Kernel Race Condition Vulnerability
Description
Linux Kernel contains a race condition vulnerability within the n_tty_write function that allows local users to cause a denial-of-service (DoS) or gain privileges via read and write operations with long strings.
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.
CVSS 3.1 vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HPublishedMay 7, 2014
Last modifiedJun 17, 2026
Added to KEVMay 12, 2023
Remediation dueJun 2, 2023
References
- bugzilla.novell.com/show_bug.cgi?id=875690Issue TrackingPermissions Required
- git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=4291086b1f081b869c6d79e5b7441633dc3ace00Broken Link
- linux.oracle.com/errata/ELSA-2014-0771.htmlThird Party Advisory
- lists.opensuse.org/opensuse-security-announce/2014-05/msg00007.htmlMailing ListThird Party Advisory
- lists.opensuse.org/opensuse-security-announce/2014-05/msg00012.htmlMailing ListThird Party Advisory
- pastebin.com/raw.php?i=yTSFUBgZExploitMailing List
- rhn.redhat.com/errata/RHSA-2014-0512.htmlThird Party Advisory
- secunia.com/advisories/59218Not Applicable
- secunia.com/advisories/59262Broken Link
- secunia.com/advisories/59599Broken Link
- source.android.com/security/bulletin/2016-07-01.htmlNot Applicable
- support.f5.com/kb/en-us/solutions/public/15000/300/sol15319.htmlThird Party Advisory
0 recent articles mention this CVE
60
Risk assessment · High
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1242 days
- CVSS
- 5.5 MEDIUM
- EPSS (30-day exploit probability)
- 20.3% · top 3% of all CVEs
- Weakness
- CWE-362
Recommended actions
- 1.The impacted product is end-of-life and should be disconnected if still in use.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.