rtc: msc313: Fix function prototype mismatch in msc313_rtc_probe()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.0.176.1.36.2In the Linux kernel, the following vulnerability has been resolved:
rtc: msc313: Fix function prototype mismatch in msc313_rtc_probe()
With clang's kernel control flow integrity (kCFI, CONFIG_CFI_CLANG), indirect call targets are validated against the expected function pointer prototype to make sure the call target is valid to help mitigate ROP attacks. If they are not identical, there is a failure at run time, which manifests as either a kernel panic or thread getting killed.
msc313_rtc_probe() was passing clk_disable_unprepare() directly, which did not have matching prototypes for devm_add_action_or_reset()'s callback argument. Refactor to use devm_clk_get_enabled() instead.
This was found as a result of Clang's new -Wcast-function-type-strict flag, which is more sensitive than the simpler -Wcast-function-type, which only checks for type width mismatches.
From the CVE record · Linux
The msc313 RTC driver passes a callback with a mismatched function prototype. On kernels built with Clang kCFI enabled, invoking that callback can cause a kernel panic or kill a thread. The input does not identify an attacker path or specify network access, authentication, or user interaction requirements.
Teams running Linux kernels with the msc313 RTC driver and Clang kCFI enabled should check their builds; affected versions are not specified.