PatchSiren cyber security CVE debrief
CVE-2026-90126 Linux CVE debrief
A vulnerability in the Linux kernel's rtc: pcf8563: fix clock provider leak on unbind has been resolved. The issue arises from the pcf8563_clkout_register_clk() function registering the CLKOUT clock provider with of_clk_add_provider(), but not having a corresponding of_clk_del_provider() call or a remove callback. This results in a leak of a provider structure and an of_node reference each time the device is unbound.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-17
- Original CVE updated
- 2026-10-19
- Advisory published
- 2026-09-17
- Advisory updated
- 2026-10-19
Who should care
Linux kernel maintainers and users who need to assess exposure and prioritize verification of affected versions, as well as apply the provided fix to prevent potential clock provider leaks.
Why it matters
A vulnerability in the Linux kernel's rtc: pcf8563: fix clock provider leak on unbind has been resolved, and Linux kernel maintainers and users should assess exposure and prioritize verification of affected versions, as well as apply the provided fix to prevent potential clock provider leaks.
- Verification of affected Linux kernel versions is required to determine exposure.
- Applying the provided fix is necessary to prevent potential clock provider leaks.
- Remediation priority is medium due to the potential for resource leaks.
Technical summary
The pcf8563_clkout_register_clk() function 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.
Defensive priority
Linux kernel maintainers and users should assess exposure and prioritize verification of affected versions, as well as apply the provided fix to prevent potential clock provider leaks.
Recommended defensive actions
- Review and apply the provided fix to prevent potential clock provider leaks
- Verify affected versions of the Linux kernel
- Assess exposure and prioritize remediation
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record and source item provide details on the vulnerability, including a description of the issue and references to the relevant commits. Linux kernel maintainers and users should verify affected versions and apply the provided fix to prevent potential clock provider leaks. This involves reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. The fix addresses a clock provider leak on unbind in the pcf8563 driver, which could lead to resource leaks if not properly rem…
Sources and references
Verified primary and authoritative sources
-
CVE-2026-90126 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-90126
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-90126 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-90126
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
rtc: pcf8563: fix clock provider leak on unbind
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/90xxx/CVE-2026-90126.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/36cb00c33bd83e7ce31b5a9f1f7c70db0cb7776c
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/30b7c63af50fe1464e7582a37de1ca4bd030ecc1
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/7afb8db47c4f107bce89cfe5115fb31ba7c94665
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/97edf3fd9a46ea89a167966991c0449cfa07b36f
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/08a59c28c2bdbcd655e99526c86a41dc83834283
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/6218c0533a72235ec9c5f41b812c63d963bd4a3e
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.