In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix mlx5e_priv_init() cleanup flow The Linux kernel CVE team has assigned CVE-2024-35959 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024052019-CVE-2024-35959-6e06@gregkh/T
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 2281924]
Besides the kernel messages on lockdep-enabled (i.e. *-debug) kernels in the driver's initialization failure path, I don't see any other possible consequences. There is no vulnerability.
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2024-35959 is: CHECK Maybe valid. Check manually. with impact LOW (that is an approximation based on flags REMOTE LOCK INIT WARNONLY NETWORK ; these flags parsed automatically based on patch data). Such automatic check happens only for Low/Moderates (and only when not from reporter, but parsing already existing CVE). Highs always checked manually (I check it myself and then we check it again in Remediation team). In rare cases some of the Moderates could be increased to High later.
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:4211 https://access.redhat.com/errata/RHSA-2024:4211
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:4352 https://access.redhat.com/errata/RHSA-2024:4352
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:9315 https://access.redhat.com/errata/RHSA-2024:9315