{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.3.3-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  KVM: guest_memfd: take the invalidate lock when unbinding a dying file  kvm_gmem_unbind() takes mapping-\u003einvalidate_lock only if the get_file_active() succeeds. When the guest_memfd file is dying, its reference count is already zero so get_file_active fails and the binding is removed without holding the invalidate lock.  kvm_gmem_invalidate_{start,end}() checks f-\u003ebindings independently to decide whether to begin or end KVM MMU invalidation. So, the bindings must therefore remain stable between the two calls. Otherwise, unbind can remove a binding after start increments mmu_invalidate_in_progress, but before end finds the binding and decrements it. Example, unbind race with memory failure:    CPU 0: memory failure               CPU 1: memslot delete   ----------------------------------  ---------------------------                                       (guest_memfd file is dying)   kvm_gmem_error_folio()     kvm_gmem_invalidate_start()       finds binding       mmu_invalidate_in_progress++                                       kvm_gmem_unbind()                                         get_file_active() fails                                         removes binding     kvm_gmem_invalidate_end()       no binding found       counter stays elevated  mmu_invalidate_retry() then returns 1 forever, so guest page faults retry without ever installing a mapping and the guest hangs.  Remove the distinction between live and dying files in the unbind path. Always use slot-\u003egmem.file and take the invalidate lock when it's non-NULL. Normal unbind callers hold slots_lock, which prevents release from clearing the pointer or freeing the file state until unbind completes. Final VM teardown can only see a NULL pointer because guest_memfd pins the KVM until release has cleared all bindings.",
  "id": "DEBIAN-CVE-2026-99336",
  "modified": "2026-11-20T04:47:34.706121889Z",
  "published": "2026-11-19T15:17:44.610Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-99336"
    }
  ],
  "upstream": [
    "CVE-2026-99336"
  ]
}