Skip to main content
VulnerabilityPublished Updated

CVE-2026-64131: Linux kernel · mm/memory: fix spurious warning when unmapping device-private/exclusive pages

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in e81446b559db4c98a6c2c5e039ac9cb23658432e : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:03 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in e81446b559db4c98a6c2c5e039ac9cb23658432e, e7af1b15c884ed12bb69da11aec095045d861ee8, be3f38d05cc5a7c3f13e51994c5dd043ab604d28 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 999dad824c39ed14dee7c4412aae531ba9e74a90, < e81446b559db4c98a6c2c5e039ac9cb23658432e
Fixed in
  • e81446b559db4c98a6c2c5e039ac9cb23658432e
LinuxLinuxAffected
  • ≥ 999dad824c39ed14dee7c4412aae531ba9e74a90, < e7af1b15c884ed12bb69da11aec095045d861ee8
Fixed in
  • e7af1b15c884ed12bb69da11aec095045d861ee8
LinuxLinuxAffected
  • ≥ 999dad824c39ed14dee7c4412aae531ba9e74a90, < be3f38d05cc5a7c3f13e51994c5dd043ab604d28
Fixed in
  • be3f38d05cc5a7c3f13e51994c5dd043ab604d28
LinuxLinuxAffected
  • ≥ 999dad824c39ed14dee7c4412aae531ba9e74a90, < a825691b804b35141aaf4eac91003a70846e316d
Fixed in
  • a825691b804b35141aaf4eac91003a70846e316d
LinuxLinuxAffected
  • ≥ 999dad824c39ed14dee7c4412aae531ba9e74a90, < 52f72b3f8f6fa64abb71b711962b97f1f6aced1c
Fixed in
  • 52f72b3f8f6fa64abb71b711962b97f1f6aced1c
LinuxLinuxAffected
  • ≥ 999dad824c39ed14dee7c4412aae531ba9e74a90, < 2fff0cdd942261497fb8922a194b4da3315ae864
Fixed in
  • 2fff0cdd942261497fb8922a194b4da3315ae864

AI-suggested

A fix for this issue has been implemented in the Linux kernel as indicated by the fixed commit versions. Users should update to a Linux kernel version that includes these fixes to eliminate the spurious warnings. No additional mitigation actions are required.

Description

A Linux kernel vulnerability caused spurious warnings during unmapping of device-private or exclusive pages due to incorrect assumptions about anonymous memory mappings. The issue arises because the unmap path incorrectly uses vma_is_anonymous() to test conditions that should be tested with folio_test_anon(), leading to warnings during process teardown. This has been fixed in specific Linux kernel commits.

References

Community reviews

Loading reviews…