{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99177 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99177 is a vulnerability in Linux, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99177 and fix it if it is affected.\n\nWhat it is: CVE-2026-99177 is a vulnerability in Linux, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99177 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-99177/ (Markdown: https://insights.sbomify.com/CVE-2026-99177/index.md)","id":"CVE-2026-99177","markdown":"https://insights.sbomify.com/CVE-2026-99177/index.md","name":"CVE-2026-99177","record":{"aliases":["DEBIAN-CVE-2026-99177","GHSA-92wr-6h6p-mvpr","UBUNTU-CVE-2026-99177"],"analysis":null,"analysis_generated_by":null,"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\nKVM: SEV: Fix page dirtying in sev_gmem_post_populate()\n\nset_page_dirty() requires that the caller holds some kind of lock to\nensure that the page's mapping does not concurrently go away.\nThat is not the case for a random page we got from get_user_pages_fast(),\nso use set_page_dirty_lock().\n\n[sean: tag for stable]","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: Fix page dirtying in sev_gmem_post_populate()","id":"CVE-2026-99177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"x86/kvm: Don't consume async #PF flags on a kernel #PF in NMI context","id":"CVE-2026-99178"},"packages":[],"prev":{"headline":"KVM: nVMX: Reset MMU back to the root MMU if loading L2 state fails for !VM-Entry","id":"CVE-2026-99176"},"products":["Linux"],"published":"2026-10-28","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-28","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99177/"}