CVE-2025-37999 Details
Description
In the Linux kernel, the following vulnerability has been resolved: fs/erofs/fileio: call erofs_onlinefolio_split() after bio_add_folio() If bio_add_folio() fails (because it is full), erofs_fileio_scan_folio() needs to submit the I/O request via erofs_fileio_rq_submit() and allocate a new I/O request with an empty `struct bio`. Then it retries the bio_add_folio() call. However, at this point, erofs_onlinefolio_split() has already been called which increments `folio->private`; the retry will call erofs_onlinefolio_split() again, but there will never be a matching erofs_onlinefolio_end() call. This leaves the folio locked forever and all waiters will be stuck in folio_wait_bit_common(). This bug has been added by commit ce63cb62d794 ("erofs: support unencoded inodes for fileio"), but was practically unreachable because there was room for 256 folios in the `struct bio` - until commit 9f74ae8c9ac9 ("erofs: shorten bvecs[] for file-backed mounts") which reduced the array capacity to 16 folios. It was now trivial to trigger the bug by manually invoking readahead from userspace, e.g.: posix_fadvise(fd, 0, st.st_size, POSIX_FADV_WILLNEED); This should be fixed by invoking erofs_onlinefolio_split() only after bio_add_folio() has succeeded. This is safe: asynchronous completions invoking erofs_onlinefolio_end() will not unlock the folio because erofs_fileio_scan_folio() is still holding a reference to be released by erofs_onlinefolio_end() at the end.
A denial-of-service vulnerability has been identified in the Linux kernel's EROFS (Enhanced Read-Only File System) implementation. This issue arises in versions of the kernel that include the commit 'ce63cb62d794', which added support for unencoded inodes in file I/O operations. The vulnerability occurs when the I/O request buffer becomes full, causing the system to attempt to split the file's data into smaller chunks. However, due to a flaw in the error handling process, the file data can become locked indefinitely, preventing any further operations on it. This issue was practically unreachable until a recent change reduced the buffer capacity, making it easy to trigger by invoking a readahead operation from userspace.
The vulnerability has been addressed in the Linux kernel by modifying the file I/O handling process to ensure that the folio splitting operation is only called after the I/O request has been successfully updated. This change prevents the file data from becoming locked indefinitely.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/61e0fc3312309867e5a3495329dad0286d2a5703 | kernel.org | Patch |
| https://git.kernel.org/stable/c/bbfe756dc3062c1e934f06e5ba39c239aa953b92 | kernel.org | Patch |
| https://git.kernel.org/stable/c/c26076197df348c84cc23e5962d61902e072a0f5 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.12, < 6.12.29 >= 6.13, < 6.14.7 6.15 rc1 6.15 rc2 6.15 rc3 6.15 rc4 6.15 rc5 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 14, 2025 | Initial Analysis | [email protected] |
| May 29, 2025 | New CVE Received | kernel.org |