CVE-2026-98746

What it actually does

Failure to call clk_put() after of_clk_get() in the ma35d1 serial driver probe function leaks clock references on error paths and module removal, gradually exhausting kernel clock resources.

Why it matters to the business

Repeated loading or error conditions on affected serial hardware can exhaust system resources, leading to degraded performance or eventual denial of service for serial-dependent operations; low immediate urgency given no known exploitation.

How an attack unfolds

An attacker with local access or the ability to trigger repeated probe/remove cycles on the ma35d1 serial device can cause resource leaks; no public exploits or threat actor campaigns are associated with this issue.

How to fix it

Update to a Linux kernel containing the referenced fix that adds clk_put() calls on all probe error paths and in ma35d1serial_remove(); rebuild and deploy the updated kernel image.

How to confirm the fix worked

Inspect the ma35d1 serial driver source for clk_put() paired with of_clk_get() on error paths and remove; confirm the updated driver is loaded via kernel module or dmesg output after reboot.

Typical attack path

1. Gain local access or control over hardware events that trigger ma35d1 serial probe
2. Force repeated successful or failed probe/remove operations on the device
3. Accumulate unreleased clock references until kernel resource limits are reached
4. Observe system degradation affecting serial or dependent subsystems

How to detect it

Review kernel logs for repeated ma35d1 probe/remove messages and monitor clock reference counts via kernel debug interfaces; no specific post-exploitation artifacts are known.

What your security team should do

• Prioritize kernel upgrade on systems using the ma35d1 serial driver within standard patching windows
• Monitor for upstream backports to supported distribution kernels
• Review device probe logs for repeated ma35d1 errors that could accelerate resource exhaustion