{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98575 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98575 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98575 and fix it if it is affected.\n\nWhat it is: CVE-2026-98575 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98575 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-98575/ (Markdown: https://insights.sbomify.com/CVE-2026-98575/index.md)","id":"CVE-2026-98575","markdown":"https://insights.sbomify.com/CVE-2026-98575/index.md","name":"CVE-2026-98575","record":{"aliases":["AZL-108927","BELL-CVE-2026-98575","DEBIAN-CVE-2026-98575","GHSA-68mj-7vm5-9gjg","UBUNTU-CVE-2026-98575"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"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 pn533 driver, potentially leaking memory or causing a 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: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()\n\nframe-\u003eccid.datalen is read directly from the USB response frame\nand used, unchecked, as an index into frame-\u003edata[]. A malicious or\nmalfunctioning device can set this field to an arbitrary value,\ncausing the driver to read far outside the received buffer.\n\nBound ccid.datalen against the maximum possible ACR122 frame size\nbefore using it. This replaces the existing datalen == 0 check,\nsince datalen \u003c 2 already covers that case and additionally\nrejects datalen == 1, which would still underflow the\n\"datalen - 2\" offset used below.","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: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()","id":"CVE-2026-98575","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: fix slab-out-of-bounds reads when logging service names","id":"CVE-2026-98576"},"packages":[],"prev":{"headline":"net: bcmgenet: stop Tx NAPI before disabling the queues","id":"CVE-2026-98574"},"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 pn533 driver, potentially leaking memory or causing a crash.","url":"https://insights.sbomify.com/CVE-2026-98575/"}