[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fIQbnG_TBULC5lrWIRGWXhUzkrcWkFRFoiCLX4zJ_S3c":3},{"article":4,"iocs":48,"iocs_total":56,"watch_terms":57,"solutions":58,"lesson":144},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":32,"category":33,"article_tags":37},"19b09a42-baa0-4e9b-a8a6-fe20112fc973","Linux KVM Flaw CVE-2026-99312 Lets Guest VMs Access Host Memory on AMD Hosts","linux-kvm-flaw-cve-2026-99312-lets-guest-vms-access-host-memory-on-amd-hosts-c7b209","A flaw in KVM, the hypervisor built into the Linux kernel, let researchers read about 127 GB of a cloud server's memory from inside a virtual machine of their own on DigitalOcean. On a shared server, that memory can include other customers' virtual machines. The flaw, tracked as CVE-2026-99312, affects only hosts with AMD processors and nested virtualization enabled. Fixed kernels shipped","A flaw in Linux KVM (CVE-2026-99312) enables guest virtual machines to access up to 127 GB of host memory on AMD processors with nested virtualization enabled, potentially exposing other customers' VMs on shared cloud servers. The vulnerability stems from an incomplete fix for CVE-2022-3344 that left a pointer referencing freed memory, which attackers with root access inside a guest VM could exploit to forge memory table entries. Fixed kernels shipped upstream on November 18, 2026, and DigitalOcean patched its infrastructure; operators running KVM on AMD hardware should update kernels or disable nested virtualization.","CVE-2026-99312 in Linux KVM allows guest VMs to read host memory on AMD systems with nested virtualization.","https:\u002F\u002Fthehackernews.com\u002F2026\u002F11\u002Fnew-linux-kvm-flaw-cve-2026-99312-lets.html","https:\u002F\u002Fblogger.googleusercontent.com\u002Fimg\u002Fb\u002FR29vZ2xl\u002FAVvXsEjg-jisyf4SWwWYA_RUtOoVqBviv2uNAUl6vEeGjsuBA0aOhfLYw7yHitbRBxAoWcf5ZP0UcGovNmyk-u-320fLFYIyUz7jtR77GiveyLdqsZWJ0DohwBfEFyN0KlNAIpIcpS9B6jHEZJybmTu7nuKM-PhSNPco-Z1QmacaSfwWyOWLXzT2WqaEdbZ810M\u002Fs1600\u002Fvms.jpg","2026-11-20T12:20:00+00:00","2026-11-20T13:00:46.984599+00:00",9,[17,20,22,25,27,30],{"name":18,"type":19},"Linux KVM","product",{"name":21,"type":19},"DigitalOcean Droplets",{"name":23,"type":24},"DigitalOcean","vendor",{"name":26,"type":24},"Red Hat",{"name":28,"type":29},"Oren Yomtov","threat_actor",{"name":31,"type":24},"Terra Security","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":32,"icon":34,"name":35,"slug":36},null,"Vulnerabilities","vulnerabilities",[38,43],{"category":39},{"id":40,"icon":34,"name":41,"slug":42},"c70f3a41-2f0c-4608-870d-b8cbcd8be076","Cloud Security","cloud-security",{"category":44},{"id":45,"icon":34,"name":46,"slug":47},"d6f63bb8-0801-486a-be7f-171400700454","IoT\u002FOT","iot-ot",[49,53],{"type":50,"value":51,"context":52},"cve","CVE-2022-3344","Earlier nested-virtualization bug whose incomplete fix introduced CVE-2026-99312",{"type":50,"value":54,"context":55},"CVE-2026-99312","Linux KVM memory disclosure flaw on AMD hosts",2,[23,26,31],{"controls":59,"vendors":143},[60,89,114],{"slug":61,"name":62,"problem":63,"products":64},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[65,73,81],{"vendor_slug":66,"vendor_name":67,"vendor_logo":68,"product_slug":69,"product_name":70,"url":71,"description":72},"qualys","Qualys","\u002Fvendor-logos\u002Fqualys.png","vmdr","Qualys VMDR","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fvulnerability-management-detection-response\u002F","Vulnerability management, detection and response with risk-based prioritisation.",{"vendor_slug":74,"vendor_name":75,"vendor_logo":76,"product_slug":77,"product_name":78,"url":79,"description":80},"axonius","Axonius","\u002Fvendor-logos\u002Faxonius.png","axonius-exposures","Axonius Exposures","https:\u002F\u002Fwww.axonius.com\u002Fplatform\u002Fexposures","Brings findings from different scanners together with asset and business context, to show what matters most and track fixes to the end.",{"vendor_slug":82,"vendor_name":83,"vendor_logo":84,"product_slug":85,"product_name":86,"url":87,"description":88},"holm-security","Holm Security","\u002Fvendor-logos\u002Fholm-security.png","holm-security-platform","Holm Security Platform","https:\u002F\u002Fwww.holmsecurity.com\u002F","Vulnerability scanning of systems, web applications, cloud and the external attack surface, plus phishing simulation.",{"slug":90,"name":91,"problem":92,"products":93},"patch-management","Automated patch management","Known holes get closed in days, not months.",[94,98,106],{"vendor_slug":66,"vendor_name":67,"vendor_logo":68,"product_slug":90,"product_name":95,"url":96,"description":97},"Qualys Patch Management","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fpatch-management\u002F","Patch deployment for operating systems and third-party applications, linked to vulnerability findings.",{"vendor_slug":99,"vendor_name":100,"vendor_logo":101,"product_slug":102,"product_name":103,"url":104,"description":105},"microsoft","Microsoft","\u002Fvendor-logos\u002Fmicrosoft.png","intune","Microsoft Intune","https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fsecurity\u002Fbusiness\u002Fmicrosoft-intune","Device management for Windows, macOS, iOS and Android, including update rings and compliance policies.",{"vendor_slug":107,"vendor_name":108,"vendor_logo":109,"product_slug":110,"product_name":111,"url":112,"description":113},"action1","Action1","\u002Fvendor-logos\u002Faction1.png","action1-patch-management","Action1 Patch Management","https:\u002F\u002Fwww.action1.com\u002F","Cloud-native patch management for Windows, macOS and third-party applications.",{"slug":115,"name":116,"problem":117,"products":118},"network-segmentation","Network segmentation and microsegmentation","One compromised machine can no longer reach everything else.",[119,127,135],{"vendor_slug":120,"vendor_name":121,"vendor_logo":122,"product_slug":123,"product_name":124,"url":125,"description":126},"threatlocker","ThreatLocker","\u002Fvendor-logos\u002Fthreatlocker.png","zero-trust-endpoint-firewall","Zero Trust Endpoint Firewall","https:\u002F\u002Fwww.threatlocker.com\u002Fcapabilities\u002Fzero-trust-endpoint-firewall","Centrally managed host firewall with device-level and dynamic access rules, to limit which machines can talk to each other.",{"vendor_slug":128,"vendor_name":129,"vendor_logo":130,"product_slug":131,"product_name":132,"url":133,"description":134},"akamai","Akamai","\u002Fvendor-logos\u002Fakamai.png","guardicore-segmentation","Akamai Guardicore Segmentation","https:\u002F\u002Fwww.akamai.com\u002Fproducts\u002Fakamai-guardicore-segmentation","Software-based microsegmentation with traffic visibility.",{"vendor_slug":136,"vendor_name":137,"vendor_logo":138,"product_slug":139,"product_name":140,"url":141,"description":142},"illumio","Illumio","\u002Fvendor-logos\u002Fillumio.png","illumio-segmentation","Illumio Segmentation","https:\u002F\u002Fwww.illumio.com\u002Fillumio-segmentation","Maps traffic between workloads and enforces segmentation across data centre, cloud and endpoints.",[],{"slug":145,"title":146,"body":147,"framework_refs":148,"framework_notes":154},"incomplete-kernel-patch-leaves-kvm-guests-able-to-read-host-memory-on-amd-systems","Incomplete Kernel Patch Leaves KVM Guests Able to Read Host Memory on AMD Systems","An incomplete fix for a 2022 Linux KVM vulnerability left a dangling pointer that attackers with root access inside a guest VM could exploit to forge memory table entries and read up to 127 GB of host memory on AMD processors with nested virtualization enabled. This is a classic case of a partial patch introducing a residual risk that persists for years before being discovered and fully remediated. In multi-tenant cloud environments, the blast radius is especially severe because one compromised or malicious tenant could access memory belonging to other customers. The incident underscores that patch quality and regression testing are as important as patch speed, and that hypervisor-level vulnerabilities demand priority treatment given the privileged boundary they protect.",[149,150,151,152,153],"CIS Control 7: Continuous Vulnerability Management (v8)","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 PR.PS-02: Software is maintained","NIS2 Article 21(2)(e)","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities",{"NIS2 Article 21(2)(e)":155,"NIST SP 800-53 SI-2: Flaw Remediation":156,"NIST CSF 2.0 PR.PS-02: Software is maintained":157,"CIS Control 7: Continuous Vulnerability Management (v8)":158,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":159},"This point requires security in acquisition, development, and maintenance including vulnerability handling and disclosure, covering the obligation to fully remediate known flaws and validate patch completeness in critical infrastructure software like hypervisors.","SI-2 requires that software flaws be identified, reported, and corrected in a timely manner, and explicitly covers the testing of updates to prevent introducing new vulnerabilities — directly addressing the incomplete patch scenario here.","This category requires that software, including firmware and hypervisors, be maintained at versions that address known vulnerabilities, which would have mandated validation that the 2022 fix fully closed the attack surface.","CIS Control 7 requires organizations to continuously assess and remediate vulnerabilities, which would have surfaced the incomplete 2022 patch and the residual CVE-2026-99312 risk before exploitation.","A.8.8 requires organizations to obtain timely information about technical vulnerabilities and take appropriate measures, which would include verifying that patches for prior CVEs such as CVE-2022-3344 were complete and effective."]