VYPR
Medium severity5.5NVD Advisory· Published Apr 22, 2026· Updated Apr 28, 2026

CVE-2026-31514

CVE-2026-31514

Description

In the Linux kernel, the following vulnerability has been resolved:

erofs: set fileio bio failed in short read case

For file-backed mount, IO requests are handled by vfs_iocb_iter_read(). However, it can be interrupted by SIGKILL, returning the number of bytes actually copied. Unused folios in bio are unexpectedly marked as uptodate.

vfs_read filemap_read filemap_get_pages filemap_readahead erofs_fileio_readahead erofs_fileio_rq_submit vfs_iocb_iter_read filemap_read filemap_get_pages <= detect signal erofs_fileio_ki_complete <= set all folios uptodate

This patch addresses this by setting short read bio with an error directly.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

In the Linux kernel's erofs filesystem, a short read due to SIGKILL during file-backed mount can cause unused folios to be incorrectly marked as uptodate, leading to potential data corruption.

Vulnerability

Description

In the Linux kernel's erofs filesystem, when using a file-backed mount, I/O requests are handled by vfs_iocb_iter_read(). This function can be interrupted by a SIGKILL signal, causing it to return fewer bytes than requested (a short read). The completion handler erofs_fileio_ki_complete then marks all folios in the bio as uptodate, even those that were not actually read. This results in unused folios being incorrectly marked as up-to-date, which is the root cause of the vulnerability [1][2][3][4].

Exploitation

Conditions

Exploitation requires local access to the system and the ability to send a SIGKILL signal to a process that is performing I/O on an erofs file-backed mount. The attacker must be able to trigger the signal at the precise moment when the I/O is in progress. No special authentication is needed beyond standard local user privileges. The attack surface is limited to scenarios where the attacker can influence the timing of signal delivery.

Impact

If successfully exploited, the incorrect marking of folios as uptodate can lead to reading uninitialized or stale data from the filesystem. This could result in information disclosure or data corruption, depending on how the affected folios are used. The CVSS v3 score of 5.5 (Medium) reflects the moderate severity, as the vulnerability requires local access and specific conditions to be triggered.

Mitigation

The fix has been applied in the Linux kernel stable tree via commits [1][2][3][4]. Users are advised to update their kernels to versions that include these patches. No workaround is documented; updating the kernel is the recommended mitigation.

AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

3

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

4

News mentions

0

No linked articles in our index yet.