CVE-2026-46013

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

mm/memfd_luo: fix physical address conversion in put_folios cleanup

In memfd_luo_retrieve_folios()'s put_folios cleanup path:

  • kho_restore_folio() expects a phys_addr_t (physical address) but
receives a raw PFN (pfolio->pfn). This causes kho_restore_page() to check the wrong physical address (pfn << PAGE_SHIFT instead of the actual physical address).
  • This loop lacks the !pfolio->pfn check that exists in the main
retrieval loop and memfd_luo_discard_folios(), which could incorrectly process sparse file holes where pfn=0.

Fix by converting PFN to physical address with PFN_PHYS() and adding the !pfolio->pfn check, matching the pattern used elsewhere in this file.

This issue was identified by the AI review. https://sashiko.dev/#/patchset/[email protected]

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (2)

Auto-updated Jun 16, 2026
No patch confirmed yet.
generic

mm/memfd_luo: fix physical address conversion in put_folios cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/memfd_luo: fix physical address conversion in put_folios cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3538f90ab89aaf302782b4b073a0aae66904cd67

Vendor Advisories for CVE-2026-46013(1)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-07-31ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-07-31ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-07-31ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-31ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-07-31ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-07-31ubuntu

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 17× in last 7d / 44× 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 115 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-46013?
CVE-2026-46013 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/memfdluo: fix physical address conversion in putfolios cleanup In memfdluoretrievefolios()'s putfolios cleanup path: 1. khorestorefolio() expects a physaddrt (physical address) but receives a raw PFN (pfolio->pfn). This causes…
When was CVE-2026-46013 disclosed?
CVE-2026-46013 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46013 actively exploited?
CVE-2026-46013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.6% of all scored CVEs.
What is the CVSS score of CVE-2026-46013?
CVE-2026-46013 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46013?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46013, 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-46013

Explore →

Is Your Infrastructure Affected by CVE-2026-46013?

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

Start Free Scan →Browse All CVEs