CVE-2026-46318

CVSS 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

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:

Revert "mm/hugetlbfs: update hugetlbfs to use mmap_prepare"

This reverts commit ea52cb24cd3f ("mm/hugetlbfs: update hugetlbfs to use mmap_prepare") with conflict resolution to account for changes in commit ea52cb24cd3f ("mm/hugetlbfs: update hugetlbfs to use mmap_prepare").

The patch incorrectly handled hugetlb VMA lock allocation at the mmap_prepare stage, where a failed allocation occurring after mmap_prepare is called might result in the lock leaking.

There is no risk of a merge causing a similar issues, as VMA_DONTEXPAND_BIT is set for hugetlb mappings.

As a first step in addressing this issue, simply revert the change so we can rework how we do this having corrected the underlying issues.

We maintain the VMA flags changes as best we can, accounting for the fact that we were working with a VMA descriptor previously and propagating like-for-like changes for this.

Note that we invoke vma_set_flags() and do not call vma_start_write() as vm_flags_set() does. This is OK as it's being done in an .mmap hook where the VMA is not yet linked into the tree so nobody else can be accessing it.

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

Published

June 9, 2026

Last Modified

June 14, 2026

References (2)

Vendor Advisories for CVE-2026-46318(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 46× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 02:30 UTCEPSS rescore
  4. 2026-07-04 14:20 UTCGHSA enrichment
  5. 2026-07-04 06:31 UTCEPSS rescore
  6. 2026-07-01 15:07 UTCEPSS rescore
  7. 2026-07-01 08:20 UTCGHSA enrichment
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-28 14:58 UTCGHSA enrichment
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-27 03:08 UTCEPSS rescore
  16. 2026-06-25 21:36 UTCGHSA enrichment
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-24 14:05 UTCEPSS rescore
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-23 21:33 UTCEPSS rescore
  21. 2026-06-23 04:14 UTCGHSA enrichment
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
Show 21 more
  1. 2026-06-21 01:59 UTCEPSS rescore
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-20 10:33 UTCGHSA enrichment
  4. 2026-06-19 19:26 UTCEPSS rescore
  5. 2026-06-19 19:26 UTCEPSS rescore
  6. 2026-06-17 17:53 UTCEPSS rescore
  7. 2026-06-17 17:08 UTCGHSA enrichment
  8. 2026-06-16 17:52 UTCEPSS rescore
  9. 2026-06-15 17:49 UTCEPSS rescore
  10. 2026-06-14 23:33 UTCMITRE cvelistV5
  11. 2026-06-14 23:07 UTCGHSA enrichment
  12. 2026-06-13 23:00 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-06-12 05:45 UTCEG score recompute
  16. 2026-06-12 05:45 UTCGHSA enrichment
  17. 2026-06-11 14:00 UTCEPSS rescore
  18. 2026-06-10 22:18 UTCEPSS rescore
  19. 2026-06-09 13:18 UTCNVD update
  20. 2026-06-09 12:24 UTCEG score recompute
  21. 2026-06-09 12:23 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-46318?
CVE-2026-46318 is a publicly disclosed vulnerability published on June 9, 2026. In the Linux kernel, the following vulnerability has been resolved: Revert "mm/hugetlbfs: update hugetlbfs to use mmap_prepare" This reverts commit ea52cb24cd3f ("mm/hugetlbfs: update hugetlbfs to use mmap_prepare") with conflict resolution to account for changes in commit ea52cb24cd3f…
When was CVE-2026-46318 disclosed?
CVE-2026-46318 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46318 actively exploited?
CVE-2026-46318 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2026-46318?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46318, 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-46318

Explore →

Is Your Infrastructure Affected by CVE-2026-46318?

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

Start Free Scan →Browse All CVEs