{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90222 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90222 is an use after free vulnerability in Linux, published on 17 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-90222 and fix it if it is affected.\n\nWhat it is: CVE-2026-90222 is an use after free vulnerability in Linux, published on 17 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-90222 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-90222/ (Markdown: https://insights.sbomify.com/CVE-2026-90222/index.md)","id":"CVE-2026-90222","markdown":"https://insights.sbomify.com/CVE-2026-90222/index.md","name":"CVE-2026-90222","record":{"aliases":["AZL-102693","BELL-CVE-2026-90222","DEBIAN-CVE-2026-90222","GHSA-36pr-4p99-6568","UBUNTU-CVE-2026-90222"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NFC driver","requires_auth":"none","summary":"A race condition in the Linux kernel NFC driver allows a use-after-free, potentially causing system crashes or arbitrary code execution via local access.","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\nnfc: pn533: hold a reference to the request skb during send_frame\n\n__pn533_send_async() publishes the command and then calls\ndev-\u003ephy_ops-\u003esend_frame(). Once dev-\u003ecmd is set, an incoming frame\ncan be matched to this command: the I2C threaded IRQ runs\npn533_recv_frame(), which queues cmd_complete_work, and\npn533_send_async_complete() frees cmd-\u003ereq with consume_skb().\n\nOn the I2C transport, pn533_i2c_send_frame() still dereferences the same\nskb after i2c_master_send() returns, so a completion that races the\nsend can free the skb while the transport is still using it.\n\nThe request skb is owned by the command object and may be freed by\ncommand completion at any time after dev-\u003ecmd is published, so the\ntransport send path must not assume it stays alive. Hold a temporary\nreference to the request skb across the send_frame() call so the\ntransport always sees a live skb even if completion races the send.\nAdd a pn533_send_cmd_frame() helper and use it from all three send\npaths.","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":"nfc: pn533: hold a reference to the request skb during send_frame","id":"CVE-2026-90222","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"nfc: llcp: bound SNL TLV parsing to the skb and add length checks","id":"CVE-2026-90223"},"packages":[],"prev":{"headline":"nfc: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing","id":"CVE-2026-90221"},"products":["Linux"],"published":"2026-09-17","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 NFC driver allows a use-after-free, potentially causing system crashes or arbitrary code execution via local access.","url":"https://insights.sbomify.com/CVE-2026-90222/"}