{"id":33300,"date":"2026-10-06T20:31:43","date_gmt":"2026-10-06T12:31:43","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-98231"},"modified":"2026-10-06T20:31:43","modified_gmt":"2026-10-06T12:31:43","slug":"cve-2026-98231","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-98231","title":{"rendered":"CVE-2026-98231 &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: serialize state"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>xfrm: serialize state GC with device state flush<\/p>\n<p>The deferred-device pass in xfrm_dev_state_flush() finds states under<br \/>\nxfrm_state_dev_gc_lock, but drops the lock before calling<br \/>\nxfrm_dev_state_free() because the driver callback may sleep.  The device<br \/>\nGC list does not hold an xfrm_state reference, so the state GC worker can<br \/>\ndestroy the same state concurrently.<\/p>\n<p>The race can proceed as follows:<\/p>\n<p>  CPU 0                               CPU 1<br \/>\n  find x on the device GC list<br \/>\n  drop xfrm_state_dev_gc_lock<br \/>\n  read x-&gt;xso.dev<br \/>\n                                      xfrm_state_gc_destroy(x)<br \/>\n                                      xfrm_dev_state_free(x)<br \/>\n                                      xfrm_state_free(x)<br \/>\n  continue xfrm_dev_state_free(x)<\/p>\n<p>Both paths can invoke the driver callback and drop the device reference.<br \/>\nCPU 0 can also access the xfrm_state after CPU 1 has freed it.<\/p>\n<p>KASAN reported:<\/p>\n<p>  BUG: KASAN: slab-use-after-free in xfrm_dev_state_free+0x24c\/0x2a0<br \/>\n  Read of size 8 at addr ffff88810bbaa960 by task poc\/102<\/p>\n<p>  Call Trace:<br \/>\n   xfrm_dev_state_free+0x24c\/0x2a0<br \/>\n   xfrm_dev_state_flush+0x353\/0x400<br \/>\n   xfrm_dev_event+0x26d\/0x3a0<br \/>\n   notifier_call_chain+0xc0\/0x280<br \/>\n   __dev_notify_flags+0x169\/0x250<br \/>\n   netif_change_flags+0xe7\/0x160<br \/>\n   dev_change_flags+0x96\/0x220<br \/>\n   devinet_ioctl+0x7f4\/0x1880<\/p>\n<p>  Allocated by task 87:<br \/>\n   xfrm_state_alloc+0x1e\/0x5c0<br \/>\n   xfrm_add_sa+0xe7f\/0x5820<br \/>\n   xfrm_user_rcv_msg+0x4f3\/0x940<\/p>\n<p>  Freed by task 57:<br \/>\n   kmem_cache_free+0xcb\/0x3d0<br \/>\n   xfrm_state_gc_task+0x4a8\/0x650<br \/>\n   process_one_work+0x63a\/0x1070<\/p>\n<p>Serialize xfrm_state destruction against the deferred-device pass with a<br \/>\nmutex.  Keep xfrm_state_dev_gc_lock limited to list operations and retain<br \/>\nthe existing callback and device-reference release ordering.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>xfrm: serialize state GC with device state flush<\/p>\n<p>The deferred-device pass in xfrm_dev_state_flush() finds states under<br \/>\nxfrm_state_<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-33300","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/33300","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=33300"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=33300"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=33300"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}