Dinghao Liu

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to a potential double-free in the `fs any create groups` function. When `kcalloc()` for `ft->g` succeeds but `kvzalloc()` for `in` fails, `fs any create groups()` will free `ft->g`. However, its caller `fs any create table()` will free `ft->g` again through calling `mlx5e destroy flow table()`, which will lead to a double-free. This can be fixed by setting `ft->g` to `NULL` in `fs any create groups()`. The vulnerability may allow an attacker to cause a denial of service. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to a memory leak in the `iio device register sysfs()` function. When `iio device register sysfs group()` fails, it does not free `iio dev opaque->chan attr group.attrs`, potentially leading to a memory leak. This could allow an attacker to cause a denial of service. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to a potential use-after-free (UAF) in the `ca8210 probe` function. 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()`. This can lead to a use-after-free when `clk unregister()` is called the second time. The fix involves removing the first `clk unregister()` call and using `IS ERR OR NULL` to catch the case where `priv->clk` is an error code on failure of `clk register fixed rate()`. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.