CVE-2025-68354: regulator: core: Protect regulator_supply_alias_list with regulator_list_mutex
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 09811a83b214cc15521e0d818e43ae9043e9a28d, 0cc15a10c3b4ab14cd71b779fd5c9ca0cb2bc30d, 431a1d44ad4866362cc28fc1cc4ca93d84989239; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.
Low priority for now. Upgrade to Linux Linux 09811a83b214cc15521e0d818e43ae9043e9a28d, 0cc15a10c3b4ab14cd71b779fd5c9ca0cb2bc30d, 431a1d44ad4866362cc28fc1cc4ca93d84989239; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 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: regulator: core: Protect regulator_supply_alias_list with regulator_list_mutex regulator_supply_alias_list was accessed without any locking in regulator_supply_alias(), regulator_register_supply_alias(), and regulator_unregister_supply_alias(). Concurrent registration, unregistration and lookups can race, leading to: 1 use-after-free if an alias entry is removed while being read, 2 duplicate entries when two threads register the same alias, 3 inconsistent alias mappings observed by consumers. Protect all traversals, insertions and deletions on regulator_supply_alias_list with the existing regulator_list_mutex.
- Published
- Dec 24, 2025
- Updated
- Oct 13, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
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.
Is your version affected? Check itNoroxi 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
- 3.13affected
- a06ccd9c3785fa5550917ae036944f4e080b5749 and later · before e1587064137028e7edcca14fb766b68d27bec94baffected · git
- a06ccd9c3785fa5550917ae036944f4e080b5749 and later · before 9d041a7ba13f21adfac052eb3fda1df62f2166c1affected · git
- a06ccd9c3785fa5550917ae036944f4e080b5749 and later · before a63fbc07d1b34a9821ea3b31ff4e6456f9d0aa61affected · git
- a06ccd9c3785fa5550917ae036944f4e080b5749 and later · before 09811a83b214cc15521e0d818e43ae9043e9a28daffected · git
- a06ccd9c3785fa5550917ae036944f4e080b5749 and later · before a9864d42ebcdd394ebb864643b961b36e7b515beaffected · git
- a06ccd9c3785fa5550917ae036944f4e080b5749 and later · before 431a1d44ad4866362cc28fc1cc4ca93d84989239affected · git
- a06ccd9c3785fa5550917ae036944f4e080b5749 and later · before 64099b5c0aeb70bc7cd5556eb7f59c5b4a5010bfaffected · git
- a06ccd9c3785fa5550917ae036944f4e080b5749 and later · before 0cc15a10c3b4ab14cd71b779fd5c9ca0cb2bc30daffected · git
- before 3.13not 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.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.13-1 | 6.17.13-1 |
| openSUSE:Tumbleweed | kernel-source | before 6.18.5-1.1 | 6.18.5-1.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-2025-68352Dec 24, 2025 · spi: ch341: fix out-of-bounds memory access in ch341_transfer_one31Monitor
- ← EarlierCVE-2025-68353Dec 24, 2025 · net: vxlan: prevent NULL deref in vxlan_xmit_one0Monitor
- Later →CVE-2025-68355Dec 24, 2025 · bpf: Fix exclusive map memory leak0Monitor
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 | 09811a83b214cc15521e0d818e43ae9043e9a28d | Vendor (CNA) |
| Linux Linux | 0cc15a10c3b4ab14cd71b779fd5c9ca0cb2bc30d | Vendor (CNA) |
| Linux Linux | 431a1d44ad4866362cc28fc1cc4ca93d84989239 | Vendor (CNA) |
| Linux Linux | 64099b5c0aeb70bc7cd5556eb7f59c5b4a5010bf | Vendor (CNA) |
| Linux Linux | 9d041a7ba13f21adfac052eb3fda1df62f2166c1 | Vendor (CNA) |
| Linux Linux | a63fbc07d1b34a9821ea3b31ff4e6456f9d0aa61 | Vendor (CNA) |
| Linux Linux | a9864d42ebcdd394ebb864643b961b36e7b515be | Vendor (CNA) |
| Linux Linux | e1587064137028e7edcca14fb766b68d27bec94b | Vendor (CNA) |
| azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 | 6.6.121.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 6.18.5-1.1 · openSUSE:Tumbleweed | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/0cc15a10c3b4ab14cd71b779fd5c9ca0cb2bc30d
- git.kernel.org/stable/c/431a1d44ad4866362cc28fc1cc4ca93d84989239
- git.kernel.org/stable/c/64099b5c0aeb70bc7cd5556eb7f59c5b4a5010bf
- git.kernel.org/stable/c/9d041a7ba13f21adfac052eb3fda1df62f2166c1
- git.kernel.org/stable/c/a63fbc07d1b34a9821ea3b31ff4e6456f9d0aa61
- git.kernel.org/stable/c/a9864d42ebcdd394ebb864643b961b36e7b515be
- git.kernel.org/stable/c/e1587064137028e7edcca14fb766b68d27bec94b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.