CVE-2025-38519
BaseFortify
Publication date: 2025-08-16
Last updated on: 2025-11-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-369 | The product divides a value by zero. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a divide-by-zero error in the Linux kernel's memory management subsystem (mm/damon). Specifically, the function damon_get_intervals_score() can crash when it attempts to divide by zero if it encounters a memory region of zero size or if intervals_goal.access_bp is zero. The issue arises because the current implementation allows zero size regions, which leads to this crash. The patch fixes the divide-by-zero bug without disallowing zero size regions to maintain backward compatibility.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash (kernel panic) due to a divide-by-zero error. Such crashes can lead to system instability, downtime, and potential data loss or service disruption on affected systems.
What immediate steps should I take to mitigate this vulnerability?
Apply the patch that fixes the divide by zero error in damon_get_intervals_score() in the Linux kernel. This patch prevents crashes caused by zero size regions or zero intervals_goal.access_bp values. Since the patch maintains backward compatibility by allowing zero size regions, updating to the fixed kernel version is the recommended mitigation.