CVE-2026-43418
Last modified
CVE-2026-43418 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.11% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.19, < 6.19.9 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-43418?
How severe is CVE-2026-43418?
How do I fix CVE-2026-43418?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-43412In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43413In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43414In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-43415In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-43416In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43417In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43419In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-4342A security issue was discovered in ingress-nginx where a com…8.8
- CVE-2026-43420In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-43421In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43422Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-43423Rejected reason: This CVE ID has been rejected or withdrawn …
Are you affected by CVE-2026-43418?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
