CVE-2026-31575
What it is
In the Linux kernel, the following vulnerability has been resolved: mm/userfaultfd: fix hugetlb fault mutex hash calculation In mfill_atomic_hugetlb(), linear_page_index() is used to calculate the page index for hugetlb_fault_mutex_hash(). However, linear_page_index() returns the index in PAGE_SIZE units, while hugetlb_fault_mutex_hash() expects the index in huge page units. This mismatch means that different addresses within the same huge page can produce different hash values, leading to the use of different mutexes for the same huge page. This can cause races between faulting threads, which can corrupt the reservation map and trigger the BUG_ON in resv_map_release(). Fix this by introducing hugetlb_linear_page_index(), which returns the page index in huge page granularity, and using it in place of linear_page_index().
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 6.12.84
- Linux Kernel < 6.18.24
- Linux Kernel < 6.19.14
- Linux Kernel < 7.0.1
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-31575.md and follow it. Check whether this project is affected by CVE-2026-31575. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0217c7fb4de4a40cee667eb21901f3204effe5ac
- https://git.kernel.org/stable/c/08282b1bf74c69fc8ecd25493e7fdb5460f01290
- https://git.kernel.org/stable/c/574501ede47ac439afd67ba9812bc66722d500ba
- https://git.kernel.org/stable/c/5a525c43baaba0bf3063f86996ca3623b71e4172
- https://git.kernel.org/stable/c/f4689fc089765d36c026063fb22d23533e883eb6
References
- https://git.kernel.org/stable/c/0217c7fb4de4a40cee667eb21901f3204effe5ac
- https://git.kernel.org/stable/c/08282b1bf74c69fc8ecd25493e7fdb5460f01290
- https://git.kernel.org/stable/c/574501ede47ac439afd67ba9812bc66722d500ba
- https://git.kernel.org/stable/c/5a525c43baaba0bf3063f86996ca3623b71e4172
- https://git.kernel.org/stable/c/f4689fc089765d36c026063fb22d23533e883eb6