Skip to main content
VulnerabilityPublished Updated

CVE-2026-31652: Linux kernel · mm/damon/stat: deallocate damon_call() failure leaking damon_ctx

Affects Linux kernelSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 12 Nov 2026, 03:19 UTC

Severity
Medium

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

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Apr 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 11 Nov 2026.

What to do

AI-suggested

A fix has been implemented in the Linux kernel to address this issue by safely managing the lifecycle of the damon_ctx object in damon_stat_start(). Users should update to the fixed kernel version once available. No other mitigation is required as the patch resolves both the leak and use-after-free risks.

Description

A memory leak vulnerability exists in the Linux kernel's mm/damon/stat component due to improper deallocation of the damon_ctx object when damon_call() fails. This leak occurs because the kernel defers deallocation to avoid use-after-free errors with the kdamond main function. The issue was fixed by modifying damon_stat_start() to handle deallocation safely, returning -EAGAIN if kdamond is still running and deallocating only once kdamond has terminated.

References

Community reviews

Loading reviews…