Live › vulnerability › CVE-2026-98825
Go to dashboardThe Linux kernel's mpfs RTC driver passed an unchecked clock pointer into clk_get_rate(), so an error return from devm_clk_get() (such as a deferred probe) could be dereferenced and crash the kernel. The fix checks the pointer with IS_ERR() before use, matching the handling of the neighbouring clock.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the MicroChip PolarFire SoC (mpfs) RTC driver, where the clkcfg clock provider may register late so the RTC probe defers. Hosts on other hardware, or kernels without this driver, are not affected.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98825")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.