# CVE-2026-99022: regulator: ltc3676: don't read the write-only HRST and CLIRQ registers


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-110873, BELL-CVE-2026-99022, DEBIAN-CVE-2026-99022, GHSA-668q-74cv-frqc, UBUNTU-CVE-2026-99022

## What is CVE-2026-99022?

CVE-2026-99022 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

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

## Which versions are affected by CVE-2026-99022?


## How do I fix CVE-2026-99022?

Upgrade to a fixed version.

## Is CVE-2026-99022 being exploited?

There is no known exploitation of CVE-2026-99022 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-99022 and fix it if it is affected.

What it is: CVE-2026-99022 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99022 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-99022/ (Markdown: https://insights.sbomify.com/CVE-2026-99022/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-99022
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99022
- OSV: https://osv.dev/vulnerability/CVE-2026-99022

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-99022/
Summaries are generated and may contain mistakes; the official description above is the record.