Menu

Star on GitHub · 3.2k

CVE-2026-23012

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: remove call_control in inactive contexts If damon_call() is executed against a DAMON context that is not running…

Published Jan 25, 2026CWE-416EPSS 0.17%

Overview

CVE-2026-23012 is a high-severity vulnerability. It was published on January 25, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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

mm/damon/core: remove call_control in inactive contexts

If damon_call() is executed against a DAMON context that is not running,

the function returns error while keeping the damon_call_control object

linked to the context's call_controls list. Let's suppose the object is

deallocated after the damon_call(), and yet another damon_call() is

executed against the same context. The function tries to add the new

damon_call_control object to the call_controls list, which still has the

pointer to the previous damon_call_control object, which is deallocated.

As a result, use-after-free happens.

This can actually be triggered using the DAMON sysfs interface. It is not

easily exploitable since it requires the sysfs write permission and making

a definitely weird file writes, though. Please refer to the report for

more details about the issue reproduction steps.

Fix the issue by making two changes. Firstly, move the final

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-23012?

CVE-2026-23012 is a high-severity vulnerability. It was published on January 25, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-23012?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-23012?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-23012?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-23012 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all