nilfs2: fix data corruption in dsync block recovery for small block sizes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b · < 2e1480538ef60bfee5473dfe02b1ecbaf1a4aa0d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix data corruption in dsync block recovery for small block sizes
The helper function nilfs_recovery_copy_block() of nilfs_recovery_dsync_blocks(), which recovers data from logs created by data sync writes during a mount after an unclean shutdown, incorrectly calculates the on-page offset when copying repair data to the file's page cache. In environments where the block size is smaller than the page size, this flaw can cause data corruption and leak uninitialized memory bytes during the recovery process.
Fix these issues by correcting this byte offset calculation on the page.
From the CVE record · Linux
The Linux kernel's nilfs2 recovery code calculates a page offset incorrectly when recovering data-sync writes during a mount after an unclean shutdown. When the block size is smaller than the page size, this can corrupt data and leak uninitialized memory bytes. The input does not describe an attacker scenario, authentication requirement, or user interaction.
Anyone running the Linux kernel with nilfs2 should check configurations where the block size is smaller than the page size; affected versions are not specified.