The (1) pipe_read and (2) pipe_write implementations in fs/pipe.c in a certain Linux kernel backport in the linux package before 3.2.73-2+deb7u3 on Debian wheezy and the kernel package before 3.10.0-229.26.2 on Red Hat Enterprise Linux (RHEL) 7.1 do not properly consider the side effects of failed __copy_to_user_inatomic and __copy_from_user_inatomic calls, which allows local users to cause a denial of service (system crash) or possibly gain privileges via a crafted application, aka an "I/O vector array overrun." NOTE: this vulnerability exists because of an incorrect fix for CVE-2015-1805.
CVE-2016-0774
Score 6.8 from GitHub Security Advisory published 2022-05-17. NVD baseline CVSS 6.8; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.8
- EG Score
- 6.8(medium)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity68% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
April 27, 2016
Last Modified
June 17, 2026
References (48)
- secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2016-04/msg00025.html
- secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2016-04/msg00026.html
- secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2016-04/msg00027.html
- secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2016-04/msg00028.html
- secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2016-04/msg00029.html
- secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2016-04/msg00030.html
- secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2016-04/msg00031.html
- secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2016-04/msg00032.html
- secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2016-04/msg00033.html
- secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2016-04/msg00034.html
- secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2016-04/msg00036.html
- secalert@redhathttp://lists.opensuse.org/opensuse-security-announce/2016-04/msg00037.html
- secalert@redhathttp://rhn.redhat.com/errata/RHSA-2016-0494.html
- secalert@redhathttp://rhn.redhat.com/errata/RHSA-2016-0617.html
- secalert@redhathttp://source.android.com/security/bulletin/2016-05-01.html
Patch Availability(8)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | linux-image-3.13.0-86-generic-lpae (3.13.0-86.130~precise1) @ precise | 2026-05-22 | ubuntu |
| ubuntu | linux-image-3.2.0-1480-omap4 (3.2.0-1480.106) @ precise | 2026-05-22 | ubuntu |
| ubuntu | linux-image-3.2.0-102-virtual (3.2.0-102.142) @ precise | 2026-05-22 | ubuntu |
| ubuntu | linux-image-extra-3.13.0-86-generic (3.13.0-86.130) @ trusty | 2026-05-22 | ubuntu |
| redhat | kernel-0:2.6.32-504.46.1.el6 | 2016-04-12 | redhat |
| redhat | kernel-0:2.6.32-573.22.1.el6 | 2016-03-22 | redhat |
| redhat | kernel-0:3.10.0-229.26.2.ael7b | 2016-02-02 | redhat |
| redhat | kernel-0:3.10.0-327.el7 | 2015-11-19 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | — | 3.16.2-2 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | — | 3.16.2-2 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | — | 3.16.2-2 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | — | 3.16.2-2 | — |
Debian:6.0(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux-2.6 | 2.6.32-30 ... 2.6.32-48squeeze9 (45 versions) | 2.6.32-48squeeze20 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(8)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
- Red HatRHSA-2015:2152MODERATE2016-02-02
RHSA-2015:2152 — Moderate
- Red HatRHSA-2016:0103MODERATE2016-02-02
RHSA-2016:0103 — Moderate
- Red HatRHSA-2016:0494MODERATE2016-02-02
RHSA-2016:0494 — Moderate
- Red HatRHSA-2016:0617MODERATE2016-02-02
RHSA-2016:0617 — Moderate
- UbuntuUSN-2967-1MEDIUM
Linux kernel vulnerabilities
- UbuntuUSN-2967-2MEDIUM
Linux kernel (OMAP4) vulnerabilities
- UbuntuUSN-2968-1MEDIUM
Linux kernel vulnerabilities
- UbuntuUSN-2968-2MEDIUM
Linux kernel (Trusty HWE) vulnerabilities
Data Freshness Timeline
(refreshed 6× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 126 total refreshes for this CVE.
- 2026-08-20 22:50 UTCEPSS rescore
- 2026-08-19 16:59 UTCEPSS rescore
- 2026-08-18 13:43 UTCEPSS rescore
- 2026-08-16 14:51 UTCEPSS rescore
- 2026-08-16 02:09 UTCEPSS rescore
- 2026-08-15 01:25 UTCEPSS rescore
- 2026-08-14 12:54 UTCOSV refresh
- 2026-08-12 13:46 UTCEPSS rescore
- 2026-08-11 13:36 UTCEPSS rescore
- 2026-08-09 13:42 UTCEPSS rescore
- 2026-08-08 16:32 UTCEPSS rescore
- 2026-08-07 16:22 UTCEPSS rescore
- 2026-08-06 13:42 UTCEPSS rescore
- 2026-08-05 19:12 UTCEPSS rescore
- 2026-08-04 15:04 UTCEPSS rescore
- 2026-08-04 10:31 UTCEPSS rescore
- 2026-08-01 04:11 UTCEPSS rescore
- 2026-07-30 01:26 UTCEPSS rescore
- 2026-07-30 01:26 UTCEPSS rescore
- 2026-07-30 01:07 UTCOSV refresh
- 2026-07-28 15:31 UTCEPSS rescore
- 2026-07-26 14:50 UTCEPSS rescore
- 2026-07-25 14:13 UTCEPSS rescore
- 2026-07-24 14:13 UTCEPSS rescore
- 2026-07-23 14:14 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-23 01:21 UTCEG score recompute
- 2026-07-23 00:22 UTCEG score recompute
- 2026-07-22 22:00 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-20 17:03 UTCEPSS rescore
- 2026-07-19 14:27 UTCEPSS rescore
- 2026-07-19 14:27 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-18 10:00 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-13 22:26 UTCEPSS rescore
- 2026-07-13 22:26 UTCEPSS rescore
- 2026-07-12 10:08 UTCOSV refresh
- 2026-07-12 05:42 UTCEPSS rescore
- 2026-07-11 08:23 UTCEPSS rescore
- 2026-07-09 19:05 UTCEPSS rescore
- 2026-07-09 19:05 UTCEPSS rescore
- 2026-07-08 15:10 UTCEPSS rescore
- 2026-07-07 13:42 UTCEPSS rescore
- 2026-07-07 13:42 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-06 02:20 UTCEPSS rescore
- 2026-07-05 02:26 UTCEPSS rescore
- 2026-07-04 06:28 UTCEPSS rescore
- 2026-07-01 15:02 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-28 14:04 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-27 03:05 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-23 15:50 UTCOSV refresh
- 2026-06-22 14:23 UTCEPSS rescore
- 2026-06-22 14:23 UTCEPSS rescore
- 2026-06-21 14:54 UTCEPSS rescore
- 2026-06-21 14:54 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-19 19:23 UTCEPSS rescore
- 2026-06-19 19:23 UTCEPSS rescore
- 2026-06-18 17:50 UTCEPSS rescore
- 2026-06-17 17:50 UTCEPSS rescore
- 2026-06-17 17:49 UTCEPSS rescore
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-15 17:45 UTCEPSS rescore
- 2026-06-14 23:14 UTCEPSS rescore
- 2026-06-13 22:57 UTCEPSS rescore
- 2026-06-12 23:09 UTCEPSS rescore
- 2026-06-12 23:09 UTCEPSS rescore
- 2026-06-11 13:57 UTCEPSS rescore
- 2026-06-11 13:57 UTCEPSS rescore
- 2026-06-10 22:15 UTCEPSS rescore
- 2026-06-10 13:18 UTCEPSS rescore
- 2026-06-08 14:14 UTCEPSS rescore
- 2026-06-07 15:22 UTCEPSS rescore
- 2026-06-06 20:29 UTCOSV refresh
- 2026-06-06 13:45 UTCEPSS rescore
- 2026-06-05 22:44 UTCEPSS rescore
- 2026-06-05 06:08 UTCEPSS rescore
- 2026-06-05 06:08 UTCEPSS rescore
- 2026-06-04 13:10 UTCEPSS rescore
- 2026-06-04 13:10 UTCEPSS rescore
- 2026-06-02 20:10 UTCEPSS rescore
- 2026-06-01 13:49 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-20
- CVE-2005-0050EG 10.0EPSS p99HIGH
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p91HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
Frequently asked(5)
What is CVE-2016-0774?
When was CVE-2016-0774 disclosed?
Is CVE-2016-0774 actively exploited?
What is the CVSS score of CVE-2016-0774?
How do I remediate CVE-2016-0774?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-0774
Is Your Infrastructure Affected by CVE-2016-0774?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.