CVE-2026-99022: regulator: ltc3676: don't read the write-only HRST and CLIRQ registers
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.16% (FIRST EPSS).
- Fixed version: Linux Linux 0893de2397d85547d4b88379044aa541b07b56af, 199a62d70314d21f06a9a6faaa3ef54d0404910c, 1fb0d58fd363b439b4faf08a16ee6ae38b575cd4; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0893de2397d85547d4b88379044aa541b07b56af, 199a62d70314d21f06a9a6faaa3ef54d0404910c, 1fb0d58fd363b439b4faf08a16ee6ae38b575cd4; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: regulator: ltc3676: don't read the write-only HRST and CLIRQ registers HRST (0x1e) and CLIRQ (0x1f) are write-only command strobes. Writing HRST triggers a hard reset of the chip and writing CLIRQ clears the interrupt; reading them returns nothing useful, and the read itself fires the command. The result is that a plain register dump resets the board: cat /sys/kernel/debug/regmap/2-003c/registers walks every readable register, hits HRST, and the board reboots. Split the callback back in two so HRST and CLIRQ stay writable but are no longer readable. The readable range is left unchanged (LTC3676_BUCK1 ... LTC3676_IRQSTAT).
- Published
- Oct 23, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th 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.1%
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.9affected
- 37b918a034feda1b1ef404acf003812f37ab8da2 and later · before 4cc1e849bb7dd8deb37f6a51e1aaf725e2016595affected · git
- 37b918a034feda1b1ef404acf003812f37ab8da2 and later · before 0893de2397d85547d4b88379044aa541b07b56afaffected · git
- 37b918a034feda1b1ef404acf003812f37ab8da2 and later · before f8b0ccdcf3ca7cf6e4c2c400e80f81a727f768c7affected · git
- 37b918a034feda1b1ef404acf003812f37ab8da2 and later · before fd376d83741118e0212f0da985889c1a98d9c827affected · git
- 37b918a034feda1b1ef404acf003812f37ab8da2 and later · before 1fb0d58fd363b439b4faf08a16ee6ae38b575cd4affected · git
- 37b918a034feda1b1ef404acf003812f37ab8da2 and later · before 199a62d70314d21f06a9a6faaa3ef54d0404910caffected · git
- 37b918a034feda1b1ef404acf003812f37ab8da2 and later · before ca5d85335a8fa6e87b45629f1a07b412482cab17affected · git
- 37b918a034feda1b1ef404acf003812f37ab8da2 and later · before 28c2388ee24cdbefbcc458fa41ef7bffaaa1cc83affected · git
- before 4.9not 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 | from 0 | — |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.11-1 | 7.2.11-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-99020Oct 23, 2026 · regulator: tps6594-regulator: Fix n_linear_ranges for TPS65224 BUCK2-40Monitor
- ← EarlierCVE-2026-99021Oct 23, 2026 · regulator: of: fill in supply names in of_regulator_bulk_get_all()0Monitor
- Later →CVE-2026-99023Oct 23, 2026 · power: sequencing: pcie-m2: Fix leaking array from of_regulator_bulk_get_all()0Monitor
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 | 0893de2397d85547d4b88379044aa541b07b56af | Vendor (CNA) |
| Linux Linux | 199a62d70314d21f06a9a6faaa3ef54d0404910c | Vendor (CNA) |
| Linux Linux | 1fb0d58fd363b439b4faf08a16ee6ae38b575cd4 | Vendor (CNA) |
| Linux Linux | 28c2388ee24cdbefbcc458fa41ef7bffaaa1cc83 | Vendor (CNA) |
| Linux Linux | 4cc1e849bb7dd8deb37f6a51e1aaf725e2016595 | Vendor (CNA) |
| Linux Linux | ca5d85335a8fa6e87b45629f1a07b412482cab17 | Vendor (CNA) |
| Linux Linux | f8b0ccdcf3ca7cf6e4c2c400e80f81a727f768c7 | Vendor (CNA) |
| Linux Linux | fd376d83741118e0212f0da985889c1a98d9c827 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | 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.
- Published
- Fix recordedsame day
- TodayOct 31, 2026+8 d
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1390 · Oct 26, 2026(Linux Kernel Güvenlik Bildirimi)
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
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.