{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90223 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90223 is a high-severity memory corruption 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-90223 and fix it if it is affected.\n\nWhat it is: CVE-2026-90223 is a high-severity memory corruption 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-90223 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-90223/ (Markdown: https://insights.sbomify.com/CVE-2026-90223/index.md)","id":"CVE-2026-90223","markdown":"https://insights.sbomify.com/CVE-2026-90223/index.md","name":"CVE-2026-90223","record":{"aliases":["AZL-102746","BELL-CVE-2026-90223","DEBIAN-CVE-2026-90223","GHSA-jxpm-782w-87ph","UBUNTU-CVE-2026-90223"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NFC","requires_auth":"none","summary":"A nearby NFC device can trigger out-of-bounds reads in the Linux kernel LLCP parser, potentially causing crashes or leaking memory.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnfc: llcp: bound SNL TLV parsing to the skb and add length checks\n\nnfc_llcp_recv_snl() walked the SNL TLV list using a u16 offset/length\npair derived from skb-\u003elen, without bounding reads to the actual skb\ndata. Three problems followed:\n\n  - For a short frame (skb-\u003elen \u003c LLCP_HEADER_SIZE), tlv_len underflowed.\n  - The per-TLV header (type, length) was read without checking that two\n    bytes remained.\n  - A declared TLV length could run past the end of the buffer, and an\n    SDREQ with length == 0 made \"service_name_len = length - 1\" underflow\n    (size_t), driving an out-of-bounds read in the following strncmp() /\n    nfc_llcp_sock_from_sn(). The SDRES case likewise read tlv[2]/tlv[3]\n    without a length check.\n\nA nearby NFC device can reach this without authentication; LLCP link\nactivation happens automatically after NFC-DEP.\n\nWalk the TLV list by pointer, bounded by skb_tail_pointer() over the\nlinear skb data, and validate each TLV declared length before use. Add\nexplicit length checks for SDREQ (\u003e= 1) and SDRES (exactly 2).\n\nFound by 0sec automated security-research tooling (https://0sec.ai).","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: llcp: bound SNL TLV parsing to the skb and add length checks","id":"CVE-2026-90223","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"nfc: nci: fix double completion race in nci_data_exchange_complete","id":"CVE-2026-90224"},"packages":[],"prev":{"headline":"nfc: pn533: hold a reference to the request skb during send_frame","id":"CVE-2026-90222"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A nearby NFC device can trigger out-of-bounds reads in the Linux kernel LLCP parser, potentially causing crashes or leaking memory.","url":"https://insights.sbomify.com/CVE-2026-90223/"}