Linux Kernel up to 7.1.7 Device Migration migrate_vma_collect_pmd uninitialized variable

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 1.02 |
Summary
A vulnerability classified as very critical was found in Linux Kernel up to 6.1.183/6.6.152/6.12.102/6.18.43/7.1.7. The impacted element is the function migrate_vma_collect_pmd of the component Device Migration. Executing a manipulation can lead to uninitialized variable.
The identification of this vulnerability is CVE-2026-80686. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability has been found in Linux Kernel up to 6.1.183/6.6.152/6.12.102/6.18.43/7.1.7 and classified as very critical. This vulnerability affects the function migrate_vma_collect_pmd of the component Device Migration. The manipulation with an unknown input leads to a uninitialized variable vulnerability. The CWE definition for the vulnerability is CWE-457. The code uses a variable that has not been initialized, leading to unpredictable or unintended results. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE pte_pfn() and pte_dirty() have undefined behaviour when called on a non-present PTE. In migrate_vma_collect_pmd(), these functions may be invoked on non-present entries (e.g., device-private entries), leading to potential crashes from pte_pfn() or incorrect dirty folio accounting from pte_dirty(). Fix both by guarding with pte_present() checks.
The advisory is available at git.kernel.org. This vulnerability was named CVE-2026-80686 since 08/26/2026. The exploitation appears to be easy. The attack can be initiated remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 08/28/2026).
Upgrading to version 6.1.184, 6.6.153, 6.12.103, 6.18.44 or 7.1.8 eliminates this vulnerability. Applying the patch 26f9ca8ed42cba25d2c75daff13561cce6019395/5b948706f11a950bc73c5304630d0a7eafc40daf/86d55447de3738620b9a8272ff167ce97e7f7203/2be94d6b20789b8865b1864dae5fe458ca85e019/42f30fa5481a1f90571ccdfbb20d2e25e47ae76e/63867c82d0c0c2d182016a32b1cc0103116b0ea5 is able to eliminate this problem.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 6.1.183
- 6.6.152
- 6.12.102
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 7.1.0
- 7.1.1
- 7.1.2
- 7.1.3
- 7.1.4
- 7.1.5
- 7.1.6
- 7.1.7
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 9.5
VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Uninitialized variableCWE: CWE-457 / CWE-453
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.1.184/6.6.153/6.12.103/6.18.44/7.1.8
Patch: 26f9ca8ed42cba25d2c75daff13561cce6019395/5b948706f11a950bc73c5304630d0a7eafc40daf/86d55447de3738620b9a8272ff167ce97e7f7203/2be94d6b20789b8865b1864dae5fe458ca85e019/42f30fa5481a1f90571ccdfbb20d2e25e47ae76e/63867c82d0c0c2d182016a32b1cc0103116b0ea5
Timeline
08/26/2026 CVE reserved08/28/2026 Advisory disclosed
08/28/2026 VulDB entry created
08/28/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-80686 (🔒)
GCVE (CVE): GCVE-0-2026-80686
GCVE (VulDB): GCVE-100-396634
Entry
Created: 08/28/2026 10:58Changes: 08/28/2026 10:58 (59)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.