rtc: pcf8563: fix clock provider leak on unbind
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 9c48a53685040bb0de45a640b34055cbbfc69d4f, Kernel 08a59c28c2bdbcd655e99526c86a41dc83834283, Kernel 2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675 and 12 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=a39a6405d5f949bc651694028a55d74c514ef1f9 <9c48a53685040bb0de45a640b34055cbbfc69d4f, >=a39a6405d5f949bc651694028a55d74c514ef1f9 <08a59c28c2bdbcd655e99526c86a41dc83834283, >=a39a6405d5f949bc651694028a55d74c514ef1f9 <2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675, >=a39a6405d5f949bc651694028a55d74c514ef1f9 <30b7c63af50fe1464e7582a37de1ca4bd030ecc1, >=a39a6405d5f949bc651694028a55d74c514ef1f9 <36cb00c33bd83e7ce31b5a9f1f7c70db0cb7776c, >=a39a6405d5f949bc651694028a55d74c514ef1f9 <6218c0533a72235ec9c5f41b812c63d963bd4a3e, >=a39a6405d5f949bc651694028a55d74c514ef1f9 <7afb8db47c4f107bce89cfe5115fb31ba7c94665, >=a39a6405d5f949bc651694028a55d74c514ef1f9 <97edf3fd9a46ea89a167966991c0449cfa07b36f, =4.4 | 9c48a53685040bb0de45a640b34055cbbfc69d4f, 08a59c28c2bdbcd655e99526c86a41dc83834283, 2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675, 30b7c63af50fe1464e7582a37de1ca4bd030ecc1, 36cb00c33bd83e7ce31b5a9f1f7c70db0cb7776c, 6218c0533a72235ec9c5f41b812c63d963bd4a3e, 7afb8db47c4f107bce89cfe5115fb31ba7c94665, 97edf3fd9a46ea89a167966991c0449cfa07b36f |
| linux-kernel: Kernel | >=5.11.0 <5.15.221, >=5.16.0 <6.1.188, >=6.13.0 <6.18.52, >=6.19.0 <7.2.6, >=6.2.0 <6.6.157, >=6.7.0 <6.12.110, >=4.4.0 <5.10.270 | 5.15.221, 6.1.188, 6.18.52, 7.2.6, 6.6.157, 6.12.110, 5.10.270 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket