{"id":3391,"date":"2026-09-04T04:59:40","date_gmt":"2026-09-03T20:59:40","guid":{"rendered":"https:\/\/www.54iter.cn\/?p=3391"},"modified":"2026-09-04T04:59:40","modified_gmt":"2026-09-03T20:59:40","slug":"cve-2026-80739","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-80739","title":{"rendered":"CVE-2026-80739 &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nnet\/mlx5e: TC, Check"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>net\/mlx5e: TC, Check if flow is PEER before acquiring devcom lock<\/p>\n<p>In case __mlx5e_add_fdb_flow() fails in lower levels, the flow is<br \/>\ndeleted via mlx5e_tc_del_flow(), and mlx5e_tc_del_flow() is acquiring<br \/>\nESW devcom lock without condition. In addition, in case of peer_flow,<br \/>\n__mlx5e_add_fdb_flow() is called while holding ESW devcom comp lock.<br \/>\nThis results in an AA deadlock.<\/p>\n<p>To fix this, introduce a new PEER flag that is set on flows created as<br \/>\npeer flows (the duplicate flows on peer devices), and check it in<br \/>\nmlx5e_tc_del_flow() before acquiring ESW devcom lock.<\/p>\n<p>Lockdep splat:<br \/>\n============================================<br \/>\nWARNING: possible recursive locking detected<br \/>\n============================================<br \/>\n Possible unsafe locking scenario:<br \/>\n       CPU0<br \/>\n       &#8212;-<br \/>\n  lock(&amp;comp-&gt;lock_key#2);<br \/>\n  lock(&amp;comp-&gt;lock_key#2);<br \/>\n *** DEADLOCK ***<br \/>\nCall Trace:<\/p>\n<p> dump_stack_lvl+0x69\/0xa0<br \/>\n print_deadlock_bug.cold+0xbd\/0xca<br \/>\n __lock_acquire+0x1671\/0x2ec0<br \/>\n lock_acquire+0x10e\/0x2e0<br \/>\n down_read+0x95\/0x430<br \/>\n mlx5_devcom_for_each_peer_begin+0x4e\/0xe0 [mlx5_core]<br \/>\n mlx5e_tc_del_flow+0x11d\/0xa70 [mlx5_core]<br \/>\n mlx5e_flow_put+0x99\/0x100 [mlx5_core]<br \/>\n __mlx5e_add_fdb_flow+0x409\/0xf00 [mlx5_core]<br \/>\n mlx5e_configure_flower+0x2a86\/0x4100 [mlx5_core]<br \/>\n mlx5e_rep_setup_tc_cls_flower+0x12f\/0x1b0 [mlx5_core]<br \/>\n mlx5e_rep_setup_tc_cb+0x153\/0x750 [mlx5_core]<br \/>\n tc_setup_cb_add+0x1dc\/0x470<br \/>\n fl_change+0x2f4d\/0x626d [cls_flower]<br \/>\n tc_new_tfilter+0x79b\/0x2310<br \/>\n rtnetlink_rcv_msg+0x778\/0xad0<br \/>\n do_syscall_64+0x70\/0x960<br \/>\n entry_SYSCALL_64_after_hwframe+0x4b\/0x53<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>net\/mlx5e: TC, Check if flow is PEER before acquiring devcom lock<\/p>\n<p>In case __mlx5e_add_fdb_flow() fails in lower levels, the flow i<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-3391","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/3391","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3391"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3391"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3391"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}