https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 23:06:44 +0000 https://vulnerability.circl.lu/vuln/cve-2026-98015 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put</p> <p>In mlx5_eswitch_termtbl_put(), the zero-ref cleanup check reads tt-&gt;ref_count after termtbl_mutex has been released. Two concurrent callers on the same mlx5_termtbl_handle race: one decrements ref_count to zero, removes the hash entry, and calls kfree(tt) while the other has already dropped the mutex and is about to evaluate if (!tt-&gt;ref_count), producing a use-after-free.</p> <p>Fix this by capturing the result of the decrement into a stack-local last variable before dropping the mutex. The cleanup decision is now made entirely under termtbl_mutex, and tt is not touched after kfree.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put</p> <p>In mlx5_eswitch_termtbl_put(), the zero-ref cleanup check reads tt-&gt;ref_count after termtbl_mutex has been released. Two concurrent callers on the same mlx5_termtbl_handle race: one decrements ref_count to zero, removes the hash entry, and calls kfree(tt) while the other has already dropped the mutex and is about to evaluate if (!tt-&gt;ref_count), producing a use-after-free.</p> <p>Fix this by capturing the result of the decrement into a stack-local last variable before dropping the mutex. The cleanup decision is now made entirely under termtbl_mutex, and tt is not touched after kfree.</p> https://vulnerability.circl.lu/vuln/cve-2026-98015