Memory leak via unremoved clock provider
Published Sep 17, 2026 · Updated Sep 17, 2026
A memory leak in Linux's PCF8563 RTC driver allows local users to consume kernel memory via repeated device unbinding. The pcf8563_clkout_register_clk() function registers a CLKOUT provider with of_clk_add_provider() without unregistering it, retaining a provider allocation and device-tree node reference after each unbind or module reload. Triggering requires administrative control over the relevant device lifecycle and an active CLKOUT provider; no crash or code execution is documented.
Summary
What happened
A memory leak in Linux's PCF8563 RTC driver allows local users to consume kernel memory via repeated device unbinding. The pcf8563_clkout_register_clk() function registers a CLKOUT provider with of_clk_add_provider() without unregistering it, retaining a provider allocation and device-tree node reference after each unbind or module reload. Triggering requires administrative control over the relevant device lifecycle and an active CLKOUT provider; no crash or code execution is documented.
The record
- CVE
- CVE-2026-90126
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.4
- Affected versionversion=a39a6405d5f949bc651694028a55d74c514ef1f9 <08a59c28c2bdbcd655e99526c86a41dc83834283
- Affected versionversion=a39a6405d5f949bc651694028a55d74c514ef1f9 <2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675
- Affected versionversion=a39a6405d5f949bc651694028a55d74c514ef1f9 <30b7c63af50fe1464e7582a37de1ca4bd030ecc1
- Affected versionversion=a39a6405d5f949bc651694028a55d74c514ef1f9 <36cb00c33bd83e7ce31b5a9f1f7c70db0cb7776c
- Affected versionversion=a39a6405d5f949bc651694028a55d74c514ef1f9 <6218c0533a72235ec9c5f41b812c63d963bd4a3e
- Affected versionversion=a39a6405d5f949bc651694028a55d74c514ef1f9 <7afb8db47c4f107bce89cfe5115fb31ba7c94665
- Affected versionversion=a39a6405d5f949bc651694028a55d74c514ef1f9 <97edf3fd9a46ea89a167966991c0449cfa07b36f
- Affected versionversion=a39a6405d5f949bc651694028a55d74c514ef1f9 <9c48a53685040bb0de45a640b34055cbbfc69d4f
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started