Skip to main content

Linux Kernel EUVDEUVD-2026-25546

| CVE-2026-31653 MEDIUM
2026-04-24 Linux GHSA-pqj5-xfrj-pv58
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.5 MEDIUM

Local access and low privileges required to write DAMON sysfs; no confidentiality or integrity impact; availability high via kernel memory exhaustion.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

6
Analysis Generated
Jul 24, 2026 - 02:46 vuln.today
CVSS changed
Apr 27, 2026 - 20:22 NVD
5.5 (MEDIUM)
Patch released
Apr 27, 2026 - 20:16 nvd
Patch available
Patch available
Apr 24, 2026 - 16:16 EUVD
EUVD ID Assigned
Apr 24, 2026 - 15:00 euvd
EUVD-2026-25546
CVE Published
Apr 24, 2026 - 14:45 nvd
MEDIUM 5.5

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

mm/damon/sysfs: dealloc repeat_call_control if damon_call() fails

damon_call() for repeat_call_control of DAMON_SYSFS could fail if somehow the kdamond is stopped before the damon_call(). It could happen, for example, when te damon context was made for monitroing of a virtual address processes, and the process is terminated immediately, before the damon_call() invocation. In the case, the dyanmically allocated repeat_call_control is not deallocated and leaked.

Fix the leak by deallocating the repeat_call_control under the damon_call() failure.

This issue is discovered by sashiko [1].

AnalysisAI

Memory leak in the Linux kernel's DAMON (Data Access MONitor) sysfs subsystem allows a local low-privileged user to exhaust kernel memory by triggering a race condition between process termination and damon_call() invocation. When DAMON is configured to monitor virtual address spaces and the target process exits before damon_call() executes, the dynamically allocated repeat_call_control structure is never freed. No public exploit exists and EPSS is 0.02% (4th percentile), placing this firmly in the low-urgency tier despite the high availability impact scored by CVSS.

Technical ContextAI

DAMON is a Linux kernel framework (mm/damon/) for monitoring data access patterns, used for memory management optimization. The sysfs interface (/sys/kernel/mm/damon/) allows userspace to configure and control DAMON contexts and kdamond threads. The vulnerability lies in the repeat_call_control code path: when DAMON is configured for virtual address space (vaddr) monitoring and the target process terminates, the kdamond thread may stop before damon_call() is invoked. In this case, damon_call() returns a failure, but the heap-allocated repeat_call_control structure is not freed, resulting in a CWE-401-class memory leak (Missing Release of Memory After Effective Lifetime). The affected CPE is cpe:2.3:a:linux:linux across multiple stable branches introduced at commit 04a06b139ec08aa63d7377f6d3e5218f8ddb1c5d. Tags reference Red Hat and SUSE, indicating downstream distribution exposure.

RemediationAI

The primary fix is to upgrade to a patched kernel version: Linux 6.18.23, Linux 6.19.13, or Linux 7.0 (mainline). The upstream fix deallocates repeat_call_control when damon_call() returns a failure, closing the leak. Patches are available directly from kernel.org stable trees at the commit references above. For Red Hat and SUSE environments, monitor vendor security advisories for backported errata. If immediate upgrade is not feasible, the most effective compensating control is to restrict access to the DAMON sysfs interface by limiting permissions on /sys/kernel/mm/damon/ to privileged users only, or by unloading the damon_sysfs kernel module if DAMON is not operationally required - note that unloading may impact memory pressure management tooling that relies on DAMON. Disabling vaddr monitoring contexts specifically (while leaving DAMON otherwise functional) would also prevent the vulnerable code path from being reached. There are no significant side effects to restricting sysfs access if DAMON is not actively used.

Vendor StatusVendor

SUSE

Severity: Medium
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

Share

EUVD-2026-25546 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy