Live › vulnerability › CVE-2026-98505
Go to dashboardIn the Linux kernel's DAMON memory monitor, clearing the accessed bit on hugetlb pages could overwrite hardware-set dirty bits during a race. The sources describe this as a data-integrity bug with no confirmed security impact.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only systems running a Linux kernel with DAMON enabled and monitoring hugetlb-backed memory are exposed. The sources do not say which kernel versions are affected or whether the default configuration enables DAMON. Systems that do not use DAMON can skip it.
No product ranges from the sources yet.
uname -r to see the running kernel versionEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
mm/damon/vaddr: avoid hw-driven pte updates during damon_hugetlb_mkold()
damon_hugetlb_mkold() reads the page table entry into a local variable, unsets the accessed bit in the variable, and updates the page table entry with the updated variable value. If hardware updates the same page table entry in parallel, the hw updates could be lost. For example, hardware-updated dirty bits might be lost.
Avoid the parallel updates by clearing the page table entry when reading it together, using huge_ptep_get_and_clear(). If a parallel write to the memory is made after the clearing, the hw will see the page table entry is cleared, trigger page fault and wait until it is handled. The page fault handling will wait for damon_hugetlb_mkold() due to the page table lock.
Because hugetlbfs is an in-memory file system and hugetlb pages cannot be reclaimed, no critical issue is expected to my best knowledge. But definitely this is a nasty bug that should be fixed sooner rather than later.
The issue was discovered [1] by Sashiko.
This page as .md · .json · in your agent: get_signal("CVE-2026-98505")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.