iio: dac: m62332: Fix regulator reference count imbalance
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 08ac8d2976d57aa943d64e351c4d0bd8bb0c6de9, 1d3a7d7dd3adee19e00be2b2237140f0fe169484, 9263b9ad968a563337a60e0eb66e35186e1faf9a.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 08ac8d2976d57aa943d64e351c4d0bd8bb0c6de9, 1d3a7d7dd3adee19e00be2b2237140f0fe169484, 9263b9ad968a563337a60e0eb66e35186e1faf9a or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: iio: dac: m62332: Fix regulator reference count imbalance m62332_set_value() enables the Vcc regulator on every write of a non-zero value and disables it on every write of zero, without tracking the channel's current state. Because the regulator is reference counted, changing a channel directly from one non-zero value to another enables it more than once, while a later write of zero disables it only once. The reference count never returns to zero and the regulator is left enabled indefinitely. Only enable the regulator on the transition from zero to non-zero, and only disable it on the transition from non-zero to zero, using the previously stored channel value to detect the edge. Balance the regulator on the I2C error path so the reference count stays consistent if the write fails.
- Published
- Sep 16, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.2affected
- b87b0c0f81e8d11c881b726b886b7502ab67d884 and later · before bac0ed8bee651aa841375edf72c6ab1d10ac80c6affected · git
- b87b0c0f81e8d11c881b726b886b7502ab67d884 and later · before 9263b9ad968a563337a60e0eb66e35186e1faf9aaffected · git
- b87b0c0f81e8d11c881b726b886b7502ab67d884 and later · before 1d3a7d7dd3adee19e00be2b2237140f0fe169484affected · git
- b87b0c0f81e8d11c881b726b886b7502ab67d884 and later · before f5acb824277a97a5210c454872202bf7f08c75d4affected · git
- b87b0c0f81e8d11c881b726b886b7502ab67d884 and later · before ae18d2d2ef27a4d04fda6e30c23774513dc9be1eaffected · git
- b87b0c0f81e8d11c881b726b886b7502ab67d884 and later · before 08ac8d2976d57aa943d64e351c4d0bd8bb0c6de9affected · git
- b87b0c0f81e8d11c881b726b886b7502ab67d884 and later · before 9fe22f563b2a0fdb11fd3711a8c39c023629c08aaffected · git
- b87b0c0f81e8d11c881b726b886b7502ab67d884 and later · before a130404ce0b69ca1438126bd81c1985d3b4d2e6faffected · git
- before 4.2not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89934Sep 16, 2026 · iio: light: ltrf216a: fix runtime PM reference leak in error path0Monitor
- ← EarlierCVE-2026-89935Sep 16, 2026 · iio: light: apds9306: fix PM reference leak in apds9306_read_data()0Monitor
- Later →CVE-2026-89937Sep 16, 2026 · iio: chemical: sgp30: Handle IAQ thread creation failure0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 08ac8d2976d57aa943d64e351c4d0bd8bb0c6de9 | Vendor (CNA) |
| Linux Linux | 1d3a7d7dd3adee19e00be2b2237140f0fe169484 | Vendor (CNA) |
| Linux Linux | 9263b9ad968a563337a60e0eb66e35186e1faf9a | Vendor (CNA) |
| Linux Linux | 9fe22f563b2a0fdb11fd3711a8c39c023629c08a | Vendor (CNA) |
| Linux Linux | a130404ce0b69ca1438126bd81c1985d3b4d2e6f | Vendor (CNA) |
| Linux Linux | ae18d2d2ef27a4d04fda6e30c23774513dc9be1e | Vendor (CNA) |
| Linux Linux | bac0ed8bee651aa841375edf72c6ab1d10ac80c6 | Vendor (CNA) |
| Linux Linux | f5acb824277a97a5210c454872202bf7f08c75d4 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1d3a7d7dd3adee19e00be2b2237140f0fe169484
- git.kernel.org/stable/c/9263b9ad968a563337a60e0eb66e35186e1faf9a
- git.kernel.org/stable/c/9fe22f563b2a0fdb11fd3711a8c39c023629c08a
- git.kernel.org/stable/c/a130404ce0b69ca1438126bd81c1985d3b4d2e6f
- git.kernel.org/stable/c/ae18d2d2ef27a4d04fda6e30c23774513dc9be1e
- git.kernel.org/stable/c/bac0ed8bee651aa841375edf72c6ab1d10ac80c6
- git.kernel.org/stable/c/f5acb824277a97a5210c454872202bf7f08c75d4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.