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-2026-98825rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe()

Description

In the Linux kernel, the following vulnerability has been resolved: rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe() devm_clk_get(&pdev->dev, "rtcref")'s return value was passed straight into clk_get_rate() without checking it for an error first, unlike the "rtc" clock a few lines above which is correctly checked with IS_ERR(). clk_get_rate() only guards against a NULL clk, not an error pointer: if (!clk) return 0; ... rate = clk_core_get_rate_recalc(clk->core); so if devm_clk_get() ever returns an error pointer here (for example ERR_PTR(-EPROBE_DEFER), which is the normal, expected outcome if the clkcfg clock-provider this RTC depends on has not registered its clocks yet by the time this driver probes), clk_get_rate() dereferences that error pointer instead of returning 0, crashing instead of letting probe defer. Capture the clock in the existing 'clk' local and check it with IS_ERR() before calling clk_get_rate(), matching the handling already used for the "rtc" clock in this same function.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 12 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (19 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 0b31d703598dc1993867597bbd45e87d824fc427 – < 7f59e824a4403e156cf930fe556b75139452099e
    • affected 0b31d703598dc1993867597bbd45e87d824fc427 – < ab741d1b714b4acc605f3d14cdc4120f87341ed1
    • affected 0b31d703598dc1993867597bbd45e87d824fc427 – < 74dc7c52946e3d47c40edd0875adb7cc15937066
    • affected 0b31d703598dc1993867597bbd45e87d824fc427 – < cfd70c9b19846c524f2b6195a7484bdf22071ccf
    • affected 0b31d703598dc1993867597bbd45e87d824fc427 – < 8a03f8422fa08eed335c51bccb612a3d81739ff2
    • affected 0b31d703598dc1993867597bbd45e87d824fc427 – < ac41b05d15db3134e839148290d67415ee0bdb58
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.56 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .