CVE-2026-43262
Page Fault in GFS2 FIEMAP Handling
Publication date: 2026-05-06
Last updated on: 2026-05-06
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
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.