{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98018 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98018 is an use after free vulnerability in Linux, published on 25 Sep 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-98018 and fix it if it is affected.\n\nWhat it is: CVE-2026-98018 is an use after free vulnerability in Linux, published on 25 Sep 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-98018 in the wild and no public exploit code.\n\nAffected product: Linux. 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-98018/ (Markdown: https://insights.sbomify.com/CVE-2026-98018/index.md)","id":"CVE-2026-98018","markdown":"https://insights.sbomify.com/CVE-2026-98018/index.md","name":"CVE-2026-98018","record":{"aliases":["BELL-CVE-2026-98018","DEBIAN-CVE-2026-98018","GHSA-wc27-x2j9-p8cq","UBUNTU-CVE-2026-98018"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in the Linux kernel MCTP I3C driver allows use-after-free, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: mctp: i3c: serialize probe with bus removal\n\nmctp_i3c_probe() drops busdevs_lock after finding the matching bus. A\nconcurrent I3C_NOTIFY_BUS_REMOVE can then unregister and free the bus\nnetdev before probe passes its private data to mctp_i3c_add_device().\nThe latter consequently adds a list node through a freed mbus pointer.\n\nKeep busdevs_lock held until the device has been added. This also\nsatisfies the __must_hold annotation on mctp_i3c_add_device().","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":"net: mctp: i3c: serialize probe with bus removal","id":"CVE-2026-98018","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"bpf: mark a NULL call argument precise","id":"CVE-2026-98019"},"packages":[],"prev":{"headline":"net/sched: defer qdisc freeing after failed creation","id":"CVE-2026-98017"},"products":["Linux"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel MCTP I3C driver allows use-after-free, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2026-98018/"}