도구
로그인
한국어

코드 배우기보안지키미

CVE-2026-99336

중요CVSS 7.0

CVE-2026-99336 중요 7.0 · Linux kernel · Linux · 설명과 패치 안내

심각도
중요
점수
7.0 · CVSS 3.1CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
제품
Linux kernel · Linux
발표일
2026-11-20
마지막 고친 날
2026-11-22
실제 공격
실제 공격 목록에 없음

설명(영문)

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->invalidate_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->bindings 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->gmem.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.

관련 패치 안내

L04밀린 보안 업데이트가 있음L05새 커널을 깔고 재부팅 안 함

CVE 목록으로