In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix hugetlb_pmd_shared() Patch series "mm/hugetlb: fixes f
위협 신호 · CVSS · EPSS · KEV
이론적 심각도 점수
30일 내 악용 확률 예측
실측 악용 기록 없음
별도 긴급 패치 불필요 — 정기 시스템 업그레이드 주기에 맞춰 조치
CVSS 벡터 · 메트릭
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H상세 설명
In the Linux kernel, the following vulnerability has been resolved:
mm/hugetlb: fix hugetlb_pmd_shared()
Patch series "mm/hugetlb: fixes for PMD table sharing (incl. using
mmu_gather)", v3.
One functional fix, one performance regression fix, and two related
comment fixes.
I cleaned up my prototype I recently shared [1] for the performance fix,
deferring most of the cleanups I had in the prototype to a later point.
While doing that I identified the other things.
The goal of this patch set is to be backported to stable trees "fairly"
easily. At least patch #1 and #4.
Patch #1 fixes hugetlb_pmd_shared() not detecting any sharing
Patch #2 + #3 are simple comment fixes that patch #4 interacts with.
Patch #4 is a fix for the reported performance regression due to excessive
IPI broadcasts during fork()+exit().
The last patch is all about TLB flushes, IPIs and mmu_gather.
Read: complicated
There are plenty of cleanups in the future to be had + one reasonable
optimization on x86. But that's all out of scope for this series.
Runtime tested, with a focus on fixing the performance regression using
the original reproducer [2] on x86.
This patch (of 4):
We switched from (wrongly) using the page count to an independent shared
count. Now, shared page tables have a refcount of 1 (excluding
speculative references) and instead use ptdesc->pt_share_count to identify
sharing.
We didn't convert hugetlb_pmd_shared(), so right now, we would never
detect a shared PMD table as such, because sharing/unsharing no longer
touches the refcount of a PMD table.
Page migration, like mbind() or migrate_pages() would allow for migrating
folios mapped into such shared PMD tables, even though the folios are not
exclusive. In smaps we would account them as "private" although they are
"shared", and we would be wrongly setting the PM_MMAP_EXCLUSIVE in the
pagemap interface.
Fix it by properly using ptdesc_pmd_is_shared() in hugetlb_pmd_shared().
AI 심층 분석
공격 시나리오 · 재현 가능한 PoC 페이로드 · 즉시 적용 가능한 차단 패치를 한 번에 받아 보세요. 보안 운영팀이 그대로 점검·티켓팅에 쓸 수 있는 형태로 정리해 드립니다.
영향받는 제품·버전
- linux linux_kernel5.10.239 - 5.11linux
- linux linux_kernel5.15.186 - 5.16linux
- linux linux_kernel6.1.142 - 6.2linux
- linux linux_kernel6.6.72 - 6.6.127linux
- linux linux_kernel6.12.9 - 6.12.74linux
- linux linux_kernel6.13.1 - 6.18.8linux
- linux linux_kernellinux
- linux linux_kernellinux
- linux linux_kernellinux
- linux linux_kernellinux
- linux linux_kernellinux
- linux linux_kernellinux
- linux linux_kernellinux
- linux linux_kernellinux
- linux linux_kernellinux
영향받는 구성 (CPE) 10
- linux linux_kernel≥ 5.10.239 < 5.11cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
- linux linux_kernel 6.13cpe:2.3:o:linux:linux_kernel:6.13:-:*:*:*:*:*:*
- linux linux_kernel 6.13cpe:2.3:o:linux:linux_kernel:6.13:rc6:*:*:*:*:*:*
- linux linux_kernel 6.13cpe:2.3:o:linux:linux_kernel:6.13:rc7:*:*:*:*:*:*
- linux linux_kernel 6.19cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*
- linux linux_kernel 6.19cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*
- linux linux_kernel 6.19cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*
- linux linux_kernel 6.19cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*
- linux linux_kernel 6.19cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*
- linux linux_kernel 6.19cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*
참고 자료 9
링크 내용 불러오는 중…