[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fjy9JSMATYmgxph5XJ2-zhFgiEmvtVZbNwkbweEHLe00":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":50},"b30c5d30-4514-4e37-a5da-09e149614755","incomplete-kernel-patch-leaves-kvm-guests-able-to-read-host-memory-on-amd-systems","19b09a42-baa0-4e9b-a8a6-fe20112fc973","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.","**Immediate actions:**\n- Apply the fixed kernel shipped upstream on November 18, 2026 to all KVM hosts running AMD processors as soon as possible.\n- Disable nested virtualization on AMD KVM hosts as a temporary mitigation if immediate kernel patching is not feasible.\n- Audit all multi-tenant KVM deployments to confirm patch status and exposure before resuming normal operations.\n\n**Long-term improvements:**\n- Establish a formal patch validation process that includes regression testing for previously fixed CVEs when related code areas are modified.\n- Maintain a real-time inventory of hypervisor versions and enabled features (such as nested virtualization) across all host infrastructure.\n- Apply the principle of least privilege so that guest VM workloads never run with unnecessary root or elevated access inside the VM.\n\n**Detection measures:**\n- Subscribe to Linux kernel security mailing lists and CVE feeds specifically covering KVM and hypervisor components for early warning.\n- Implement memory integrity monitoring and anomaly detection at the hypervisor layer to flag unexpected cross-VM memory access patterns.\n- Track and alert on any changes to virtualization feature flags (e.g., nested virtualization toggles) in cloud infrastructure configuration management tools.",[12,13,14,15,16],"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)":18,"NIST SP 800-53 SI-2: Flaw Remediation":19,"NIST CSF 2.0 PR.PS-02: Software is maintained":20,"CIS Control 7: Continuous Vulnerability Management (v8)":21,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":22},"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.","published","2026-11-20T14:21:36.933839+00:00","2026-11-20T14:21:36.918+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fthehackernews.com\u002F2026\u002F11\u002Fnew-linux-kvm-flaw-cve-2026-99312-lets.html","linux-kvm-flaw-cve-2026-99312-lets-guest-vms-access-host-memory-on-amd-hosts-c7b209","Linux KVM Flaw CVE-2026-99312 Lets Guest VMs Access Host Memory on AMD Hosts",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":38,"name":39,"slug":40,"description":41,"color":42},"af7fce9e-1ce8-4156-93bc-09dcfbfdf29d","Patch Management","patch-management","Unpatched vulnerabilities, delayed updates","#ef4444",[44],{"id":45,"date":46,"edition":47,"title":48,"audio_url":49},"0bb91999-d8d6-422a-ac21-58fc90d5815f","2026-11-20","afternoon","ThreatNoir Afternoon Brief — November 20","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-11-20\u002Fthreatnoir-afternoon-brief-2026-11-20.mp3",[51,54,57],{"slug":34,"name":52,"problem":53},"Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",{"slug":40,"name":55,"problem":56},"Automated patch management","Known holes get closed in days, not months.",{"slug":58,"name":59,"problem":60},"network-segmentation","Network segmentation and microsegmentation","One compromised machine can no longer reach everything else."]