memory: pl353-smc: Fix refcount leak bug in pl353_smc_probe()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ fee10bd2267868f2a3e7ba008ef7665aac5e4412 · < 61b3c876c1cbdb1efd1f52a1f348580e6e14efb6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
memory: pl353-smc: Fix refcount leak bug in pl353_smc_probe()
The break of for_each_available_child_of_node() needs a corresponding of_node_put() when the reference 'child' is not used anymore. Here we do not need to call of_node_put() in fail path as '!match' means no break.
While the of_platform_device_create() will created a new reference by 'child' but it has considered the refcounting.
From the CVE record · Linux
The Linux kernel’s pl353_smc_probe() can leak a device-tree node reference when it exits a child-node loop. The input does not specify how an attacker could trigger the issue or whether access, authentication, or user interaction is required.
Teams running the Linux kernel should check whether their kernel includes the affected pl353-smc code; affected versions are not specified.