CVE-2026-46268

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: 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:

PCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition

Commit b7e282378773 has already changed the initial page refcount of p2pdma page from one to zero, however, in p2pmem_alloc_mmap() it uses "VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))" to assert the initial page refcount should not be zero and the following will be reported when CONFIG_DEBUG_VM is enabled:

page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x380400000 flags: 0x20000000002000(reserved|node=0|zone=4) raw: 0020000000002000 ff1100015e3ab440 0000000000000000 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: VM_WARN_ON_ONCE_PAGE(!page_ref_count(page)) ------------[ cut here ]------------ WARNING: CPU: 5 PID: 449 at drivers/pci/p2pdma.c:240 p2pmem_alloc_mmap+0x83a/0xa60

Fix by using "page_ref_count(page)" as the assertion condition.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
1.7%
KEV
Not listed

Published

June 3, 2026

Last Modified

June 9, 2026

Advisory Details (3)

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

PCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition - kernel/git/stable/linux.git - Linux kernel stable tree

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

PCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition - kernel/git/stable/linux.git - Linux kernel stable tree

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

PCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9b69243983fb2f4d4d1f4ef0989bc1296547dc2c

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

Frequently asked(5)

What is CVE-2026-46268?
CVE-2026-46268 is a medium vulnerability published on June 3, 2026. In the Linux kernel, the following vulnerability has been resolved: PCI/P2PDMA: Fix p2pmemallocmmap() warning condition Commit b7e282378773 has already changed the initial page refcount of p2pdma page from one to zero, however, in p2pmemallocmmap() it uses "VMWARNONONCEPAGE(!pagerefcount(page))" to…
When was CVE-2026-46268 disclosed?
CVE-2026-46268 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on June 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46268 actively exploited?
CVE-2026-46268 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46268?
CVE-2026-46268 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46268?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46268, 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-46268

Explore →

Is Your Infrastructure Affected by CVE-2026-46268?

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