Linux Kernel up to 7.1.1 Memory Management drivers/base/memory __add_memory_block altmap memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.8$0-$5k0.80

Summaryinfo

A vulnerability labeled as very critical has been found in Linux Kernel up to 6.6.143/6.12.94/6.18.36/7.0.13/7.1.1. This issue affects the function __add_memory_block of the file drivers/base/memory of the component Memory Management. The manipulation of the argument altmap results in memory corruption. This vulnerability is known as CVE-2026-64244. Attacking locally is a requirement. No exploit is available.

Detailsinfo

A vulnerability, which was classified as very critical, was found in Linux Kernel up to 6.6.143/6.12.94/6.18.36/7.0.13/7.1.1. Affected is the function __add_memory_block of the file drivers/base/memory of the component Memory Management. The manipulation of the argument altmap with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: drivers/base/memory: set mem->altmap after successful device registration If __add_memory_block() fails at xa_store() (under memory pressure for example), device_unregister() is called, which eventually triggers memory_block_release() with mem->altmap still set, causing a WARN_ON(mem->altmap). This was triggered by modifying virtio-mem driver. Fix this by delaying the assignment of mem->altmap until after __add_memory_block() has succeeded.

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-64244 since 07/19/2026. The exploitability is told to be easy. The attack needs to be approached locally. The exploitation requires an enhanced level of successful authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 07/24/2026).

Upgrading to version 6.6.144, 6.12.95, 6.18.37, 7.0.14, 7.1.2 or 7.2-rc1 eliminates this vulnerability. Applying the patch 802e113cf120df7208e4c7e604950a85e87120a8/22dc0d042f02ce82aa61422ea5f232628bfd9e9c/6c25bf4e44a2b6a14332f952bba0974521f5b72d/bc3dd82a0ffd488bb902f4c69c3d28fd4088d973/059ac6252a63edf1cea79bf30bd860a8c264b62c/a2b8d7827f48ee54a686cb80e4a1d0ff954ec42a is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.2
VulDB Meta Temp Score: 7.8

VulDB Base Score: 8.2
VulDB Temp Score: 7.8
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.144/6.12.95/6.18.37/7.0.14/7.1.2/7.2-rc1
Patch: 802e113cf120df7208e4c7e604950a85e87120a8/22dc0d042f02ce82aa61422ea5f232628bfd9e9c/6c25bf4e44a2b6a14332f952bba0974521f5b72d/bc3dd82a0ffd488bb902f4c69c3d28fd4088d973/059ac6252a63edf1cea79bf30bd860a8c264b62c/a2b8d7827f48ee54a686cb80e4a1d0ff954ec42a

Timelineinfo

07/19/2026 CVE reserved
07/24/2026 +5 days Advisory disclosed
07/24/2026 +0 days VulDB entry created
07/24/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64244 (🔒)
GCVE (CVE): GCVE-0-2026-64244
GCVE (VulDB): GCVE-100-382980

Entryinfo

Created: 07/24/2026 19:05
Changes: 07/24/2026 19:05 (61)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!