{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98020 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98020 is a vulnerability in Linux, published on 25 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-98020 and fix it if it is affected.\n\nWhat it is: CVE-2026-98020 is a vulnerability in Linux, published on 25 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-98020 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-98020/ (Markdown: https://insights.sbomify.com/CVE-2026-98020/index.md)","id":"CVE-2026-98020","markdown":"https://insights.sbomify.com/CVE-2026-98020/index.md","name":"CVE-2026-98020","record":{"aliases":["AZL-104229","BELL-CVE-2026-98020","DEBIAN-CVE-2026-98020","GHSA-qm2m-cwg6-99v6","UBUNTU-CVE-2026-98020"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A race condition in the pds_core driver allows unmapping memory during firmware updates, potentially causing a kernel crash or arbitrary code execution.","user_interaction":"not_required","vuln_class":"race_condition"},"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\npds_core: fix cmd_regs access racing BAR unmap on reset\n\npdsc_reset_prepare() and pdsc_reset_done()'s pdsc_map_bars() error path\nclear/iounmap cmd_regs without devcmd_lock, and\npdsc_legacy_firmware_update()'s download loop derefs cmd_regs after\ndropping and retaking the lock without re-checking. An FLR concurrent\nwith a devlink flash can unmap cmd_regs under an in-flight devcmd,\ncausing a NULL deref or a write to unmapped MMIO.\n\nTake devcmd_lock across the BAR unmap/remap, and re-check cmd_regs in\nthe download loop. Only the PF maps cmd_regs and runs devcmd, so skip\nthe unmap on a VF, as pdsc_remove() and pdsc_reset_done() already do.\n\nA reset that completes entirely within the unlocked window is not a\ncorrectness problem for the image: the device clears its update session,\nso a resumed download is rejected, and it verifies the staged image\nbefore writing a flash slot, reporting PDS_RC_BAD_FW rather than\nactivating it.\n\npdsc_unmap_bars() also clears info_regs, intr_status and intr_ctrl. The\ninterrupt and start/stop readers of those are quiesced before the unmap\nby pdsc_fw_down(), which frees the interrupts and tears down the queues.\nThe debugfs readers are not, since those files outlive a reset; that is\npre-existing and out of scope here.","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":"pds_core: fix cmd_regs access racing BAR unmap on reset","id":"CVE-2026-98020","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"net: reject oversized tx_queue_len at netlink parse time","id":"CVE-2026-98021"},"packages":[],"prev":{"headline":"bpf: mark a NULL call argument precise","id":"CVE-2026-98019"},"products":["Linux"],"published":"2026-09-25","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 race condition in the pds_core driver allows unmapping memory during firmware updates, potentially causing a kernel crash or arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2026-98020/"}