CVE-2026-90126: rtc: pcf8563: fix clock provider leak on unbind
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 08a59c28c2bdbcd655e99526c86a41dc83834283, 2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675, 30b7c63af50fe1464e7582a37de1ca4bd030ecc1; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 08a59c28c2bdbcd655e99526c86a41dc83834283, 2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675, 30b7c63af50fe1464e7582a37de1ca4bd030ecc1; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.4affected
- a39a6405d5f949bc651694028a55d74c514ef1f9 and later · before 2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675affected · git
- a39a6405d5f949bc651694028a55d74c514ef1f9 and later · before 36cb00c33bd83e7ce31b5a9f1f7c70db0cb7776caffected · git
- a39a6405d5f949bc651694028a55d74c514ef1f9 and later · before 30b7c63af50fe1464e7582a37de1ca4bd030ecc1affected · git
- a39a6405d5f949bc651694028a55d74c514ef1f9 and later · before 7afb8db47c4f107bce89cfe5115fb31ba7c94665affected · git
- a39a6405d5f949bc651694028a55d74c514ef1f9 and later · before 97edf3fd9a46ea89a167966991c0449cfa07b36faffected · git
- a39a6405d5f949bc651694028a55d74c514ef1f9 and later · before 08a59c28c2bdbcd655e99526c86a41dc83834283affected · git
- a39a6405d5f949bc651694028a55d74c514ef1f9 and later · before 6218c0533a72235ec9c5f41b812c63d963bd4a3eaffected · git
- a39a6405d5f949bc651694028a55d74c514ef1f9 and later · before 9c48a53685040bb0de45a640b34055cbbfc69d4faffected · git
- before 4.4not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90124Sep 17, 2026 · irqchip/renesas-rzg2l: Fix loss of interrupt0Monitor
- ← EarlierCVE-2026-90125Sep 17, 2026 · smb: client: fix request buffer leak in smb2_new_read_req()0Monitor
- Later →CVE-2026-90127Sep 17, 2026 · virtio: rtc: time out alarm requests0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 08a59c28c2bdbcd655e99526c86a41dc83834283 | Vendor (CNA) |
| Linux Linux | 2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675 | Vendor (CNA) |
| Linux Linux | 30b7c63af50fe1464e7582a37de1ca4bd030ecc1 | Vendor (CNA) |
| Linux Linux | 36cb00c33bd83e7ce31b5a9f1f7c70db0cb7776c | Vendor (CNA) |
| Linux Linux | 6218c0533a72235ec9c5f41b812c63d963bd4a3e | Vendor (CNA) |
| Linux Linux | 7afb8db47c4f107bce89cfe5115fb31ba7c94665 | Vendor (CNA) |
| Linux Linux | 97edf3fd9a46ea89a167966991c0449cfa07b36f | Vendor (CNA) |
| Linux Linux | 9c48a53685040bb0de45a640b34055cbbfc69d4f | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2b5622cf4ee218b6f98d31dbf3fbd44b9b6bd675
- git.kernel.org/stable/c/30b7c63af50fe1464e7582a37de1ca4bd030ecc1
- git.kernel.org/stable/c/36cb00c33bd83e7ce31b5a9f1f7c70db0cb7776c
- git.kernel.org/stable/c/6218c0533a72235ec9c5f41b812c63d963bd4a3e
- git.kernel.org/stable/c/7afb8db47c4f107bce89cfe5115fb31ba7c94665
- git.kernel.org/stable/c/97edf3fd9a46ea89a167966991c0449cfa07b36f
- git.kernel.org/stable/c/9c48a53685040bb0de45a640b34055cbbfc69d4f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.