CVE-2022-50616

/// Technical description

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 it

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References