CVE-2015-1805

HIGHCVSS v2 · 7.27.2—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.2 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:L/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 1.2% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Elevated
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS v2: 7.2Exploit: Elevated riskExposed: 0

A fix is available — apply it.

The (1) pipe_read and (2) pipe_write implementations in fs/pipe.c in the Linux kernel before 3.16 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."

CVSS v2.0 (legacy)
7.2HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.2(low)
EG Risk
53(Track)
EG Risk 53/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 computed
Severity72% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
71%
KEV
Not listed

Published

August 8, 2015

Last Modified

May 6, 2026

References (72)

Vendor Advisories for CVE-2015-1805(10)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-image-3.13.0-58-generic-lpae (3.13.0-58.97~precise1) @ precise2026-05-23ubuntu
ubuntulinux-image-3.2.0-88-highbank (3.2.0-88.126) @ precise2026-05-23ubuntu
ubuntulinux-image-3.2.0-1468-omap4 (3.2.0-1468.89) @ precise2026-05-23ubuntu
ubuntulinux-image-extra-3.13.0-58-generic (3.13.0-58.97) @ trusty2026-05-23ubuntu
redhatkernel-0:2.6.32-358.62.1.el62015-07-07redhat
redhatkernel-0:2.6.32-431.59.1.el62015-06-30redhat
redhatkernel-0:2.6.18-238.56.1.el52015-06-25redhat
redhatkernel-rt-1:3.10.0-229.rt56.153.el6rt2015-06-23redhat
redhatkernel-rt-0:3.10.0-229.7.2.rt56.141.6.el7_12015-06-23redhat
redhatkernel-0:3.10.0-229.7.2.ael7b2015-06-23redhat
redhatkernel-0:2.6.18-348.31.2.el52015-06-16redhat
redhatkernel-0:2.6.32-220.63.2.el62015-06-09redhat
redhatkernel-0:2.6.32-504.23.4.el62015-06-09redhat
redhatkernel-0:2.6.18-406.el52015-06-02redhat

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

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux—3.16.2-2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—3.16.2-2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—3.16.2-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—3.16.2-2—
Debian:6.0(1)
PackageVulnerable rangeFixed inDependents
linux-2.62.6.32-30 ... 2.6.32-48squeeze9 (38 versions)2.6.32-48squeeze12—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
linux3.2.41-2 ... 3.2.68-1+deb7u2~bpo60+1 (41 versions)3.2.68-1+deb7u2—

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 20× 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 141 total refreshes for this CVE.

  1. 2026-09-19 09:36 UTCOSV refresh
  2. 2026-09-18 19:22 UTCEPSS rescore
  3. 2026-09-17 19:21 UTCEPSS rescore
  4. 2026-09-15 03:05 UTCEPSS rescore
  5. 2026-09-12 14:55 UTCEPSS rescore
  6. 2026-09-11 09:31 UTCEPSS rescore
  7. 2026-09-10 09:26 UTCEPSS rescore
  8. 2026-09-07 15:56 UTCEPSS rescore
  9. 2026-09-06 13:42 UTCEPSS rescore
  10. 2026-09-05 15:23 UTCEPSS rescore
  11. 2026-09-04 13:55 UTCEPSS rescore
  12. 2026-09-02 14:07 UTCEPSS rescore
  13. 2026-09-01 03:31 UTCEPSS rescore
  14. 2026-08-31 13:04 UTCOSV refresh
  15. 2026-08-30 19:12 UTCEPSS rescore
  16. 2026-08-27 14:20 UTCEPSS rescore
  17. 2026-08-26 14:41 UTCEPSS rescore
  18. 2026-08-25 13:44 UTCEPSS rescore
  19. 2026-08-21 23:44 UTCEPSS rescore
  20. 2026-08-20 22:50 UTCEPSS rescore
  21. 2026-08-19 16:59 UTCEPSS rescore
  22. 2026-08-18 13:43 UTCEPSS rescore
  23. 2026-08-16 14:51 UTCEPSS rescore
  24. 2026-08-16 02:09 UTCEPSS rescore
  25. 2026-08-15 01:25 UTCEPSS rescore
