Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2026-31741

medium

In the Linux kernel, the following vulnerability has been resolved: counter: rz-mtu3-cnt: prevent counter from being toggled multiple times Runtime PM counte…

Vendor / product: Linux — linux kernel

In the Linux kernel, the following vulnerability has been resolved: counter: rz-mtu3-cnt: prevent counter from being toggled multiple times Runtime PM counter is incremented / decremented each time the sysfs enable file is written to. If user writes 0 to the sysfs enable file multiple times, runtime PM usage count underflows, generating the following message. rz-mtu3-counter rz-mtu3-counter.0: Runtime PM usage count underflow! At the same time, hardware registers end up being accessed with clocks off in rz_mtu3_terminate_counter() to disable an already disabled channel. If user writes 1 to the sysfs enable file multiple times, runtime PM usage count will be incremented each time, requiring the same number of 0 writes to get it back to 0. If user writes 0 to the sysfs enable file while PWM is in progress, PWM is stopped without counter being the owner of the underlying MTU3 channel. Check against the cached count_is_enabled value and exit if the user is trying to set the same enable value.

CVSS
5.5
5.5 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2026-05-01 15:16
Modified: 2026-11-11 21:10
NVD status: Analyzed
Last synced 5 hours ago
Verified against the source API 2026-11-11 21:11 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥6.4 <6.6.134, ≥6.7 <6.12.81, ≥6.13 <6.18.22, ≥6.19 <6.19.12, 7.0

Weakness classification (CWE)

NVD-CWE-Other

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/67c3f99bed6f422ba343d2b70a2eeeccdfd91bef
Patch / mitigation: https://git.kernel.org/stable/c/885aa739a07ab45e90dfa997205acec97979ce4e
Patch / mitigation: https://git.kernel.org/stable/c/ced8b48420eddb1251f93c22dc23fa136490b3cd
Patch / mitigation: https://git.kernel.org/stable/c/e07237df8538b0ae98dce112e4f6db093d767f80
Patch / mitigation: https://git.kernel.org/stable/c/f5f6f06d7e6d262026578b59ba7426eb04acce5d

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-11 21:11 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs