Skip to main content
VulnerabilityPublished Updated

CVE-2026-31653: Linux kernel · mm/damon/sysfs: dealloc repeat_call_control if damon_call() fails

Affects Linux kernelSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 12 Nov 2026, 03:19 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

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 applied to the Linux kernel to deallocate repeat_call_control upon damon_call() failure. Users should update to a Linux kernel version that includes this fix once available. No other mitigation is indicated.

Description

A memory leak vulnerability in the Linux kernel's mm/damon/sysfs component occurs when damon_call() fails to deallocate repeat_call_control. This can happen if the monitoring daemon (kdamond) stops before damon_call() is invoked, such as when monitoring virtual address processes that terminate immediately. The issue has been fixed by ensuring repeat_call_control is deallocated upon damon_call() failure.

References

Community reviews

Loading reviews…