Answer in brief
CVE-2026-98825 records a Unknown severity vulnerability in rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0b31d703598dc1993867597bbd45e87d824fc427 <74dc7c52946e3d47c40edd0875adb7cc15937066 || >=0b31d703598dc1993867597bbd45e87d824fc427 <cfd70c9b19846c524f2b6195a7484bdf22071ccf || >=0b31d703598dc1993867597bbd45e87d824fc427 <8a03f8422fa08eed335c51bccb612a3d81739ff2 || >=0b31d703598dc1993867597bbd45e87d824fc427 <ac41b05d15db3134e839148290d67415ee0bdb58 | 74dc7c52946e3d47c40edd0875adb7cc15937066, cfd70c9b19846c524f2b6195a7484bdf22071ccf, 8a03f8422fa08eed335c51bccb612a3d81739ff2, ac41b05d15db3134e839148290d67415ee0bdb58 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.