Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-39909mm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters()

Description

In the Linux kernel, the following vulnerability has been resolved: mm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters() Patch series "mm/damon: avoid divide-by-zero in DAMON module's parameters application". DAMON's RECLAIM and LRU_SORT modules perform no validation on user-configured parameters during application, which may lead to division-by-zero errors. Avoid the divide-by-zero by adding validation checks when DAMON modules attempt to apply the parameters. This patch (of 2): During the calculation of 'hot_thres' and 'cold_thres', either 'sample_interval' or 'aggr_interval' is used as the divisor, which may lead to division-by-zero errors. Fix it by directly returning -EINVAL when such a case occurs. Additionally, since 'aggr_interval' is already required to be set no smaller than 'sample_interval' in damon_set_attrs(), only the case where 'sample_interval' is zero needs to be checked.

Timeline

  1. ID reserved

    By Linux

  2. · 6 months later

    Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-39909, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 40e983cca9274e177bd5b9379299b44d9536ac68 – < 74e391f7da7d9d5235a3cca88ee9fc18f720c75b
    • affected 40e983cca9274e177bd5b9379299b44d9536ac68 – < 7bb675c9f0257840d33e5d1337d7e3afdd74a6bf
    • affected 40e983cca9274e177bd5b9379299b44d9536ac68 – < af0ae62b935317bed1a1361c8c9579db9d300e70
    • affected 40e983cca9274e177bd5b9379299b44d9536ac68 – < 326a4b3750c71af3f3c52399ec4dbe33b6da4c26
    • affected 40e983cca9274e177bd5b9379299b44d9536ac68 – < 711f19dfd783ffb37ca4324388b9c4cb87e71363
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.153 – ≤ 6.1.*
    • unaffected 6.6.107 – ≤ 6.6.*
    • unaffected 6.12.48 – ≤ 6.12.*
    • unaffected 6.16.8 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-39909 badge
[![CVE-2025-39909](https://cveledger.app/badge/CVE-2025-39909.svg)](https://cveledger.app/cve/CVE-2025-39909)

Record last updated .