CVE-2024-47674

MEDIUM EPSS 14.6%
Published Oct 15, 20241y ago · Modified Jun 17, 20261w ago
5.5 CVSS 3.1
Medium
Find Similar
Published Oct 15, 2024 1y ago
Last Modified Jun 17, 2026 1w ago

Description

In the Linux kernel, the following vulnerability has been resolved: mm: avoid leaving partial pfn mappings around in error case As Jann points out, PFN mappings are special, because unlike normal memory mappings, there is no lifetime information associated with the mapping - it is just a raw mapping of PFNs with no reference counting of a 'struct page'. That's all very much intentional, but it does mean that it's easy to mess up the cleanup in case of errors. Yes, a failed mmap() will always eventually clean up any partial mappings, but without any explicit lifetime in the page table mapping itself, it's very easy to do the error handling in the wrong order. In particular, it's easy to mistakenly free the physical backing store before the page tables are actually cleaned up and (temporarily) have stale dangling PTE entries. To make this situation less error-prone, just make sure that any partial pfn mapping is torn down early, before any other error handling.

CVSS Details

Base Score
5.5
Exploitability
1.8
Impact
3.6
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality None
Integrity None
Availability High

Threat Intelligence

EPSS Exploit Probability
14.6% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Weaknesses 1

CWE-459

Affected Products 11

VendorProductVersionRange
linuxlinux_kernel* <5.15.168
linuxlinux_kernel*≥5.16  –  <6.1.111
linuxlinux_kernel*≥6.2  –  <6.6.52
linuxlinux_kernel*≥6.7  –  <6.10.11
linuxlinux_kernel6.11any
linuxlinux_kernel6.11any
linuxlinux_kernel6.11any
linuxlinux_kernel6.11any
linuxlinux_kernel6.11any
linuxlinux_kernel6.11any
linuxlinux_kernel6.11any

References 10

  • git.kernel.org https://git.kernel.org/stable/c/3213fdcab961026203dd587a4533600c70b3336b
  • git.kernel.org https://git.kernel.org/stable/c/35770ca6180caa24a2b258c99a87bd437a1ee10f
  • git.kernel.org https://git.kernel.org/stable/c/5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/65d0db500d7c07f0f76fc24a4d837791c4862cd2
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/79a61cc3fc0466ad2b7b89618a6157785f0293b3
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/954fd4c81f22c4b6ba65379a81fd252971bf4ef3
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/a95a24fcaee1b892e47d5e6dcc403f713874ee80
    Patch
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html
  • project-zero.issues.chromium.org https://project-zero.issues.chromium.org/issues/366053091

Remediation

  • git.kernel.org https://git.kernel.org/stable/c/5b2c8b34f6d76bfbd1dd4936eb8a0fbfb9af3959
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/65d0db500d7c07f0f76fc24a4d837791c4862cd2
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/79a61cc3fc0466ad2b7b89618a6157785f0293b3
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/954fd4c81f22c4b6ba65379a81fd252971bf4ef3
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/a95a24fcaee1b892e47d5e6dcc403f713874ee80
    Patch