Menu

Star on GitHub · 3.2k

CVE-2025-39877

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs: fix use-after-free in state_show() state_show() reads kdamond->damon_ctx without holding damon_sysfs_lock.

Published Sep 23, 2025CWE-416EPSS 0.15%

Overview

CVE-2025-39877 is a high-severity vulnerability. It was published on September 23, 2025 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/sysfs: fix use-after-free in state_show()

state_show() reads kdamond->damon_ctx without holding damon_sysfs_lock.

This allows a use-after-free race:

CPU 0 CPU 1

----- -----

state_show() damon_sysfs_turn_damon_on()

ctx = kdamond->damon_ctx; mutex_lock(&damon_sysfs_lock);

damon_destroy_ctx(kdamond->damon_ctx);

kdamond->damon_ctx = NULL;

mutex_unlock(&damon_sysfs_lock);

damon_is_running(ctx); /* ctx is freed */

mutex_lock(&ctx->kdamond_lock); /* UAF */

(The race can also occur with damon_sysfs_kdamonds_rm_dirs() and

damon_sysfs_kdamond_release(), which free or replace the context under

damon_sysfs_lock.)

Fix by taking damon_sysfs_lock before dereferencing the context, mirroring

the locking used in pid_show().

The bug has existed since state_sh

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-2025-39877?

CVE-2025-39877 is a high-severity vulnerability. It was published on September 23, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2025-39877?

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-2025-39877?

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-2025-39877?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-39877 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 2025

View all