CVE-2022-50724: regulator: core: fix resource leak in regulator_register()
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.26% (FIRST EPSS).
- Fixed version: Linux Linux 35593d60b1622834984c43add7646d4069671aa9, 4.10, 4.15.
Low priority for now. Upgrade to Linux Linux 35593d60b1622834984c43add7646d4069671aa9, 4.10, 4.15 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: fix resource leak in regulator_register() I got some resource leak reports while doing fault injection test: OF: ERROR: memory leak, expected refcount 1 instead of 100, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /i2c/pmic@64/regulators/buck1 unreferenced object 0xffff88810deea000 (size 512): comm "490-i2c-rt5190a", pid 253, jiffies 4294859840 (age 5061.046s) hex dump (first 32 bytes): 00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00 .....N.......... ff ff ff ff ff ff ff ff a0 1e 00 a1 ff ff ff ff ................ backtrace: [<00000000d78541e2>] kmalloc_trace+0x21/0x110 [<00000000b343d153>] device_private_init+0x32/0xd0 [<00000000be1f0c70>] device_add+0xb2d/0x1030 [<00000000e3e6344d>] regulator_register+0xaf2/0x12a0 [<00000000e2f5e754>] devm_regulator_register+0x57/0xb0 [<000000008b898197>] rt5190a_probe+0x52a/0x861 [rt5190a_regulator] unreferenced object 0xffff88810b617b80 (size 32): comm "490-i2c-rt5190a", pid 253, jiffies 4294859904 (age 5060.983s) hex dump (first 32 bytes): 72 65 67 75 6c 61 74 6f 72 2e 32 38 36 38 2d 53 regulator.2868-S 55 50 50 4c 59 00 ff ff 29 00 00 00 2b 00 00 00 UPPLY...)...+... backtrace: [<000000009da9280d>] __kmalloc_node_track_caller+0x44/0x1b0 [<0000000025c6a4e5>] kstrdup+0x3a/0x70 [<00000000790efb69>] create_regulator+0xc0/0x4e0 [<0000000005ed203a>] regulator_resolve_supply+0x2d4/0x440 [<0000000045796214>] regulator_register+0x10b3/0x12a0 [<00000000e2f5e754>] devm_regulator_register+0x57/0xb0 [<000000008b898197>] rt5190a_probe+0x52a/0x861 [rt5190a_regulator] After calling regulator_resolve_supply(), the 'rdev->supply' is set by set_supply(), after this set, in the error path, the resources need be released, so call regulator_put() to avoid the leaks.
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 18th 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
- 1d58235c062309d51660fd04182d7a8ab6a48ad6, 167c3b1f9793a1fb23e75e693f078420850306d4, 3fc99e38fdbf6b693693f861aa55a50a74c2d202, 96c6b5d5775637b3095ef934f871044811fd4db7, f58ce31b05b4ca0c200a5cbe4724efe279405095, 5.10affected
- 0120ec32a7774b5061ced1a9a7ff833edd8b4cb6 and later · before 35593d60b1622834984c43add7646d4069671aa9affected · git
- aea6cb99703e17019e025aa71643b4d3e0a24413 and later · before 6a03c31d08f95dca9633a552de167b9e625833a8affected · git
- aea6cb99703e17019e025aa71643b4d3e0a24413 and later · before c4c64d8abd656b9807b63178750fa91454602b86affected · git
- aea6cb99703e17019e025aa71643b4d3e0a24413 and later · before 90b713aadc1240bf2dd03d610d6c1d016a9123a2affected · git
- aea6cb99703e17019e025aa71643b4d3e0a24413 and later · before f86b2f216636790d5922458578825e4628fb570faffected · git
- aea6cb99703e17019e025aa71643b4d3e0a24413 and later · before ba62319a42c50e6254e98b3f316464fac8e77968affected · git
- 5.4.73 and later · before 5.4.229affected · semver
- 4.9.241 and later · before 4.10affected · semver
- 4.14.203 and later · before 4.15affected · 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.4-1 | 6.1.4-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-2022-50722Dec 24, 2025 · media: ipu3-imgu: Fix NULL pointer dereference in active selection access0Monitor
- ← EarlierCVE-2022-50723Dec 24, 2025 · bnxt_en: fix memory leak in bnxt_nvm_test()0Monitor
- Later →CVE-2022-50725Dec 24, 2025 · media: vidtv: Fix use-after-free in vidtv_bridge_dvb_init()0Monitor
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 | 35593d60b1622834984c43add7646d4069671aa9 | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 5.10 | Vendor (CNA) |
| Linux Linux | 5.4.229 | Vendor (CNA) |
| Linux Linux | 5.9 | Vendor (CNA) |
| Linux Linux | 6a03c31d08f95dca9633a552de167b9e625833a8 | Vendor (CNA) |
| Linux Linux | 90b713aadc1240bf2dd03d610d6c1d016a9123a2 | Vendor (CNA) |
| Linux Linux | ba62319a42c50e6254e98b3f316464fac8e77968 | Vendor (CNA) |
| Linux Linux | c4c64d8abd656b9807b63178750fa91454602b86 | Vendor (CNA) |
| Linux Linux | f86b2f216636790d5922458578825e4628fb570f | Vendor (CNA) |
| debian:linux | 6.1.4-1 · 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.
No history yet (it accumulates with the daily EPSS job).
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).
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 (5 more)Show less
- git.kernel.org/stable/c/6a03c31d08f95dca9633a552de167b9e625833a8
- git.kernel.org/stable/c/90b713aadc1240bf2dd03d610d6c1d016a9123a2
- git.kernel.org/stable/c/ba62319a42c50e6254e98b3f316464fac8e77968
- git.kernel.org/stable/c/c4c64d8abd656b9807b63178750fa91454602b86
- git.kernel.org/stable/c/f86b2f216636790d5922458578825e4628fb570f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.