ieee802154: ca8210: Fix a potential UAF in ca8210_probe
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ded845a781a578dfb0b5b2c138e5a067aa3b1242 · < 217efe32a45249eb07dcd7197e8403de98345e66| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ieee802154: ca8210: Fix a potential UAF in ca8210_probe
If of_clk_add_provider() fails in ca8210_register_ext_clock(), it calls clk_unregister() to release priv->clk and returns an error. However, the caller ca8210_probe() then calls ca8210_remove(), where priv->clk is freed again in ca8210_unregister_ext_clock(). In this case, a use-after-free may happen in the second time we call clk_unregister().
Fix this by removing the first clk_unregister(). Also, priv->clk could be an error code on failure of clk_register_fixed_rate(). Use IS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().
From the CVE record · Linux
The Linux kernel’s ca8210 driver can unregister a clock twice during probe cleanup if clock-provider registration fails, potentially causing a use-after-free. The input does not establish whether an attacker can trigger this failure or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the ca8210 driver should check their versions; affected versions are not specified.