PatchSiren cyber security CVE debrief
CVE-2026-64130 Linux CVE debrief
A Linux kernel vulnerability, CVE-2026-64130, was resolved by decoupling __GFP_ZEROTAGS from __GFP_ZERO to fix initialization of tags of the huge zero folio with init_on_free. The vulnerability affects the Linux kernel and could potentially expose uninitialized tags. The fix ensures that tags are properly initialized for the huge zero folio. Linux kernel developers and maintainers, as well as users of Linux-based systems, should be aware of this vulnerability and its fix.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-19
- Original CVE updated
- 2026-08-13
- Advisory published
- 2026-07-19
- Advisory updated
- 2026-08-13
Who should care
Linux kernel developers and maintainers, as well as users of Linux-based systems, should be aware of this vulnerability and its fix. They should review the official advisory to determine the affected scope and severity. The vulnerability could potentially expose uninitialized tags, and defenders should verify the affected scope and severity with the official advisory.
Technical summary
The Linux kernel vulnerability, CVE-2026-64130, relates to the initialization of tags for the huge zero folio when using init_on_free. The __GFP_ZEROTAGS flag is used in conjunction with __GFP_ZERO and __GFP_SKIP_KASAN. However, when allocating with __GFP_ZEROTAG set, post_alloc_hook() skips clearing page content and tag memory. This issue affects the huge zero folio, which is mapped through a PMD marked as special, and can expose uninitialized tags. The fix decouples __GFP_ZEROTAGS from __GFP_ZERO and passes a flag to tag_clear_highpages() to clear page content.
Defensive priority
Medium
Recommended defensive actions
- Review and apply the kernel patch to decouple __GFP_ZEROTAGS from __GFP_ZERO
- Verify that the Linux kernel version used is not vulnerable
- Monitor for any potential issues related to memory tagging
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record was published on 2026-07-19T16:17:54.723Z and has not been modified since then. The NVD entry is currently Received. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the official advisory. The fix decouples __GFP_ZEROTAGS from __GFP_ZERO and passes a flag to tag_clear_highpages() to clear page content. Linux kernel developers and maintainers should review the official advisory for more information.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-64130 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-64130
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-64130 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-64130
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/2f2aec5120b93a8f8b52dc50cdc60dbb8aec72f6
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/6a288a4ddb4a994490505ab5f41c445f8e6b6467
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/738d18f1da3513d17b6f7bf30146cc4ac2480ffd
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.