{"id":25852,"date":"2026-09-18T04:31:59","date_gmt":"2026-09-17T20:31:59","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-92483"},"modified":"2026-09-18T04:31:59","modified_gmt":"2026-09-17T20:31:59","slug":"cve-2026-92483","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-92483","title":{"rendered":"CVE-2026-92483 &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nliveupdate: Remember"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>liveupdate: Remember FLB retrieve() status<\/p>\n<p>LUO keeps track of successful retrieve attempts on an FLB. It does so<br \/>\nto avoid multiple retrievals of the same FLB. Multiple retrievals cause<br \/>\nproblems because once the FLB is retrieved, the serialized data<br \/>\nstructures are likely freed and the FLB is likely in a very different<br \/>\nstate from what the code expects.<\/p>\n<p>All this works well when retrieve succeeds. When it fails,<br \/>\nluo_flb_retrieve_one() returns the error immediately, without ever<br \/>\nstoring anywhere that a retrieve was attempted or what its error code<br \/>\nwas. If the user attempts to retrieve another file registered with the<br \/>\nsame FLB, LUO will attempt to call the FLB&#8217;s retrieve() callback again.<\/p>\n<p>The retry is problematic for much of the same reasons listed above. The<br \/>\nFLB is likely in a very different state than what the retrieve logic<br \/>\nnormally expects (e.g. some KHO pages may have already been restored and<br \/>\nfreed).<\/p>\n<p>There is no sane way of attempting the retrieve again. Remember the<br \/>\nerror retrieve returned and directly return it on a retry.<\/p>\n<p>This is done by changing the retrieved bool to a retrieve_status<br \/>\ninteger. A value of 0 means retrieve was never attempted, a positive<br \/>\nvalue means it succeeded, and a negative value means it failed and the<br \/>\nerror code is the value.<\/p>\n<p>This is similar to commit f85b1c6af5bc (&#8220;liveupdate: luo_file: remember<br \/>\nretrieve() status&#8221;) which did the same for LUO files.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>liveupdate: Remember FLB retrieve() status<\/p>\n<p>LUO keeps track of successful retrieve attempts on an FLB. It does so<br \/>\nto avoid multiple<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-25852","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/25852","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=25852"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=25852"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=25852"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}