CVE-2026-80592

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> samples/damon/mtier: fail early if address range parameters are invalid<br /> <br /> The comment on top of `struct damon_region` clearly says that<br /> <br /> For any use case, @ar should be non-zero positive size.<br /> <br /> which is now verified in damon_verify_new_region() if the kernel is built<br /> with DAMON_DEBUG_SANITY.<br /> <br /> The WARN_ONCE() can be triggered if the mtier sample module is enabled<br /> before node{0,1}_{start,end}_addr have been properly initialized, which is<br /> obviously not good.<br /> <br /> ------------[ cut here ]------------<br /> start 0 &gt;= end 0<br /> WARNING: mm/damon/core.c:217 at damon_new_region+0xf4/0x118, CPU#59: bash/341468<br /> Call trace:<br /> damon_new_region+0xf4/0x118 (P)<br /> damon_set_regions+0xfc/0x3c0<br /> damon_sample_mtier_build_ctx+0xe8/0x3a8<br /> damon_sample_mtier_start+0x1c/0x90<br /> damon_sample_mtier_enable_store+0x98/0xb0<br /> param_attr_store+0xb4/0x128<br /> module_attr_store+0x2c/0x50<br /> sysfs_kf_write+0x58/0x90<br /> kernfs_fop_write_iter+0x16c/0x238<br /> vfs_write+0x2c0/0x370<br /> ksys_write+0x74/0x118<br /> __arm64_sys_write+0x24/0x38<br /> invoke_syscall+0xa8/0x118<br /> el0_svc_common.constprop.0+0x48/0xf0<br /> do_el0_svc+0x24/0x38<br /> el0_svc+0x54/0x370<br /> el0t_64_sync_handler+0xa0/0xe8<br /> el0t_64_sync+0x1ac/0x1b0<br /> ---[ end trace 0000000000000000 ]---<br /> <br /> Note that the same issue can happen if detect_node_addresses is true, and<br /> node 0 or 1 is memoryless. Fix it together by checking the validity of<br /> parameters right before damon_new_region() and fail early if they&amp;#39;re<br /> invalid.