{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98481 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98481 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98481 and fix it if it is affected.\n\nWhat it is: CVE-2026-98481 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98481 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-98481/ (Markdown: https://insights.sbomify.com/CVE-2026-98481/index.md)","id":"CVE-2026-98481","markdown":"https://insights.sbomify.com/CVE-2026-98481/index.md","name":"CVE-2026-98481","record":{"aliases":["AZL-108668","BELL-CVE-2026-98481","DEBIAN-CVE-2026-98481","GHSA-76wj-ccjf-8q4p","UBUNTU-CVE-2026-98481"],"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 driver","requires_auth":"none","summary":"A malicious NFC device can trigger an out-of-bounds read in the Linux kernel port100 driver by declaring a frame length larger than the actual received data.","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: port100: reject frames whose declared length exceeds the received data\n\nport100_recv_response() passes the URB transfer buffer to\nport100_rx_frame_is_valid(), which checksums le16_to_cpu(frame-\u003edatalen)\nbytes of frame-\u003edata. datalen is a 16-bit field supplied by the device\nand is never checked against the number of bytes actually received\n(urb-\u003eactual_length), so a device reporting a datalen larger than the\nreceived frame makes port100_data_checksum() read out of bounds past the\ntransfer buffer.\n\nReject a response whose declared frame size does not fit the received\nlength before validating it.\n\nFound by 0sec (https://0sec.ai) using automated source analysis; the\nmissing bound is evident from source. Compile-tested.","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: port100: reject frames whose declared length exceeds the received data","id":"CVE-2026-98481","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: llcp: drop truncated I/RR/RNR PDUs in nfc_llcp_recv_hdlc()","id":"CVE-2026-98482"},"packages":[],"prev":{"headline":"nfc: trf7970a: power down on startup RX gain failure","id":"CVE-2026-98480"},"products":["Linux"],"published":"2026-10-18","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 device can trigger an out-of-bounds read in the Linux kernel port100 driver by declaring a frame length larger than the actual received data.","url":"https://insights.sbomify.com/CVE-2026-98481/"}