Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 7 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 37b918a034feda1b1ef404acf003812f37ab8da2 – < 4cc1e849bb7dd8deb37f6a51e1aaf725e2016595
    • affected 37b918a034feda1b1ef404acf003812f37ab8da2 – < 0893de2397d85547d4b88379044aa541b07b56af
    • affected 37b918a034feda1b1ef404acf003812f37ab8da2 – < f8b0ccdcf3ca7cf6e4c2c400e80f81a727f768c7
    • affected 37b918a034feda1b1ef404acf003812f37ab8da2 – < fd376d83741118e0212f0da985889c1a98d9c827
    • affected 37b918a034feda1b1ef404acf003812f37ab8da2 – < 1fb0d58fd363b439b4faf08a16ee6ae38b575cd4
    • affected 37b918a034feda1b1ef404acf003812f37ab8da2 – < 199a62d70314d21f06a9a6faaa3ef54d0404910c
    • affected 37b918a034feda1b1ef404acf003812f37ab8da2 – < ca5d85335a8fa6e87b45629f1a07b412482cab17
    • affected 37b918a034feda1b1ef404acf003812f37ab8da2 – < 28c2388ee24cdbefbcc458fa41ef7bffaaa1cc83
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99022 badge
[![CVE-2026-99022](https://cveledger.app/badge/CVE-2026-99022.svg)](https://cveledger.app/cve/CVE-2026-99022)

Record last updated .