In the Linux kernel, the following vulnerability has been resolved:
net/mlx5e: Fix CT entry update leaks of modify header context
The cited commit allocates a new modify header to replace the old
one when updating CT entry. But if failed to allocate a new one, eg.
exceed the max number firmware can support, modify header will be
an error pointer that will trigger a panic when deallocating it. And
the old modify header point is copied to old attr. When the old
attr is freed, the old modify header is lost.
Fix it by restoring the old attr to attr when failed to allocate a
new modify header context. So when the CT entry is freed, the right
modify header context will be freed. And the panic of accessing
error pointer is also fixed.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 24.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux-azure | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux-gcp | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux-gke | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-hwe-6.8 | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux-ibm | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux-intel | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux-lowlatency | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-lowlatency-hwe-6.8 | < any | UNKNOWN |
git.kernel.org/linus/025f2b85a5e5a46df14ecf162c3c80a957a36d0b (6.11-rc2)
git.kernel.org/stable/c/025f2b85a5e5a46df14ecf162c3c80a957a36d0b
git.kernel.org/stable/c/89064d09c56b44c668509bf793c410484f63f5ad
git.kernel.org/stable/c/daab2cc17b6b6ab158566bba037e9551fd432b59
launchpad.net/bugs/cve/CVE-2024-43864
nvd.nist.gov/vuln/detail/CVE-2024-43864
security-tracker.debian.org/tracker/CVE-2024-43864
www.cve.org/CVERecord?id=CVE-2024-43864