In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: fix initialization of tags of the huge zero folio with… (CVE-2026-64130)
A vulnerability in the Linux kernel's memory management subsystem related to the initialization of tags in huge zero folios has been resolved. The issue involves improper clearing of memory tags when allocating huge zero folios with certain flags enabled, potentially exposing stale tag data. This affects the behavior of memory tagging on ARM64 architectures when init_on_free is enabled. The fix decouples tag clearing from zeroing page content to ensure tags are properly cleared.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-64130) in the Linux kernel concerns the improper initialization of memory tags for huge zero folios when allocated with the __GFP_ZEROTAGS flag alongside init_on_free. Normally, pages are zeroed on free to optimize allocation, and tags are cleared when mapped to user space. However, huge zero folios mapped through a special PMD do not trigger tag initialization, leaving stale tags exposed. The fix involves separating the clearing of tags from page content zeroing and adjusting the tag_clear_highpages() function semantics to ensure proper tag clearing regardless of page content zeroing. This issue was reproduced and tested on ARM64 with memory tagging extension self-tests.
Potential Impact
The vulnerability could lead to exposure of stale memory tags in huge zero folios, which may affect memory tagging integrity on ARM64 systems using init_on_free. This could potentially undermine the security guarantees provided by memory tagging extensions by exposing residual tag data. However, no known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by properly clearing tags on huge zero folios. Users should update to the fixed kernel version once available. Since this is a kernel-level fix, applying the official kernel update is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the exact fixed versions and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: fix initialization of tags of the huge zero folio with… (CVE-2026-64130)
Description
A vulnerability in the Linux kernel's memory management subsystem related to the initialization of tags in huge zero folios has been resolved. The issue involves improper clearing of memory tags when allocating huge zero folios with certain flags enabled, potentially exposing stale tag data. This affects the behavior of memory tagging on ARM64 architectures when init_on_free is enabled. The fix decouples tag clearing from zeroing page content to ensure tags are properly cleared.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-64130) in the Linux kernel concerns the improper initialization of memory tags for huge zero folios when allocated with the __GFP_ZEROTAGS flag alongside init_on_free. Normally, pages are zeroed on free to optimize allocation, and tags are cleared when mapped to user space. However, huge zero folios mapped through a special PMD do not trigger tag initialization, leaving stale tags exposed. The fix involves separating the clearing of tags from page content zeroing and adjusting the tag_clear_highpages() function semantics to ensure proper tag clearing regardless of page content zeroing. This issue was reproduced and tested on ARM64 with memory tagging extension self-tests.
Potential Impact
The vulnerability could lead to exposure of stale memory tags in huge zero folios, which may affect memory tagging integrity on ARM64 systems using init_on_free. This could potentially undermine the security guarantees provided by memory tagging extensions by exposing residual tag data. However, no known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by properly clearing tags on huge zero folios. Users should update to the fixed kernel version once available. Since this is a kernel-level fix, applying the official kernel update is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the exact fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-jjh5-mvrv-5xmg
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64130"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a82a4a8d598912aed6
Added to database: 07/19/2026, 19:38:16 UTC
Last enriched: 07/19/2026, 19:44:55 UTC
Last updated: 07/20/2026, 12:37:44 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.