CVE-2022-50724

regulator: core: fix resource leak in regulator_register()

N/A
Published: December 24, 2025 at 12:22 PM UTC
Updated: June 17, 2026 at 05:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.3%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.14.203v ≥ 4.19.153v ≥ 4.9.241v ≥ 5.8.17v ≥ 5.9.24.14.203 ≤ v < 4.154.19.153 ≤ v < 4.204.9.241 ≤ v < 4.105.10 ≤ v < 5.10.1635.10 ≤ v < 5.15.865.10 ≤ v < 6.0.165.10 ≤ v < 6.1.25.10 ≤ v < 6.25.4.73 ≤ v < 5.4.2295.8.17 ≤ v < 5.95.9.2 ≤ v < 5.10120ec32a7774b5061ced1a9a7ff833edd8b4cb6167c3b1f9793a1fb23e75e693f078420850306d41d58235c062309d51660fd04182d7a8ab6a48ad63fc99e38fdbf6b693693f861aa55a50a74c2d2024.14.2034.19.1534.9.2415.105.4.735.8.175.9.296c6b5d5775637b3095ef934f871044811fd4db7aea6cb99703e17019e025aa71643b4d3e0a24413f58ce31b05b4ca0c200a5cbe4724efe279405095
Vendor states this is fixed in 35593d60b1622834984c43add7646d4069671aa9 (fixed)
Vendor states this is fixed in 6a03c31d08f95dca9633a552de167b9e625833a8 (fixed)
Vendor states this is fixed in 90b713aadc1240bf2dd03d610d6c1d016a9123a2 (fixed)
Vendor states this is fixed in ba62319a42c50e6254e98b3f316464fac8e77968 (fixed)
Vendor states this is fixed in c4c64d8abd656b9807b63178750fa91454602b86 (fixed)
Vendor states this is fixed in f86b2f216636790d5922458578825e4628fb570f (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.86 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Affected range stops below 5.9, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.0.16 (unaffected)
Vendor states this is fixed in 6.1.2 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card