همهٔ گزارش‌ها
متوسط

kernel: sched/mmcid: Prevent CID stalls due to concurrent forks

متن اصلی

نسخه‌های متأثر

نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده

بهره‌برداری

CVE-2026-43418

احتمال بهره‌برداری در ۳۰ روز آینده: 0.11%

FIRST EPSS · ۱۴۰۵/۰۸/۲۹

شرح آسیب‌پذیری

In the Linux kernel, the following vulnerability has been resolved: sched/mmcid: Prevent CID stalls due to concurrent forks A newly forked task is accounted as MMCID user before the task is visible in the process' thread list and the global task list. This creates the following problem: CPU1CPU2 fork() sched_mm_cid_fork(tnew1) tnew1->mm.mm_cid_users++; tnew1->mm_cid.cid = getcid() -> preemption fork() sched_mm_cid_fork(tnew2) tnew2->mm.mm_cid_users++; // Reaches the per CPU threshold mm_cid_fixup_tasks_to_cpus() for_each_other(current, p) .... As tnew1 is not visible yet, this fails to fix up the already allocated CID of tnew1. As a consequence a subsequent schedule in might fail to acquire a (transitional) CID and the machine stalls. Move the invocation of sched_mm_cid_fork() after the new task becomes visible in the thread and the task list to prevent this. This also makes it symmetrical vs. exit() where the task is removed as CID user before the task is removed from the thread and task lists.

A flaw was found in the Linux kernel's sched/mmcid component. When new tasks are created concurrently, a race condition can occur where a task is accounted as a Memory Management Context ID (MMCID) user before it is fully registered in the system's task lists. This can lead to an incorrect allocation of Context IDentifiers (CIDs). As a result, the system may fail to acquire a necessary CID, causing the machine to stall and resulting in a Denial of Service (DoS).