CVE-2026-46115

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-28. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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

block: add pgmap check to biovec_phys_mergeable

biovec_phys_mergeable() is used by the request merge, DMA mapping, and integrity merge paths to decide if two physically contiguous bvec segments can be coalesced into one. It currently has no check for whether the segments belong to different dev_pagemaps.

When zone device memory is registered in multiple chunks, each chunk gets its own dev_pagemap. A single bio can legitimately contain bvecs from different pgmaps -- iov_iter_extract_bvecs() breaks at pgmap boundaries but the outer loop in bio_iov_iter_get_pages() continues filling the same bio. If such bvecs are physically contiguous, biovec_phys_mergeable() will coalesce them, making it impossible to recover the correct pgmap for the merged segment via page_pgmap().

Add a zone_device_pages_have_same_pgmap() check to prevent merging bvec segments that span different pgmaps.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
38.9%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 24, 2026

Advisory Details (5)

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

block: add pgmap check to biovec_phys_mergeable - kernel/git/stable/linux.git - Linux kernel stable tree

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

block: add pgmap check to biovec_phys_mergeable - kernel/git/stable/linux.git - Linux kernel stable tree

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

block: add pgmap check to biovec_phys_mergeable - kernel/git/stable/linux.git - Linux kernel stable tree

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

block: add pgmap check to biovec_phys_mergeable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d2ecbd444b01d6500671d1a582b7393943cf539
generic

block: add pgmap check to biovec_phys_mergeable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13920e4b7b784b40cf4519ff1f0f3e513476a499

Vendor Advisories for CVE-2026-46115(2)

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

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-07-16ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-07-16ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-07-16ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-07-16ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1026.26) @ noble2026-07-16ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-07-16ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-07-16ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-07-16ubuntu
ubuntulinux-virtual-hwe-24.04 (6.17.0-40.40~24.04.1) @ noble2026-07-16ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1021.21) @ questing2026-07-16ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-07-16ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-07-16ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-40.40) @ questing2026-07-16ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1028.28) @ noble2026-07-16ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-07-16ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-16ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-07-16ubuntu

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.

Additional Vendor Advisories

(18)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-46115?
CVE-2026-46115 is a critical vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: block: add pgmap check to biovecphysmergeable biovecphysmergeable() is used by the request merge, DMA mapping, and integrity merge paths to decide if two physically contiguous bvec segments can be coalesced into one. It currently…
When was CVE-2026-46115 disclosed?
CVE-2026-46115 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46115 actively exploited?
CVE-2026-46115 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 38.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46115?
CVE-2026-46115 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-46115?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46115, 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-46115

Explore →

Is Your Infrastructure Affected by CVE-2026-46115?

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

Start Free Scan →Browse All CVEs