CVE-2025-22009regulator: dummy: force synchronous probing
- 5.5MediumCVSS base score
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: regulator: dummy: force synchronous probing Sometimes I get a NULL pointer dereference at boot time in kobject_get() with the following call stack: anatop_regulator_probe() devm_regulator_register() regulator_register() regulator_resolve_supply() kobject_get() By placing some extra BUG_ON() statements I could verify that this is raised because probing of the 'dummy' regulator driver is not completed ('dummy_regulator_rdev' is still NULL). In the JTAG debugger I can see that dummy_regulator_probe() and anatop_regulator_probe() can be run by different kernel threads (kworker/u4:*). I haven't further investigated whether this can be changed or if there are other possibilities to force synchronization between these two probe routines. On the other hand I don't expect much boot time penalty by probing the 'dummy' regulator synchronously.
Timeline
ID reserved
By Linux
- 3 months later
· 3 months later
Published
- 13 months later
· 13 months 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 259b93b21a9ffe5117af4dfb5505437e463c6a5a – < e26f24ca4fb940b15e092796c5993142a2558bd9
- affected 259b93b21a9ffe5117af4dfb5505437e463c6a5a – < d3b83a1442a09b145006eb4294b1a963c5345c9c
- affected 259b93b21a9ffe5117af4dfb5505437e463c6a5a – < 5ade367b56c3947c990598df92395ce737bee872
- affected 259b93b21a9ffe5117af4dfb5505437e463c6a5a – < 8619909b38eeebd3e60910158d7d68441fc954e9
- affected 6.4
- unaffected < 6.4
- unaffected 6.6.85 – ≤ 6.6.*
- unaffected 6.12.21 – ≤ 6.12.*
- unaffected 6.13.9 – ≤ 6.13.*
- unaffected 6.14 – ≤ *
References
References4
- https://git.kernel.org/stable/c/e26f24ca4fb940b15e092796c5993142a2558bd9 (opens in a new tab)
- https://git.kernel.org/stable/c/d3b83a1442a09b145006eb4294b1a963c5345c9c (opens in a new tab)
- https://git.kernel.org/stable/c/5ade367b56c3947c990598df92395ce737bee872 (opens in a new tab)
- https://git.kernel.org/stable/c/8619909b38eeebd3e60910158d7d68441fc954e9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-10337 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-22009)Record last updated .