{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80803 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80803 is a memory corruption vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-80803 and fix it if it is affected.\n\nWhat it is: CVE-2026-80803 is a memory corruption vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-80803 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-80803/ (Markdown: https://insights.sbomify.com/CVE-2026-80803/index.md)","id":"CVE-2026-80803","markdown":"https://insights.sbomify.com/CVE-2026-80803/index.md","name":"CVE-2026-80803","record":{"aliases":["AZL-99399","BELL-CVE-2026-80803","DEBIAN-CVE-2026-80803","GHSA-p57f-2f7j-w542","UBUNTU-CVE-2026-80803"],"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 NFC","requires_auth":"none","summary":"A malicious NFC-F device can trigger a stack buffer overflow in the Linux kernel NFC driver, potentially leading to code execution or system crash.","user_interaction":"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: digital: clamp SENSF_RES length to the destination buffer\n\ndigital_in_recv_sensf_res() memcpy()s resp-\u003elen bytes from a remote\nNFC-F device response into the NFC_SENSF_RES_MAXSIZE-byte target.sensf_res\nfield without an upper-bound check. A nearby malicious NFC-F device can\nsend an oversized SENSF_RES response to overflow the stack-local struct\nnfc_target.\n\nClamp resp-\u003elen to NFC_SENSF_RES_MAXSIZE before the copy.\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: digital: clamp SENSF_RES length to the destination buffer","id":"CVE-2026-80803","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"xfs: restore nofs context unconditionally in xfs_trans_roll","id":"CVE-2026-80804"},"packages":[],"prev":{"headline":"nfc: fdp: bound the device-reported read length and fix an skb leak","id":"CVE-2026-80802"},"products":["Linux"],"published":"2026-09-04","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 malicious NFC-F device can trigger a stack buffer overflow in the Linux kernel NFC driver, potentially leading to code execution or system crash.","url":"https://insights.sbomify.com/CVE-2026-80803/"}