CVE-2026-43178

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

procfs: fix possible double mmput() in do_procmap_query()

When user provides incorrectly sized buffer for build ID for PROCMAP_QUERY we return with -ENAMETOOLONG error. After recent changes this condition happens later, after we unlocked mmap_lock/per-VMA lock and did mmput(), so original goto out is now wrong and will double-mmput() mm_struct. Fix by jumping further to clean up only vm_file and name_buf.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
—
EPSS
3.2%
KEV
Not listed

Published

May 6, 2026

Last Modified

July 15, 2026

Advisory Details (4)

Auto-updated May 12, 2026
No patch confirmed yet.
generic

procfs: fix possible double mmput() in do_procmap_query() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f9fe092084cd04deea18747f58a2304026e76aaa
generic

procfs: fix possible double mmput() in do_procmap_query() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/90f5e87c9b75833b9ef3a4415b92c0247f28ab2f
generic

procfs: fix possible double mmput() in do_procmap_query() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8adaff87db143583e08eec4f4e7788f1ef8af94d
generic

procfs: fix possible double mmput() in do_procmap_query() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61dc9f776705d6db6847c101b98fa4f0e9eb6fa3

Vendor Advisories for CVE-2026-43178(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.75—osv

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.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

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

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-43178?
CVE-2026-43178 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: procfs: fix possible double mmput() in doprocmapquery() When user provides incorrectly sized buffer for build ID for PROCMAP_QUERY we return with -ENAMETOOLONG error. After recent changes this condition happens later, after we…
When was CVE-2026-43178 disclosed?
CVE-2026-43178 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43178 actively exploited?
CVE-2026-43178 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43178?
CVE-2026-43178 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43178?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43178, 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-2026-43178

Explore →

Is Your Infrastructure Affected by CVE-2026-43178?

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

Start Free Scan →Browse All CVEs