CVE Intelligence
Unknown

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

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

Published Sep 17, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.21%
ahead of 11% of scored CVEs · Oct 18, 2026
Affects
Linux
Linux
CVSS base
—
Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux ≥ a39a6405d5f949bc651694028a55d74c514ef1f9 and < 2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675≥ a39a6405d5f949bc651694028a55d74c514ef1f9 and < 36cb00c33bd83e7ce31b5a9f1f7c70db0cb7776c≥ a39a6405d5f949bc651694028a55d74c514ef1f9 and < 30b7c63af50fe1464e7582a37de1ca4bd030ecc1≥ a39a6405d5f949bc651694028a55d74c514ef1f9 and < 7afb8db47c4f107bce89cfe5115fb31ba7c94665≥ a39a6405d5f949bc651694028a55d74c514ef1f9 and < 97edf3fd9a46ea89a167966991c0449cfa07b36f≥ a39a6405d5f949bc651694028a55d74c514ef1f9 and < 08a59c28c2bdbcd655e99526c86a41dc83834283≥ a39a6405d5f949bc651694028a55d74c514ef1f9 and < 6218c0533a72235ec9c5f41b812c63d963bd4a3e≥ a39a6405d5f949bc651694028a55d74c514ef1f9 and < 9c48a53685040bb0de45a640b34055cbbfc69d4f
and 1 more version 4.4
Vulnerable CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 18, 2026 · 3 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 15, 2026
  • Affected products added · linux/linux
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Received
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Sep 17, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 19, 2026 – Oct 19, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

10 on the record

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

  • Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 1d
  • Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 1d
  • Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 1d
  • Unknown CVE-2026-98865 sched_ext: Don't run ops.dequeue() with a DSQ lock held 1d
  • Unknown CVE-2026-98864 sched_ext: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task 1d
  • Unknown CVE-2026-98863 KVM: x86: Re-pend GET_NESTED_STATE_PAGES if getting said pages fails 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CVSS score published by NVD, the CNA, CISA or GitHub so far.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-90126 is "rtc: pcf8563: fix clock provider leak on unbind", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.