Answer in brief
CVE-2026-46115 records a Critical severity (CVSS 9.8) vulnerability in block: add pgmap check to biovec_phys_mergeable. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=49580e690755d0e51ed7aa2c33225dd884fa738a <3d2ecbd444b01d6500671d1a582b7393943cf539 || >=49580e690755d0e51ed7aa2c33225dd884fa738a <a7f3aa8c9df3905fe820ae36b67ba56b81587574 || >=49580e690755d0e51ed7aa2c33225dd884fa738a <f17d521075325b8afc42d1baa1c28a5e9aca111f || >=49580e690755d0e51ed7aa2c33225dd884fa738a <f632dab4b841554cd6416058c61886d7db176581 || >=49580e690755d0e51ed7aa2c33225dd884fa738a <13920e4b7b784b40cf4519ff1f0f3e513476a499 | 3d2ecbd444b01d6500671d1a582b7393943cf539, a7f3aa8c9df3905fe820ae36b67ba56b81587574, f17d521075325b8afc42d1baa1c28a5e9aca111f, f632dab4b841554cd6416058c61886d7db176581, 13920e4b7b784b40cf4519ff1f0f3e513476a499 |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-46115 records a Critical severity (CVSS 9.8) vulnerability in block: add pgmap check to biovec_phys_mergeable. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=49580e690755d0e51ed7aa2c33225dd884fa738a <3d2ecbd444b01d6500671d1a582b7393943cf539 || >=49580e690755d0e51ed7aa2c33225dd884fa738a <a7f3aa8c9df3905fe820ae36b67ba56b81587574 || >=49580e690755d0e51ed7aa2c33225dd884fa738a <f17d521075325b8afc42d1baa1c28a5e9aca111f || >=49580e690755d0e51ed7aa2c33225dd884fa738a <f632dab4b841554cd6416058c61886d7db176581 || >=49580e690755d0e51ed7aa2c33225dd884fa738a <13920e4b7b784b40cf4519ff1f0f3e513476a499 | 3d2ecbd444b01d6500671d1a582b7393943cf539, a7f3aa8c9df3905fe820ae36b67ba56b81587574, f17d521075325b8afc42d1baa1c28a5e9aca111f, f632dab4b841554cd6416058c61886d7db176581, 13920e4b7b784b40cf4519ff1f0f3e513476a499 |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.