Skip to main content
VulnerabilityPublished Updated

CVE-2026-98825: Linux kernel · rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in cfd70c9b19846c524f2b6195a7484bdf22071ccf : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:07 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in cfd70c9b19846c524f2b6195a7484bdf22071ccf, ac41b05d15db3134e839148290d67415ee0bdb58, ab741d1b714b4acc605f3d14cdc4120f87341ed1 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 0b31d703598dc1993867597bbd45e87d824fc427, < cfd70c9b19846c524f2b6195a7484bdf22071ccf
Fixed in
  • cfd70c9b19846c524f2b6195a7484bdf22071ccf
LinuxLinuxAffected
  • ≥ 0b31d703598dc1993867597bbd45e87d824fc427, < ac41b05d15db3134e839148290d67415ee0bdb58
Fixed in
  • ac41b05d15db3134e839148290d67415ee0bdb58
LinuxLinuxAffected
  • ≥ 0b31d703598dc1993867597bbd45e87d824fc427, < ab741d1b714b4acc605f3d14cdc4120f87341ed1
Fixed in
  • ab741d1b714b4acc605f3d14cdc4120f87341ed1
LinuxLinuxAffected
  • ≥ 0b31d703598dc1993867597bbd45e87d824fc427, < 74dc7c52946e3d47c40edd0875adb7cc15937066
Fixed in
  • 74dc7c52946e3d47c40edd0875adb7cc15937066
LinuxLinuxAffected
  • ≥ 0b31d703598dc1993867597bbd45e87d824fc427, < 8a03f8422fa08eed335c51bccb612a3d81739ff2
Fixed in
  • 8a03f8422fa08eed335c51bccb612a3d81739ff2
LinuxLinuxAffected
  • =6.0
Fixed in–

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.

References

Community reviews

Loading reviews…