CVE-2014-4171

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

mm/shmem.c in the Linux kernel through 3.15.1 does not properly implement the interaction between range notification and hole punching, which allows local users to cause a denial of service (i_mutex hold) by using the mmap system call to access a hole, as demonstrated by interfering with intended shmem activity by blocking completion of (1) an MADV_REMOVE madvise call or (2) an FALLOC_FL_PUNCH_HOLE fallocate call.

CVSS v3
—
EG Score
0.0(none)
EPSS
35.4%
KEV
Not listed

Published

June 23, 2014

Last Modified

May 6, 2026

References (28)

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-image-3.2.0-1452-omap4 (3.2.0-1452.72) @ precise2026-05-28ubuntu
ubuntulinux-image-3.2.0-68-highbank (3.2.0-68.102) @ precise2026-05-28ubuntu
ubuntulinux-image-3.13.0-35-generic (3.13.0-35.62~precise1) @ precise2026-05-28ubuntu
ubuntulinux-image-extra-3.13.0-35-generic (3.13.0-35.62) @ trusty2026-05-28ubuntu
redhatkernel-0:3.10.0-123.20.1.el72015-01-28redhat
redhatkernel-rt-0:3.10.33-rt32.51.el6rt2014-09-29redhat

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.

All Vendor Advisories

(6)

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.

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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.

  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-05 02:26 UTCEPSS rescore
  5. 2026-07-04 23:26 UTCOSV refresh
  6. 2026-07-04 06:27 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-07-01 15:02 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-29 14:02 UTCEPSS rescore
  12. 2026-06-28 14:03 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-28 04:53 UTCEPSS rescore
  15. 2026-06-27 03:05 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-25 13:47 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-23 21:30 UTCEPSS rescore
  22. 2026-06-22 14:22 UTCEPSS rescore
  23. 2026-06-22 14:22 UTCEPSS rescore
  24. 2026-06-21 14:54 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
Show 54 more
  1. 2026-06-19 19:23 UTCEPSS rescore
  2. 2026-06-18 17:49 UTCEPSS rescore
  3. 2026-06-18 17:49 UTCEPSS rescore
  4. 2026-06-17 17:49 UTCEPSS rescore
  5. 2026-06-17 17:49 UTCEPSS rescore
  6. 2026-06-16 17:50 UTCEPSS rescore
  7. 2026-06-16 17:49 UTCEPSS rescore
  8. 2026-06-16 17:49 UTCEPSS rescore
  9. 2026-06-16 11:14 UTCOSV refresh
  10. 2026-06-14 23:14 UTCEPSS rescore
  11. 2026-06-13 22:57 UTCEPSS rescore
  12. 2026-06-12 23:08 UTCEPSS rescore
  13. 2026-06-11 13:57 UTCEPSS rescore
  14. 2026-06-10 22:15 UTCEPSS rescore
  15. 2026-06-08 14:14 UTCEPSS rescore
  16. 2026-06-07 15:22 UTCEPSS rescore
  17. 2026-06-06 13:45 UTCEPSS rescore
  18. 2026-06-06 13:45 UTCEPSS rescore
  19. 2026-06-05 22:44 UTCEPSS rescore
  20. 2026-06-05 06:08 UTCEPSS rescore
  21. 2026-06-05 06:08 UTCEPSS rescore
  22. 2026-06-04 13:09 UTCEPSS rescore
  23. 2026-06-04 13:09 UTCEPSS rescore
  24. 2026-06-02 20:10 UTCEPSS rescore
  25. 2026-06-02 20:10 UTCEPSS rescore
  26. 2026-06-01 13:49 UTCEPSS rescore
  27. 2026-06-01 13:49 UTCEPSS rescore
  28. 2026-05-31 22:28 UTCEPSS rescore
  29. 2026-05-31 22:28 UTCEPSS rescore
  30. 2026-05-31 00:14 UTCEPSS rescore
  31. 2026-05-31 00:14 UTCEPSS rescore
  32. 2026-05-29 13:41 UTCEPSS rescore
  33. 2026-05-28 18:21 UTCEG score recompute
  34. 2026-05-28 18:21 UTCVendor advisory
  35. 2026-05-28 18:21 UTCGHSA enrichment
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-28 13:42 UTCEPSS rescore
  38. 2026-05-28 13:42 UTCEPSS rescore
  39. 2026-05-28 04:03 UTCOSV refresh
  40. 2026-05-27 13:38 UTCEPSS rescore
  41. 2026-05-27 13:38 UTCEPSS rescore
  42. 2026-05-26 13:41 UTCEPSS rescore
  43. 2026-05-26 07:16 UTCEPSS rescore
  44. 2026-05-24 16:43 UTCEPSS rescore
  45. 2026-05-22 21:15 UTCEPSS rescore
  46. 2026-05-22 21:15 UTCEPSS rescore
  47. 2026-05-22 21:15 UTCEPSS rescore
  48. 2026-05-21 22:39 UTCEPSS rescore
  49. 2026-05-20 22:37 UTCEPSS rescore
  50. 2026-05-20 22:37 UTCEPSS rescore
  51. 2026-05-20 22:37 UTCEPSS rescore
  52. 2026-05-20 11:21 UTCEPSS rescore
  53. 2026-05-20 11:21 UTCEPSS rescore
  54. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2014-4171?
CVE-2014-4171 is a none vulnerability published on June 23, 2014. mm/shmem.c in the Linux kernel through 3.15.1 does not properly implement the interaction between range notification and hole punching, which allows local users to cause a denial of service (imutex hold) by using the mmap system call to access a hole, as demonstrated by interfering with intended…
When was CVE-2014-4171 disclosed?
CVE-2014-4171 was first published in the National Vulnerability Database on June 23, 2014, 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-2014-4171 actively exploited?
CVE-2014-4171 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2014-4171?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-4171, 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

Explore the affected products and dependency analysis for CVE-2014-4171

Explore →

Is Your Infrastructure Affected by CVE-2014-4171?

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

Start Free Scan →Browse All CVEs