{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90221 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90221 is a 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-90221 and fix it if it is affected.\n\nWhat it is: CVE-2026-90221 is a 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-90221 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-90221/ (Markdown: https://insights.sbomify.com/CVE-2026-90221/index.md)","id":"CVE-2026-90221","markdown":"https://insights.sbomify.com/CVE-2026-90221/index.md","name":"CVE-2026-90221","record":{"aliases":["AZL-102122","BELL-CVE-2026-90221","DEBIAN-CVE-2026-90221","GHSA-h298-hpmc-3w4v","UBUNTU-CVE-2026-90221"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NFC","requires_auth":"none","summary":"A local attacker can trigger uninitialized memory reads in the Linux kernel NFC subsystem, potentially disclosing sensitive kernel memory contents.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing\n\nnci_core_init_rsp_packet_v1() and nci_core_init_rsp_packet_v2() parse\nthe CORE_INIT_RSP packet without validating that the skb contains\nenough data. A malformed response (e.g. injected via virtual_ncidev)\ncan declare a large num_supported_rf_interfaces while providing\ninsufficient data, causing reads of uninitialized slab memory. This\nis later used in nci_init_complete_req(), triggering a KMSAN\nuninit-value warning.\n\nAdd skb length checks before accessing packet fields:\n- Validate the skb has at least 1 byte for the status field.\n- Validate the skb can hold the fixed-size header before parsing.\n- In v2, bounds-check each variable-length rf_interface entry and its\n  extension parameters within the parsing loop.\n- In v1, verify the skb is large enough for both the variable-length\n  rf_interfaces array and the trailing rsp_2 structure.","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: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing","id":"CVE-2026-90221","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"nfc: pn533: hold a reference to the request skb during send_frame","id":"CVE-2026-90222"},"packages":[],"prev":{"headline":"ALSA: seq: Don't leak the extension cell pointer in the bounce payload","id":"CVE-2026-90220"},"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 local attacker can trigger uninitialized memory reads in the Linux kernel NFC subsystem, potentially disclosing sensitive kernel memory contents.","url":"https://insights.sbomify.com/CVE-2026-90221/"}