CVE-2026-43262
Page Fault in GFS2 FIEMAP Handling
Publication date: 2026-05-06
Last updated on: 2026-05-08
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.2 (inc) to 6.6.128 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.75 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.16 (exc) |
| linux | linux_kernel | From 6.19 (inc) to 6.19.6 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.165 (exc) |
| linux | linux_kernel | From 2.6.29 (inc) to 5.15.202 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-401 | The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's gfs2 filesystem code, specifically in the gfs2_fiemap() function. The issue arises because the function calls iomap_fiemap() while holding the inode glock (a type of lock). If the fiemap buffer is memory mapped to the same inode, accessing it can trigger a page fault, which leads to recursive acquisition of the glock. This recursive locking can cause problems such as deadlocks or crashes.
The fix implemented disables page faults during the iomap_fiemap() call and manually handles faulting in the buffer if needed, preventing the recursive glock taking scenario.
How can this vulnerability impact me? :
This vulnerability can lead to system instability or crashes due to recursive locking (recursive glock taking) when accessing certain memory-mapped files on the gfs2 filesystem. Such instability could cause denial of service conditions on affected systems, potentially interrupting normal operations.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability in the Linux kernel related to gfs2 fiemap page fault has been fixed by disabling page faults for iomap_fiemap() and handling buffer faults manually.
To mitigate this vulnerability, you should update your Linux kernel to a version that includes this fix.