CVE-2026-46115block: add pgmap check to biovec_phys_mergeable
- 9.8CriticalCVSS base score
- 0.49%Exploitation in 30 daysEPSS · top 57% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 15 days later
· 15 days later
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Undergoing Analysis | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.49% · top 57% of all CVEs (13 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected 49580e690755d0e51ed7aa2c33225dd884fa738a – < 3d2ecbd444b01d6500671d1a582b7393943cf539
- affected 49580e690755d0e51ed7aa2c33225dd884fa738a – < a7f3aa8c9df3905fe820ae36b67ba56b81587574
- affected 49580e690755d0e51ed7aa2c33225dd884fa738a – < f17d521075325b8afc42d1baa1c28a5e9aca111f
- affected 49580e690755d0e51ed7aa2c33225dd884fa738a – < f632dab4b841554cd6416058c61886d7db176581
- affected 49580e690755d0e51ed7aa2c33225dd884fa738a – < 13920e4b7b784b40cf4519ff1f0f3e513476a499
- affected 6.2
- unaffected < 6.2
- unaffected 6.6.140 – ≤ 6.6.*
- unaffected 6.12.88 – ≤ 6.12.*
- unaffected 6.18.30 – ≤ 6.18.*
- unaffected 7.0.7 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References5
- https://git.kernel.org/stable/c/3d2ecbd444b01d6500671d1a582b7393943cf539 (opens in a new tab)
- https://git.kernel.org/stable/c/a7f3aa8c9df3905fe820ae36b67ba56b81587574 (opens in a new tab)
- https://git.kernel.org/stable/c/f17d521075325b8afc42d1baa1c28a5e9aca111f (opens in a new tab)
- https://git.kernel.org/stable/c/f632dab4b841554cd6416058c61886d7db176581 (opens in a new tab)
- https://git.kernel.org/stable/c/13920e4b7b784b40cf4519ff1f0f3e513476a499 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-32874 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-46115)Record last updated .