CVE-2026-93193: drm/rockchip: analogix_dp: Fix OF node reference leak via auto cleanup
In the Linux kernel, the following vulnerability has been resolved:
drm/rockchip: analogixdp: Fix OF node reference leak via auto cleanup
Sashiko reported a reference leak in rockchipdpdrmencoderenable(), the ofgetchildbyname() function does not call ofnodeput() in a symmetrical way [1].
Fix the device node reference leak by using free(devicenode) to automatically manage ofnodeput() for all device nodes.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1
Event History
Frequently Asked Questions
Which systems are affected by this issue?
Systems using the Linux kernel's DRM Rockchip Analogix DisplayPort driver may be affected when rockchip_dp_drm_encoder_enable() obtains device-tree child nodes.
What is the impact of triggering the flaw?
The issue leaks device-tree node references because references returned by of_get_child_by_name() were not released symmetrically. The provided information does not describe a security impact beyond this resource leak.
How is the issue addressed?
The fix changes device-node lifetime handling to use __free(device_node), which automatically performs of_node_put() cleanup for the relevant device nodes.