LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38519: mm/damon: fix divide by zero in damon_get_intervals_score()

In the Linux kernel, the following vulnerability has been resolved: mm/damon: fix divide by zero in damon_get_intervals_score() The current implementation allows having zero size regions with no special reasons, but damon_get_intervals_score() gets crashed by divide by zero when the region size is zero. [ 29.403950] Oops: divide error: 0000 [#1] SMP NOPTI This patch fixes the bug, but does not disallow zero size regions to keep the backward compatibility since disallowing zero size regions might be a breaking change for some users. In addition, the same crash can happen when intervals_goal.access_bp is zero so this should be fixed in stable trees as well.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash a system through a divide-by-zero condition in DAMON memory-monitoring code. The public record does not provide a CVSS score, CWE, or confirmed attack path. Treat it as an availability risk until your kernel vendor maps the fix into supported package versions.

Executive priority

Track this as a kernel availability issue needing normal patch governance, not an emergency based on current evidence. Escalate priority if your vendor rates it higher, confirms reachable attack paths, or you rely on DAMON in production.

Technical view

The flaw is in damon_get_intervals_score(). A zero-size DAMON region, or intervals_goal.access_bp set to zero, can trigger a divide error and kernel Oops. The fix preserves zero-size region compatibility while handling the crash condition. Stable-tree fixes are referenced by commit URLs.

Likely exposure

Exposure is limited to Linux systems running affected kernel builds listed in the CVE data, including 6.15, 6.15.7, and 6.16. The bundle does not clarify distribution package mappings or whether DAMON must be actively configured.

Exploitation context

No active exploitation is cited, and the CVE is not marked KEV. The source describes a crash condition but does not document remote reachability, privilege requirements, or a public exploit. Impact should be assessed mainly as potential denial of service.

Researcher notes

The record is sparse: no CVSS, CWE, exploit status, or distribution mapping is provided. Analysis should focus on code lineage, whether DAMON inputs can create zero-size regions or zero access_bp, and whether local permissions constrain triggering the vulnerable path.

Mitigation direction

  • Check your Linux distribution or kernel vendor advisory for CVE-2025-38519 guidance.
  • Update to a kernel build containing the referenced stable fixes.
  • Prioritize systems where DAMON is enabled, exposed, or used operationally.
  • If updates are unavailable, ask the vendor for supported temporary risk-reduction guidance.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and container hosts.
  • Map installed package versions to vendor advisories for CVE-2025-38519.
  • Confirm whether the referenced stable commits are present in custom kernels.
  • Review kernel logs for divide errors or Oops events involving DAMON.
Prepared
Confidence
medium
Sources
4

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-38519 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
0ADP providers
3Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf04b0fedbe714f822bd066b319a60faa39a985a1, f04b0fedbe714f822bd066b319a60faa39a985a1unaffected
LinuxLinux6.15, 0, 6.15.7, 6.16affected
Weakness

CWE details

No CWE listed

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