cbcvebase.
CVE-2022-50616
published 2025-12-08

CVE-2022-50616: In the Linux kernel, the following vulnerability has been resolved: regulator: core: Use different devices for resource allocation and DT lookup Following by…

PriorityP425medium6.7
EPSS
0.18%
7.3th percentile
In the Linux kernel, the following vulnerability has been resolved: regulator: core: Use different devices for resource allocation and DT lookup Following by the below discussion, there's the potential UAF issue between regulator and mfd. https://lore.kernel.org/all/[email protected]/ From the analysis of Yingliang CPU A |CPU B mt6370_probe() | devm_mfd_add_devices() | |mt6370_regulator_probe() | regulator_register() | //allocate init_data and add it to devres | regulator_of_get_init_data() i2c_unregister_device() | device_del() | devres_release_all() | // init_data is freed | release_nodes() | | // using init_data causes UAF | regulator_register() It's common to use mfd core to create child device for the regulator. In order to do the DT lookup for init data, the child that registered the regulator would pass its parent as the parameter. And this causes init data resource allocated to its parent, not itself. The issue happen when parent device is going to release and regulator core is still doing some operation of init data constraint for the regulator of child device. To fix it, this patch expand 'regulator_register' API to use the different devices for init data allocation and DT lookup.

Affected

10 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.4-1 (bookworm)linux 6.1.4-1 (bookworm)
linuxlinux
linuxlinux>= a0c7b164ad115ec0556dc0904ee2218cbc5cedfa < cb29811d989bcb7ea81ca111c4b13878b344e086cb29811d989bcb7ea81ca111c4b13878b344e086
linuxlinux>= a0c7b164ad115ec0556dc0904ee2218cbc5cedfa < b0f25ca1ff9be7abd1679ae7e59a8f25dbffe67ab0f25ca1ff9be7abd1679ae7e59a8f25dbffe67a
linuxlinux>= a0c7b164ad115ec0556dc0904ee2218cbc5cedfa < 8f3cbcd6b440032ebc7f7d48a1689dcc70a4eb988f3cbcd6b440032ebc7f7d48a1689dcc70a4eb98
linuxlinux_kernel>= 0 < 6.1.4-16.1.4-1
linuxlinux_kernel>= 0 < 6.1.4-16.1.4-1
linuxlinux_kernel>= 0 < 6.1.4-16.1.4-1
linuxlinux_kernel>= 3.18.0 < 6.0.166.0.16
linuxlinux_kernel>= 6.1.0 < 6.1.26.1.2
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.