How to Fix CVE-2026-31653: mm/damon/sysfs: dealloc repeat_call_control if damon_call() fails in Linux

By Sai Kiran Pandrala

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2026-23176: Critical Vulnerability in Linux — Critical Vulnerability in Linux
• How to Fix CVE-2026-23167: Critical Vulnerability in Linux — Critical Vulnerability in Linux
• How to Fix CVE-2026-31527: driver core: platform: use generic driver_override infrastructure in Linux , driver core: platform: use generic driver_override infrastructure in Linux
• How to Fix CVE-2026-43296: Security Vulnerability in Linux , Security Vulnerability in Linux
• How to Fix CVE-2026-43189: Security Vulnerability in Linux , Security Vulnerability in Linux

Last verified: 2026-05-25

CVE-2026-31653 is a mm/damon/sysfs: dealloc repeat_call_control if damon_call() fails in Linux Linux. Fix it by upgrading to 6.18.23, 6.19.13, 7.0.

What is CVE-2026-31653?

CVE-2026-31653 is a mm/damon/sysfs: dealloc repeat_call_control if damon_call() fails flaw in Linux Linux. The vendor has not published a verified CVSS metric at the time of writing. It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

From the source record: 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].

Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of Linux matches a version listed in the Affected row above.

# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux

How to fix CVE-2026-31653

Apply the vendor patch. Target the build named in the Fixed in row above (6.18.23, 6.19.13, 7.0). The runnable command set below covers the most common deployment patterns for Linux.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade linux
dpkg -s linux | grep Version

RHEL / CentOS / Rocky

sudo dnf upgrade linux -y
rpm -q linux

After applying the patch

1. Restart the service or device so the patched binary loads.
2. Confirm the running version matches the Fixed in row using the verification command below.
3. Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict network exposure

Block public access to the affected service at the perimeter. Allow only trusted source IPs.

# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4

# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
  -RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny"  -Direction Inbound -Action Block `
  -Protocol TCP -LocalPort 443

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux

Expected: a version at or above 6.18.23, 6.19.13, 7.0.

Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Is CVE-2026-31653 being exploited in the wild?

As of 2026-05-25, CVE-2026-31653 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.

What is the CVSS score for CVE-2026-31653?

A verified CVSS score is not listed in the public record for CVE-2026-31653. Check the vendor advisory and the NVD page for an updated metric.

What version fixes this?

Upgrade to 6.18.23, 6.19.13, 7.0.

Will a WAF or IDS rule alone close this?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

References

• Official vendor advisory: https://git.kernel.org/stable/c/b9dadf026a9fb681ed32a0646adc10ab485bf3b1
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-31653
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Additional reference: https://git.kernel.org/stable/c/0655f5cf1735508394ef8af98ddcfab3ac1c1cc5
• Additional reference: https://git.kernel.org/stable/c/0199390a6b92fc21860e1b858abf525c7e73b956

*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*