regulator: core: Use different devices for resource allocation and DT lookup
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 8f3cbcd6b440032ebc7f7d48a1689dcc70a4eb98, Kernel b0f25ca1ff9be7abd1679ae7e59a8f25dbffe67a and Kernel cb29811d989bcb7ea81ca111c4b13878b344e086.
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/20221128143601.1698148-1-yangyingliang@huawei.com/ 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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.18, >=a0c7b164ad115ec0556dc0904ee2218cbc5cedfa <8f3cbcd6b440032ebc7f7d48a1689dcc70a4eb98, >=a0c7b164ad115ec0556dc0904ee2218cbc5cedfa <b0f25ca1ff9be7abd1679ae7e59a8f25dbffe67a, >=a0c7b164ad115ec0556dc0904ee2218cbc5cedfa <cb29811d989bcb7ea81ca111c4b13878b344e086 | 8f3cbcd6b440032ebc7f7d48a1689dcc70a4eb98, b0f25ca1ff9be7abd1679ae7e59a8f25dbffe67a, cb29811d989bcb7ea81ca111c4b13878b344e086 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket