CVE-2026-46277
Received Received - Intake

Memory Corruption in Linux Kernel mm/zone_device

Vulnerability report for CVE-2026-46277, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-08

Last updated on: 2026-06-14

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: mm/zone_device: do not touch device folio after calling ->folio_free() The contents of a device folio can immediately change after calling ->folio_free(), as the folio may be reallocated by a driver with a different order. Instead of touching the folio again to extract the pgmap, use the local stack variable when calling percpu_ref_put_many().

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-08
Last Modified
2026-06-14
Generated
2026-06-29
AI Q&A
2026-06-08
EPSS Evaluated
2026-06-27
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in the Linux kernel's memory management subsystem, specifically in the handling of device folios within the mm/zone_device component.

The issue arises because after calling the folio_free() function on a device folio, the contents of that folio can immediately change. This happens because the folio may be reallocated by a driver with a different order.

The vulnerability is due to touching or accessing the device folio after calling folio_free(), which is unsafe. The correct approach is to use a local stack variable to hold necessary information before calling percpu_ref_put_many(), avoiding accessing the folio after it might have been reallocated.

Impact Analysis

This vulnerability involves improper handling of device folios in the Linux kernel, where the contents of a device folio can change immediately after calling the folio_free() function. This can lead to potential memory corruption or unexpected behavior in kernel drivers that manage device memory, possibly causing system instability or crashes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-46277. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart