CVE-2024-42233
Linux Kernel PTE Unmap Use-After-Free Vulnerability
Description
In the Linux kernel, the following vulnerability has been resolved: filemap: replace pte_offset_map() with pte_offset_map_nolock() The vmf->ptl in filemap_fault_recheck_pte_none() is still set from handle_pte_fault(). But at the same time, we did a pte_unmap(vmf->pte). After a pte_unmap(vmf->pte) unmap and rcu_read_unlock(), the page table may be racily changed and vmf->ptl maybe fails to protect the actual page table. Fix this by replacing pte_offset_map() with pte_offset_map_nolock(). As David said, the PTL pointer might be stale so if we continue to use it infilemap_fault_recheck_pte_none(), it might trigger UAF. Also, if the PTL fails, the issue fixed by commit 58f327f2ce80 ("filemap: avoid unnecessary major faults in filemap_fault()") might reappear.
INFO
Published Date :
Aug. 7, 2024, 4:15 p.m.
Last Modified :
Aug. 8, 2024, 2:56 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
1.4
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-42233
.
URL | Resource |
---|---|
https://git.kernel.org/stable/c/24be02a42181f0707be0498045c4c4b13273b16d | Patch |
https://git.kernel.org/stable/c/6a6c2aec1a89506595801b4cf7e8eef035f33748 | Patch |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-42233
vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-42233
vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Aug. 08, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N Changed Reference Type https://git.kernel.org/stable/c/24be02a42181f0707be0498045c4c4b13273b16d No Types Assigned https://git.kernel.org/stable/c/24be02a42181f0707be0498045c4c4b13273b16d Patch Changed Reference Type https://git.kernel.org/stable/c/6a6c2aec1a89506595801b4cf7e8eef035f33748 No Types Assigned https://git.kernel.org/stable/c/6a6c2aec1a89506595801b4cf7e8eef035f33748 Patch Added CWE NIST NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.9 up to (excluding) 6.9.10 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 07, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: filemap: replace pte_offset_map() with pte_offset_map_nolock() The vmf->ptl in filemap_fault_recheck_pte_none() is still set from handle_pte_fault(). But at the same time, we did a pte_unmap(vmf->pte). After a pte_unmap(vmf->pte) unmap and rcu_read_unlock(), the page table may be racily changed and vmf->ptl maybe fails to protect the actual page table. Fix this by replacing pte_offset_map() with pte_offset_map_nolock(). As David said, the PTL pointer might be stale so if we continue to use it infilemap_fault_recheck_pte_none(), it might trigger UAF. Also, if the PTL fails, the issue fixed by commit 58f327f2ce80 ("filemap: avoid unnecessary major faults in filemap_fault()") might reappear. Added Reference kernel.org https://git.kernel.org/stable/c/6a6c2aec1a89506595801b4cf7e8eef035f33748 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/24be02a42181f0707be0498045c4c4b13273b16d [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-42233
is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-42233
weaknesses.