LiveActive security incident?Get immediate response
CVE Record

CVE-2025-39916: mm/damon/reclaim: avoid divide-by-zero in damon_reclaim_apply_parameters()

In the Linux kernel, the following vulnerability has been resolved: mm/damon/reclaim: avoid divide-by-zero in damon_reclaim_apply_parameters() When creating a new scheme of DAMON_RECLAIM, the calculation of 'min_age_region' uses 'aggr_interval' as the divisor, which may lead to division-by-zero errors. Fix it by directly returning -EINVAL when such a case occurs.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-39916 is a Linux kernel flaw in DAMON_RECLAIM parameter handling. A zero aggregation interval could trigger a divide-by-zero condition when creating a reclaim scheme. The provided sources describe a kernel fix that rejects the invalid case instead of continuing.

Executive priority

Treat as a routine kernel reliability patch with moderate priority. Prioritize internet-facing or multi-user Linux systems only if untrusted users can influence kernel memory-management configuration. No active exploitation is evidenced in the provided sources.

Technical view

The issue is in mm/damon/reclaim, specifically damon_reclaim_apply_parameters(). The min_age_region calculation used aggr_interval as a divisor without first ensuring it was nonzero. The upstream stable fixes return -EINVAL for that invalid parameter state.

Likely exposure

Exposure is most likely on systems running affected Linux kernel versions listed in the CVE data and using or allowing configuration of DAMON_RECLAIM. Systems without the affected kernel code path enabled or exercised are less likely exposed.

Exploitation context

The provided bundle does not show active exploitation, public exploit details, or KEV listing. The practical impact appears to be local reliability risk from invalid DAMON_RECLAIM parameters, but the sources do not fully describe attacker prerequisites.

Researcher notes

Evidence is limited to the CVE record, Linux stable commit references, and Debian LTS announcement. No CVSS, CWE, exploit status, or detailed privilege boundary is provided. Avoid assuming remote exploitability or a specific denial-of-service outcome beyond the divide-by-zero condition.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Apply distribution kernel updates, including Debian LTS guidance where applicable.
  • Review vendor advisories for exact fixed package versions.
  • Restrict DAMON_RECLAIM configuration access to trusted administrators.
  • Avoid deploying kernels listed as affected until patched.

Validation and detection

  • Inventory Linux kernel versions across affected hosts.
  • Check whether DAMON_RECLAIM is enabled or configured.
  • Confirm installed kernels include one of the referenced stable fixes.
  • Review distribution security advisories for package-level remediation status.
  • Validate that kernel update testing includes DAMON_RECLAIM workloads.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-39916 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf5a79d7c0c87c8d88bb5e3f3c898258fdf1b3b05, f5a79d7c0c87c8d88bb5e3f3c898258fdf1b3b05, f5a79d7c0c87c8d88bb5e3f3c898258fdf1b3b05, f5a79d7c0c87c8d88bb5e3f3c898258fdf1b3b05, f5a79d7c0c87c8d88bb5e3f3c898258fdf1b3b05, fd3e613a912bbb344ee18579cc2ad3329aacba41, 6.0.12unaffected
LinuxLinux6.1, 0, 6.1.153, 6.6.107, 6.12.48, 6.16.8, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.