Show 75 more
  1. 2026-08-14 18:24 UTCOSV refresh
  2. 2026-08-12 13:46 UTCEPSS rescore
  3. 2026-08-09 13:42 UTCEPSS rescore
  4. 2026-08-08 16:31 UTCEPSS rescore
  5. 2026-08-07 16:22 UTCEPSS rescore
  6. 2026-08-06 13:42 UTCEPSS rescore
  7. 2026-08-05 19:12 UTCEPSS rescore
  8. 2026-08-04 15:04 UTCEPSS rescore
  9. 2026-08-02 02:22 UTCEPSS rescore
  10. 2026-08-01 04:11 UTCEPSS rescore
  11. 2026-07-30 16:23 UTCEPSS rescore
  12. 2026-07-30 06:54 UTCOSV refresh
  13. 2026-07-30 01:26 UTCEPSS rescore
  14. 2026-07-28 15:31 UTCEPSS rescore
  15. 2026-07-26 14:50 UTCEPSS rescore
  16. 2026-07-26 13:53 UTCEG score recompute▲ 7.20
  17. 2026-07-24 14:13 UTCEPSS rescore
  18. 2026-07-23 14:14 UTCEPSS rescore
  19. 2026-07-23 01:16 UTCEG score recompute
  20. 2026-07-23 00:19 UTCEG score recompute
  21. 2026-07-22 21:57 UTCEG score recompute
  22. 2026-07-22 14:04 UTCEPSS rescore
  23. 2026-07-21 15:21 UTCEPSS rescore
  24. 2026-07-21 15:21 UTCEPSS rescore
  25. 2026-07-20 17:03 UTCEPSS rescore
  26. 2026-07-19 14:27 UTCEPSS rescore
  27. 2026-07-19 14:27 UTCEPSS rescore
  28. 2026-07-19 02:26 UTCEPSS rescore
  29. 2026-07-19 02:26 UTCEPSS rescore
  30. 2026-07-18 10:00 UTCEPSS rescore
  31. 2026-07-16 16:59 UTCEPSS rescore
  32. 2026-07-16 16:59 UTCEPSS rescore
  33. 2026-07-15 16:54 UTCEPSS rescore
  34. 2026-07-15 16:54 UTCEPSS rescore
  35. 2026-07-15 01:56 UTCEPSS rescore
  36. 2026-07-13 22:26 UTCEPSS rescore
  37. 2026-07-12 16:07 UTCOSV refresh
  38. 2026-07-12 05:42 UTCEPSS rescore
  39. 2026-07-11 08:23 UTCEPSS rescore
  40. 2026-07-09 19:05 UTCEPSS rescore
  41. 2026-07-08 15:10 UTCEPSS rescore
  42. 2026-07-07 13:42 UTCEPSS rescore
  43. 2026-07-06 16:24 UTCEPSS rescore
  44. 2026-07-06 02:20 UTCEPSS rescore
  45. 2026-07-05 02:26 UTCEPSS rescore
  46. 2026-07-04 06:27 UTCEPSS rescore
  47. 2026-07-02 15:21 UTCEPSS rescore
  48. 2026-07-01 15:02 UTCEPSS rescore
  49. 2026-07-01 15:02 UTCEPSS rescore
  50. 2026-06-30 23:19 UTCEPSS rescore
  51. 2026-06-30 23:19 UTCEPSS rescore
  52. 2026-06-29 14:03 UTCEPSS rescore
  53. 2026-06-28 14:03 UTCEPSS rescore
  54. 2026-06-28 04:53 UTCEPSS rescore
  55. 2026-06-27 03:05 UTCEPSS rescore
  56. 2026-06-25 13:47 UTCEPSS rescore
  57. 2026-06-25 13:47 UTCEPSS rescore
  58. 2026-06-24 14:02 UTCEPSS rescore
  59. 2026-06-24 14:02 UTCEPSS rescore
  60. 2026-06-23 21:30 UTCEPSS rescore
  61. 2026-06-23 21:29 UTCOSV refresh
  62. 2026-06-22 14:23 UTCEPSS rescore
  63. 2026-06-22 14:22 UTCEPSS rescore
  64. 2026-06-21 14:54 UTCEPSS rescore
  65. 2026-06-21 01:57 UTCEPSS rescore
  66. 2026-06-21 01:57 UTCEPSS rescore
  67. 2026-06-19 19:23 UTCEPSS rescore
  68. 2026-06-19 19:23 UTCEPSS rescore
  69. 2026-06-18 17:50 UTCEPSS rescore
  70. 2026-06-18 17:49 UTCEPSS rescore
  71. 2026-06-17 17:49 UTCEPSS rescore
  72. 2026-06-16 17:50 UTCEPSS rescore
  73. 2026-06-16 17:49 UTCEPSS rescore
  74. 2026-06-15 17:45 UTCEPSS rescore
  75. 2026-06-14 23:14 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (4 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCireshchaminda1/Android-Privilege-Escalation-Remote-Access-Vulnerability-CVE-2015-1805
    First seen Feb 12, 2023

    AndroRAT is a capability that can be used to inject a root exploit as a silent installation to perform a malicious task on the device. This AndroRAT is designed to exploit CVE-2015-1805, a vulnerability that was discovered and made public in 2016.

    Open source ↗
  • GitHub PoCFloatingGuy/cve-2015-1805
    First seen Jun 30, 2016
    Open source ↗
  • GitHub PoCdosomder/iovyroot
    First seen Apr 1, 2016

    CVE-2015-1805 root tool

    Open source ↗
  • GitHub PoCpanyu6325/CVE-2015-1805
    First seen Mar 24, 2016
    Open source ↗

Frequently asked(4)

What is CVE-2015-1805?
CVE-2015-1805 is a high vulnerability published on August 8, 2015. The (1) piperead and (2) pipewrite implementations in fs/pipe.c in the Linux kernel before 3.16 do not properly consider the side effects of failed copytouserinatomic and copyfromuserinatomic calls, which allows local users to cause a denial of service (system crash) or possibly gain privileges via…
When was CVE-2015-1805 disclosed?
CVE-2015-1805 was first published in the National Vulnerability Database on August 8, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-1805 actively exploited?
CVE-2015-1805 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 28.8% of all scored CVEs.
How do I remediate CVE-2015-1805?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-1805, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-1805

Explore →

Is Your Infrastructure Affected by CVE-2015-1805?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs