Vulnerability · Published May 8, 2026 · Assigned by Linux

CVE-2026-43418sched/mmcid: Prevent CID stalls due to concurrent forks

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 1% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.1%top 98.8% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

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: CPU1 CPU2 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux6.19.10-1DEBIAN-CVE-2026-43418
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-43418
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-43418
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-43418

Affected products (as reported)

VendorProductVersions
Linux Linux fbd0e71dc370af73f6b316e4de9eed273dd90340 – before f0189d49282e0458f3a737bd486c1ec048148f66fbd0e71dc370af73f6b316e4de9eed273dd90340 – before b2e48c429ec54715d16fefa719dd2fbded2e65be
Linux Linux 6.19

References