Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected a39a6405d5f949bc651694028a55d74c514ef1f9 – < 2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675
    • affected a39a6405d5f949bc651694028a55d74c514ef1f9 – < 36cb00c33bd83e7ce31b5a9f1f7c70db0cb7776c
    • affected a39a6405d5f949bc651694028a55d74c514ef1f9 – < 30b7c63af50fe1464e7582a37de1ca4bd030ecc1
    • affected a39a6405d5f949bc651694028a55d74c514ef1f9 – < 7afb8db47c4f107bce89cfe5115fb31ba7c94665
    • affected a39a6405d5f949bc651694028a55d74c514ef1f9 – < 97edf3fd9a46ea89a167966991c0449cfa07b36f
    • affected a39a6405d5f949bc651694028a55d74c514ef1f9 – < 08a59c28c2bdbcd655e99526c86a41dc83834283
    • affected a39a6405d5f949bc651694028a55d74c514ef1f9 – < 6218c0533a72235ec9c5f41b812c63d963bd4a3e
    • affected a39a6405d5f949bc651694028a55d74c514ef1f9 – < 9c48a53685040bb0de45a640b34055cbbfc69d4f
  • Linux · Linux

    • affected 4.4
    • unaffected < 4.4
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90126 badge
[![CVE-2026-90126](https://cveledger.app/badge/CVE-2026-90126.svg)](https://cveledger.app/cve/CVE-2026-90126)

Record last updated .