CVE-2026-99022 json
regulator: ltc3676: don't read the write-only HRST and CLIRQ registers
published 19d ago modified 12d ago also EUVD-2026-108816
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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).
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.11-1
debian advisories DEBIAN-CVE-2026-99022
- linux Ubuntu 26.10 7.3.0-10.10
- linux-aws Ubuntu 26.10 7.3.0-1004.4
- linux-gcp Ubuntu 26.10 7.3.0-1004.4
- linux-raspi Ubuntu 26.10 7.3.0-1004.4
- linux-riscv Ubuntu 26.10 7.3.0-10.10.1
- linux-oracle Ubuntu 26.10 7.3.0-1004.4
- linux-realtime Ubuntu 26.10 7.3.0-10.10.1
ubuntu advisories UBUNTU-CVE-2026-99022
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default Linux Micro 6.0 6.4.0-159998.55.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default-base Linux Micro 6.0 6.4.0-159998.55.1.159998.21.42
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.90.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.90.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
suse advisories SUSE-SU-2026:24550-1SUSE-SU-2026:5091-1
- git.kernel.org/stable/c/4cc1e849bb7dd8deb37f6a51e1aaf725e2016595 commit
- git.kernel.org/stable/c/0893de2397d85547d4b88379044aa541b07b56af commit
- git.kernel.org/stable/c/f8b0ccdcf3ca7cf6e4c2c400e80f81a727f768c7 commit
- git.kernel.org/stable/c/fd376d83741118e0212f0da985889c1a98d9c827 commit
- git.kernel.org/stable/c/1fb0d58fd363b439b4faf08a16ee6ae38b575cd4 commit
- git.kernel.org/stable/c/199a62d70314d21f06a9a6faaa3ef54d0404910c commit
- git.kernel.org/stable/c/ca5d85335a8fa6e87b45629f1a07b412482cab17 commit
- git.kernel.org/stable/c/28c2388ee24cdbefbcc458fa41ef7bffaaa1cc83 commit
Is CVE-2026-99022 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99022 updated cvss 4.4
kernel: regulator: ltc3676: don't read the write-only HRST and CLIRQ registers
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/4cc1e849bb7dd8deb37f6a51e1aaf725e2016595
- git.kernel.org /stable/c/0893de2397d85547d4b88379044aa541b07b56af
- git.kernel.org /stable/c/f8b0ccdcf3ca7cf6e4c2c400e80f81a727f768c7
- git.kernel.org /stable/c/fd376d83741118e0212f0da985889c1a98d9c827
- git.kernel.org /stable/c/1fb0d58fd363b439b4faf08a16ee6ae38b575cd4
- git.kernel.org /stable/c/199a62d70314d21f06a9a6faaa3ef54d0404910c
- git.kernel.org /stable/c/ca5d85335a8fa6e87b45629f1a07b412482cab17
- git.kernel.org /stable/c/28c2388ee24cdbefbcc458fa41ef7bffaaa1cc83
Sources
- CVE List CVE-2026-99022
- NVD CVE-2026-99022
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.