{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90226 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90226 is a 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-90226 and fix it if it is affected.\n\nWhat it is: CVE-2026-90226 is a 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-90226 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-90226/ (Markdown: https://insights.sbomify.com/CVE-2026-90226/index.md)","id":"CVE-2026-90226","markdown":"https://insights.sbomify.com/CVE-2026-90226/index.md","name":"CVE-2026-90226","record":{"aliases":["AZL-102093","BELL-CVE-2026-90226","DEBIAN-CVE-2026-90226","GHSA-phjm-5cmf-7w3f","UBUNTU-CVE-2026-90226"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NFC","requires_auth":"low_privilege","summary":"A local attacker can trigger a buffer overflow in the Linux kernel NFC LLCP module via getsockopt, potentially leading to privilege escalation or code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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: llcp: avoid userspace overflow on invalid optlen\n\nnfc_llcp_getsockopt() casts optval to (u32 __user *) for put_user(), so\nthe kernel always stores 4 bytes regardless of the caller-supplied\noptlen. The existing min_t(u32, len, sizeof(u32)) only clamps the length\nreported back to userspace; it does not constrain the store. A call with\noptlen \u003c 4 therefore writes past the user buffer, violating the\ngetsockopt(2) contract for all five supported optnames.\n\nReject any call with optlen \u003c sizeof(u32) up front. 'len' is int, so a\nplain size comparison would promote a negative optlen to size_t and slip\npast the check; an explicit 'len \u003c 0' test is added first to catch\nnegative values before the size compare.","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: avoid userspace overflow on invalid optlen","id":"CVE-2026-90226","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":"nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed()","id":"CVE-2026-90227"},"packages":[],"prev":{"headline":"nfc: llcp: read llcp_sock-\u003elocal under the socket lock in getsockopt","id":"CVE-2026-90225"},"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 a buffer overflow in the Linux kernel NFC LLCP module via getsockopt, potentially leading to privilege escalation or code execution.","url":"https://insights.sbomify.com/CVE-2026-90226/"}