net/mlx4_en: Fix an use-after-free bug in mlx4_en_try_alloc_resources()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ec25bc04ed8e12947738468cbe2191f1529f9e39 · < addad7643142f500080417dd7272f49b7a185570| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net/mlx4_en: Fix an use-after-free bug in mlx4_en_try_alloc_resources()
In mlx4_en_try_alloc_resources(), mlx4_en_copy_priv() is called and tmp->tx_cq will be freed on the error path of mlx4_en_copy_priv(). After that mlx4_en_alloc_resources() is called and there is a dereference of &tmp->tx_cq[t][i] in mlx4_en_alloc_resources(), which could lead to a use after free problem on failure of mlx4_en_copy_priv().
Fix this bug by adding a check of mlx4_en_copy_priv()
This bug was found by a static analyzer. The analysis employs differential checking to identify inconsistent security operations (e.g., checks or kfrees) between two code paths and confirms that the inconsistent operations are not recovered in the current function or the callers, so they constitute bugs.
Note that, as a bug found by static analysis, it can be a false positive or hard to trigger. Multiple researchers have cross-reviewed the bug.
Builds with CONFIG_MLX4_EN=m show no new warnings, and our static analyzer no longer warns about this code.
From the CVE record · Linux
The Linux kernel's net/mlx4_en driver may use freed memory if mlx4_en_copy_priv() fails and resource allocation continues. This bug was found by static analysis and may be hard to trigger or a false positive; the input does not establish attacker capabilities, access requirements, or user interaction.
Engineers running Linux kernels with the net/mlx4_en driver should check their builds; affected versions are not specified.