CVE-2026-31652
kernel: mm/damon/stat: deallocate damon_call() failure leaking damon_ctx
Overview
Description
In the Linux kernel, the following vulnerability has been resolved:
mm/damon/stat: deallocate damon_call() failure leaking damon_ctx
damon_stat_start() always allocates the module's damon_ctx object
(damon_stat_context). Meanwhile, if damon_call() in the function fails,
the damon_ctx object is not deallocated. Hence, if the damon_call() is
failed, and the user writes Y to “enabled” again, the previously
allocated damon_ctx object is leaked.
This cannot simply be fixed by deallocating the damon_ctx object when
damon_call() fails. That's because damon_call() failure doesn't guarantee
the kdamond main function, which accesses the damon_ctx object, is
completely finished. In other words, if damon_stat_start() deallocates
the damon_ctx object after damon_call() failure, the not-yet-terminated
kdamond could access the freed memory (use-after-free).
Fix the leak while avoiding the use-after-free by keeping returning
damon_stat_start() without deallocating the damon_ctx object after
damon_call() failure, but deallocating it when the function is invoked
again and the kdamond is completely terminated. If the kdamond is not yet
terminated, simply return -EAGAIN, as the kdamond will soon be terminated.
The issue was discovered [1] by sashiko.
Source: OX vulnerability database
Severity
7.8 · HIGH
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness: CWE-416
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 2 fixes
debian 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 14 | linux | 6.19.13-1 |
ubuntu 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 26.04 | linux-nvidia | 7.0.0-1006.6 |
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2026-31652
- git.kernel.org https://git.kernel.org/linus/4c04c6b47c361612b1d70cec8f7a60b1482d1400 (7.0)
- git.kernel.org https://git.kernel.org/stable/c/16c92e9bf55fa049ddb5e894dc0623dacd46a620
- git.kernel.org https://git.kernel.org/stable/c/447f8870b484f6596d7a7130e72bd0a3f1e037bb
- git.kernel.org https://git.kernel.org/stable/c/4c04c6b47c361612b1d70cec8f7a60b1482d1400
- lore.kernel.org https://lore.kernel.org/linux-cve-announce/2026042400-CVE-2026-31652-e967@gregkh/T
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2026-31652
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2026-31652
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.