{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-43418 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-43418 is a medium-severity vulnerability in Linux kernel, published on 8 May 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-43418 and fix it if it is affected.\n\nWhat it is: CVE-2026-43418 is a medium-severity vulnerability in Linux kernel, published on 8 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-43418 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-43418/ (Markdown: https://insights.sbomify.com/CVE-2026-43418/index.md)","id":"CVE-2026-43418","markdown":"https://insights.sbomify.com/CVE-2026-43418/index.md","name":"CVE-2026-43418","record":{"aliases":["DEBIAN-CVE-2026-43418","GHSA-5r8w-mfmh-79h7","UBUNTU-CVE-2026-43418"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel's MM CID handling during concurrent forks can cause a system stall, leading to denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"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' 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"sched/mmcid: Prevent CID stalls due to concurrent forks","id":"CVE-2026-43418","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"ceph: fix memory leaks in ceph_mdsc_build_path()","id":"CVE-2026-43419"},"packages":[],"prev":{"headline":"sched/mmcid: Handle vfork()/CLONE_VM correctly","id":"CVE-2026-43417"},"products":["Linux"],"published":"2026-05-08","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A race condition in the Linux kernel's MM CID handling during concurrent forks can cause a system stall, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-43418/"}