CVE-2025-39916: mm/damon/reclaim: avoid divide-by-zero in damon_reclaim_apply_parameters()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 40cb9b38b645126fdd1d6aa3d6811a8ad50ddfa1, 5d6eeb3c683c777ed4538eb3a650bb7da17a7cff, 6.1; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1.
Low priority for now. Upgrade to Linux Linux 40cb9b38b645126fdd1d6aa3d6811a8ad50ddfa1, 5d6eeb3c683c777ed4538eb3a650bb7da17a7cff, 6.1; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 1, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-369
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- fd3e613a912bbb344ee18579cc2ad3329aacba41, 6.1affected
- f5a79d7c0c87c8d88bb5e3f3c898258fdf1b3b05 and later · before 64dc351e58271c1e9005e42f5216b4f3d7a39b66affected · git
- f5a79d7c0c87c8d88bb5e3f3c898258fdf1b3b05 and later · before 9fe0415156fbde773b31f920201cb70b1f0e40feaffected · git
- f5a79d7c0c87c8d88bb5e3f3c898258fdf1b3b05 and later · before 5d6eeb3c683c777ed4538eb3a650bb7da17a7cffaffected · git
- f5a79d7c0c87c8d88bb5e3f3c898258fdf1b3b05 and later · before 40cb9b38b645126fdd1d6aa3d6811a8ad50ddfa1affected · git
- f5a79d7c0c87c8d88bb5e3f3c898258fdf1b3b05 and later · before e6b543ca9806d7bced863f43020e016ee996c057affected · git
- 6.0.12 and later · before 6.1affected · semver
- before 6.1not affected · semver
- 6.1.153 and later · up to and including 6.1.*not affected · semver
- 6.6.107 and later · up to and including 6.6.*not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel6.0.12 and later · before 6.1.153
- linux linux kernel6.2 and later · before 6.6.107
- linux linux kernel6.7 and later · before 6.12.48
- linux linux kernel6.13 and later · before 6.16.8
- linux linux kernel6.17
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.153-1 | 6.1.153-1 |
| Debian:13 | linux | before 6.12.48-1 | 6.12.48-1 |
| Debian:14 | linux | before 6.16.8-1 | 6.16.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-39914Oct 1, 2025 · tracing: Silence warning when chunk allocation fails in trace_pid_write22Monitor
- ← EarlierCVE-2025-39915Oct 1, 2025 · net: phy: transfer phy_config_inband() locking responsibility to phylink22Monitor
- Later →CVE-2022-50431Oct 1, 2025 · ALSA: aoa: i2sbus: fix possible memory leak in i2sbus_add_dev()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 40cb9b38b645126fdd1d6aa3d6811a8ad50ddfa1 | Vendor (CNA) |
| Linux Linux | 5d6eeb3c683c777ed4538eb3a650bb7da17a7cff | Vendor (CNA) |
| Linux Linux | 6.1 | Vendor (CNA) |
| Linux Linux | 64dc351e58271c1e9005e42f5216b4f3d7a39b66 | Vendor (CNA) |
| Linux Linux | 9fe0415156fbde773b31f920201cb70b1f0e40fe | Vendor (CNA) |
| Linux Linux | e6b543ca9806d7bced863f43020e016ee996c057 | Vendor (CNA) |
| azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 | 6.6.112.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.153-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-26945518 days apartcrypto: iaa - Fix nr_cpus < nr_iaa case33Monitor
- CVE-2025-399090 days apartmm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters()22Monitor
- CVE-2025-399548 days apartclk: sunxi-ng: mp: Fix dual-divider clock rate readback22Monitor
- CVE-2025-3974220 days apartRDMA: hfi1: fix possible divide-by-zero in find_hw_thread_mask()22Monitor
- CVE-2025-3871927 days apartnet: hibmcge: fix the division by zero issue22Monitor
- CVE-2025-3851946 days apartmm/damon: fix divide by zero in damon_get_intervals_score()22Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-369 · Divide By ZeroCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/5d6eeb3c683c777ed4538eb3a650bb7da17a7cff
- git.kernel.org/stable/c/64dc351e58271c1e9005e42f5216b4f3d7a39b66
- git.kernel.org/stable/c/9fe0415156fbde773b31f920201cb70b1f0e40fe
- git.kernel.org/stable/c/e6b543ca9806d7bced863f43020e016ee996c057
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.