CVE-2026-90126

rtc: pcf8563: fix clock provider leak on unbind

N/A
Published: September 17, 2026 at 04:06 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: rtc: pcf8563: fix clock provider leak on unbind pcf8563_clkout_register_clk() registers the CLKOUT clock provider with of_clk_add_provider(), but nothing ever unwinds it: there is no of_clk_del_provider() call and the driver has no remove callback. Each of_clk_add_provider() allocates a struct of_clk_provider, takes a reference on the OF node and adds an entry to the global of_clk_providers list, none of which is released when the device is unbound. Every bind/unbind (or module reload) therefore leaks a provider structure and an of_node reference. The clock itself is already device-managed (devm_clk_register()); only the provider registration was not. Use devm_of_clk_add_hw_provider() so the provider is removed automatically on unbind. Tie it to the parent i2c device, whose OF node carries the #clock-cells and clock-output-names properties (the RTC class device has no OF node of its own).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.4a39a6405d5f949bc651694028a55d74c514ef1f9
Vendor states this is fixed in 08a59c28c2bdbcd655e99526c86a41dc83834283 (fixed)
Vendor states this is fixed in 2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675 (fixed)
Vendor states this is fixed in 30b7c63af50fe1464e7582a37de1ca4bd030ecc1 (fixed)
Vendor states this is fixed in 36cb00c33bd83e7ce31b5a9f1f7c70db0cb7776c (fixed)
Vendor states this is fixed in 6218c0533a72235ec9c5f41b812c63d963bd4a3e (fixed)
Vendor states this is fixed in 7afb8db47c4f107bce89cfe5115fb31ba7c94665 (fixed)
Vendor states this is fixed in 97edf3fd9a46ea89a167966991c0449cfa07b36f (fixed)
Vendor states this is fixed in 9c48a53685040bb0de45a640b34055cbbfc69d4f (fixed)
Vendor states this is fixed in 4.4 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card