Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-99022

regulator: ltc3676: don't read the write-only HRST and CLIRQ registers

Products / packages Linux

Published

Share

Severity and exploitation

Not in CISA KEVNo CVSS score

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 21:25:33 UTC

Severity

unknown

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

The Linux kernel regulator for ltc3676 has a vulnerability where reading write-only registers HRST and CLIRQ can trigger a hard reset or clear an interrupt. Affected versions are prior to specific git commits. The impact is a potential board reboot when readable registers are accessed.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Linux · Linux

Linux

8 ranges
Linux version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

37b918a034feda1b1ef404acf003812f37ab8da2 → before 4cc1e849bb7dd8deb37f6a51e1aaf725e2016595

git versions

37b918a034feda1b1ef404acf003812f37ab8da2 → before 0893de2397d85547d4b88379044aa541b07b56af

git versions

37b918a034feda1b1ef404acf003812f37ab8da2 → before f8b0ccdcf3ca7cf6e4c2c400e80f81a727f768c7

git versions

37b918a034feda1b1ef404acf003812f37ab8da2 → before fd376d83741118e0212f0da985889c1a98d9c827

git versions

37b918a034feda1b1ef404acf003812f37ab8da2 → before 1fb0d58fd363b439b4faf08a16ee6ae38b575cd4

git versions

37b918a034feda1b1ef404acf003812f37ab8da2 → before 199a62d70314d21f06a9a6faaa3ef54d0404910c

git versions

37b918a034feda1b1ef404acf003812f37ab8da2 → before ca5d85335a8fa6e87b45629f1a07b412482cab17

git versions

37b918a034feda1b1ef404acf003812f37ab8da2 → before 28c2388ee24cdbefbcc458fa41ef7bffaaa1cc83

git versions

unaffected

unknown

Other versions: unaffected

Linux · Linux

Linux

10 ranges
Linux version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

4.9

unaffected

0 → before 4.9

semver versions

5.10.273 → through 5.10.*

semver versions

5.15.224 → through 5.15.*

semver versions

6.1.191 → through 6.1.*

semver versions

6.6.160 → through 6.6.*

semver versions

6.12.113 → through 6.12.*

semver versions

6.18.57 → through 6.18.*

semver versions

7.2.11 → through 7.2.*

semver versions

7.3 → through *

original_commit_for_fix versions

unknown

Other versions: affected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher 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).

References

8 sources
git.kernel.org/stable/c/4cc1e849bb7dd8deb37f6a51e1aaf725e2016595
Source referenceLinux
git.kernel.org/stable/c/0893de2397d85547d4b88379044aa541b07b56af
Source referenceLinux
git.kernel.org/stable/c/f8b0ccdcf3ca7cf6e4c2c400e80f81a727f768c7
Source referenceLinux
git.kernel.org/stable/c/fd376d83741118e0212f0da985889c1a98d9c827
Source referenceLinux
git.kernel.org/stable/c/1fb0d58fd363b439b4faf08a16ee6ae38b575cd4
Source referenceLinux
git.kernel.org/stable/c/199a62d70314d21f06a9a6faaa3ef54d0404910c
Source referenceLinux
View 2 more references
git.kernel.org/stable/c/ca5d85335a8fa6e87b45629f1a07b412482cab17
Source referenceLinux
git.kernel.org/stable/c/28c2388ee24cdbefbcc458fa41ef7bffaaa1cc83
Source referenceLinux

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification · not supplied
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-99022

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

Linux · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 5.10.273

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 5.15.224

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 6.1.191

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 6.6.160

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 6.12.113

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 6.18.57

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 7.2.11

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 7.3

Applicability preview
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "5.10.273"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "5.15.224"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "6.1.191"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "6.6.160"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "6.12.113"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "6.18.57"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "7.2.11"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "7.3"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 1
Linux

Assigning organization

2026-10-30

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.