{"id":41070,"date":"2026-10-19T00:32:01","date_gmt":"2026-10-18T16:32:01","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-98598"},"modified":"2026-10-19T00:32:01","modified_gmt":"2026-10-18T16:32:01","slug":"cve-2026-98598","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-98598","title":{"rendered":"CVE-2026-98598 &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Prevent rt6_ins"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>ipv6: Prevent rt6_insert_exception() for dying fib6_info.<\/p>\n<p>Before the cited commit, fib6_nh_flush_exceptions() always set<br \/>\nfrom-&gt;exception_bucket_flushed = 1 under rt6_exception_lock to<br \/>\nprevent rt6_insert_exception() from inserting a new exception<br \/>\nfor a dying fib6_info.<\/p>\n<p>The flag was replaced with the FIB6_EXCEPTION_BUCKET_FLUSHED<br \/>\nbit stored in nh-&gt;rt6i_exception_bucket.<\/p>\n<p>The problem is that now the bit is only set when the bucket<br \/>\nis not NULL and fib6_nh_flush_exceptions() is called from<br \/>\nfib6_nh_release() after fib6_ref has already reached zero.<\/p>\n<p>If rt6_insert_exception() is called while the target fib6_info<br \/>\nis being removed via fib6_purge_rt(), a new exception could be<br \/>\ncreated successfully because rt6_flush_exceptions() no longer<br \/>\nsets the bit.<\/p>\n<p>This creates a reference cycle between the fib6_info and the<br \/>\nexception route, leaking the fib6_info, its nexthop device,<br \/>\nand all per-CPU routes in fib6_nh-&gt;rt6i_pcpu, which stalls netdev<br \/>\nunregistration.<\/p>\n<p>[   34.680602] unregister_netdevice: waiting for gre6 to become free. Usage count = 68<br \/>\n[   44.920675] unregister_netdevice: waiting for gre6 to become free. Usage count = 68<br \/>\n[   55.176582] unregister_netdevice: waiting for gre6 to become free. Usage count = 68<\/p>\n<p>Let&#8217;s call fib6_drop_pcpu_from() before rt6_flush_exceptions(),<br \/>\nto set fib6_destroying before rt6_exception_lock, and check<br \/>\nf6i-&gt;fib6_destroying in rt6_insert_exception().<\/p>\n<p>Note that FIB6_EXCEPTION_BUCKET_FLUSHED logic is dead and<br \/>\nwe can clean it up in net-next.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>ipv6: Prevent rt6_insert_exception() for dying fib6_info.<\/p>\n<p>Before the cited commit, fib6_nh_flush_exceptions() always set<br \/>\nfrom-&gt;exc<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-41070","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/41070","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=41070"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=41070"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=41070"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}