CVE-2023-52661

What it actually does

Missing clk_put() after failed clk_get_sys(..., "pll_d2_out0") in tegra_dc_rgb_probe error paths, leaving clock references allocated.

Why it matters to the business

Resource leaks in Tegra display drivers on Linux systems may cause gradual driver instability or exhaustion on affected devices; low exploitation likelihood but widespread kernel exposure increases patch urgency.

How an attack unfolds

An attacker triggers the specific error condition during probe of the RGB display controller; the absent clk_put leaves a dangling clock reference that can be abused for later resource manipulation or denial of service in the kernel.

How to fix it

Update the Linux kernel to commit 5c8dc26e31b8b410ad1895e0d314def50c76eed0 or later; apply the corresponding stable branch fixes that add the clk_put call and put_pll_d_out0 error label.

How to confirm the fix worked

Inspect the tegra_dc_rgb_probe function in drm/tegra/rgb.c for the clk_put after the clk_get_sys failure and confirm the new put_pll_d_out0 label exists in error handling.

Typical attack path

1. Reach tegra_dc_rgb_probe via device initialization or module load
2. Force clk_get_sys failure for pll_d2_out0
3. Bypass the missing clk_put in the error exit path
4. Retain leaked clock reference for subsequent kernel memory or resource abuse

How to detect it

Search kernel logs and dmesg for tegra_dc_rgb_probe error paths; examine source history around the probe function for the missing clk_put; no public exploitation artifacts reported.

What your security team should do

• Prioritize kernel package updates on all Tegra-based systems
• Reboot affected hosts after applying the fixed kernel
• Audit custom or downstream kernel trees for the same missing clk_put pattern