{"id":21674,"date":"2026-09-12T04:31:30","date_gmt":"2026-09-11T20:31:30","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-89752"},"modified":"2026-09-12T04:31:30","modified_gmt":"2026-09-11T20:31:30","slug":"cve-2026-89752","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-89752","title":{"rendered":"CVE-2026-89752 &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nmm: memcg: stop recla"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>mm: memcg: stop reclaim when a limit update is superseded<\/p>\n<p>kernfs serializes file operations only per open file, so separate open<br \/>\nfiles can update the same memory.high or memory.max file concurrently.<br \/>\nBoth handlers store the new limit before synchronous reclaim, but continue<br \/>\nto use the writer&#8217;s local target in the reclaim loop.  If another writer<br \/>\nraises or removes the limit, the first writer can continue reclaiming<br \/>\ntoward a stale target.<\/p>\n<p>For memory.max, this can leave the writer looping indefinitely once<br \/>\nreclaim retries are exhausted.  The OOM path sees sufficient margin under<br \/>\nthe current limit and returns true without killing, while the writer still<br \/>\ncompares usage against its stale target and records another OOM event.<\/p>\n<p>Check the current limit at the start of each reclaim iteration and stop if<br \/>\nit no longer matches the writer&#8217;s target.<\/p>\n<p>Reproducer:<\/p>\n<p>Populate a cgroup with anonymous memory and disable swapping.  Lower<br \/>\nmemory.max from one open file, then restore it to &#8220;max&#8221; through another<br \/>\nopen file after the new limit becomes visible.<\/p>\n<p>Without the patch, the first writer remains blocked and repeatedly<br \/>\nincrements the OOM event counter.  With the patch, it returns normally.<\/p>\n<p>This was not motivated by a reported production workload.  We found it<br \/>\nthrough automated randomized testing for our cgroup observability work<br \/>\nand reduced it to the reproducer above.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>mm: memcg: stop reclaim when a limit update is superseded<\/p>\n<p>kernfs serializes file operations only per open file, so separate open<br \/>\nf<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-21674","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/21674","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=21674"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=21674"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=21674"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}