{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98471 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98471 is a high-severity 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-98471 and fix it if it is affected.\n\nWhat it is: CVE-2026-98471 is a high-severity 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-98471 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-98471/ (Markdown: https://insights.sbomify.com/CVE-2026-98471/index.md)","id":"CVE-2026-98471","markdown":"https://insights.sbomify.com/CVE-2026-98471/index.md","name":"CVE-2026-98471","record":{"aliases":["AZL-108702","BELL-CVE-2026-98471","DEBIAN-CVE-2026-98471","GHSA-hqmw-j6g2-75m9","UBUNTU-CVE-2026-98471"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel KVM","requires_auth":"high_privilege","summary":"A local attacker with high privileges can read stale data from CPU caches during KVM SEV intra-host migration due to missing cache maintenance on the source VM.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Do cache maintenance on the source VM during intra-host migration\n\nManually perform cache maintenance on the source VM during intra-host\nmigration to ensure no stale data is left in CPU caches after the VM is\ndestroyed.  Because the source VM is \"converted\" to a non-SEV VM, KVM's\nmemory reclaim flows won't trigger cache maintenance, e.g. when all guest\nmemory is reclaimed in response to detaching from the mmu_notifier.\n\nNote, relying on the destination VM to do cache maintenance isn't an option\nas KVM doesn't require identical guest memory configurations, i.e. the\nsource VM may have access to memory that the destination VM does not.\nEnforcing equivalent memory configurations is infeasible, as it would\nrequire a *deep* comparison of memslots, e.g. to verify that not only are\nthe memslot identical, but what the memslots point at is also identical.","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":"KVM: SEV: Do cache maintenance on the source VM during intra-host migration","id":"CVE-2026-98471","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV","id":"CVE-2026-98472"},"packages":[],"prev":{"headline":"KVM: arm64: Don't WARN on an unknown VM ioctl in protected mode","id":"CVE-2026-98470"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-24","vendors":["Linux"]},"summary":"A local attacker with high privileges can read stale data from CPU caches during KVM SEV intra-host migration due to missing cache maintenance on the source VM.","url":"https://insights.sbomify.com/CVE-2026-98471/"}