FKIE_CVE-2026-43418
Vulnerability from fkie_nvd - Published: 2026-05-08 15:16 - Updated: 2026-05-12 14:10
Severity
Summary
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.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsched/mmcid: Prevent CID stalls due to concurrent forks\n\nA newly forked task is accounted as MMCID user before the task is visible\nin the process\u0027 thread list and the global task list. This creates the\nfollowing problem:\n\n CPU1\t\t\tCPU2\n fork()\n sched_mm_cid_fork(tnew1)\n tnew1-\u003emm.mm_cid_users++;\n tnew1-\u003emm_cid.cid = getcid()\n-\u003e preemption\n\t\t\tfork()\n\t\t\t sched_mm_cid_fork(tnew2)\n\t\t\t tnew2-\u003emm.mm_cid_users++;\n // Reaches the per CPU threshold\n\t\t\t mm_cid_fixup_tasks_to_cpus()\n\t\t\t for_each_other(current, p)\n\t\t\t ....\n\nAs tnew1 is not visible yet, this fails to fix up the already allocated CID\nof tnew1. As a consequence a subsequent schedule in might fail to acquire a\n(transitional) CID and the machine stalls.\n\nMove the invocation of sched_mm_cid_fork() after the new task becomes\nvisible in the thread and the task list to prevent this.\n\nThis also makes it symmetrical vs. exit() where the task is removed as CID\nuser before the task is removed from the thread and task lists."
}
],
"id": "CVE-2026-43418",
"lastModified": "2026-05-12T14:10:27.343",
"metrics": {},
"published": "2026-05-08T15:16:53.803",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/b2e48c429ec54715d16fefa719dd2fbded2e65be"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/f0189d49282e0458f3a737bd486c1ec048148f66"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Undergoing Analysis"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…