Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty() nilfs_ioctl_mark_blocks_dirty() uses bd_oblocknr to detect dead blocks by comparing it with the current block number bd_blocknr. If they differ, the block is considered dead and skipped. However, bd_oblocknr should never be 0 since block 0 typically stores the primary superblock and is never a valid GC target block. A corrupted ioctl request with bd_oblocknr set to 0 causes the comparison to incorrectly match when the lookup returns -ENOENT and sets bd_blocknr to 0, bypassing the dead block check and calling nilfs_bmap_mark() on a non-existent block. This causes nilfs_btree_do_lookup() to return -ENOENT, triggering the WARN_ON(ret == -ENOENT). Fix this by rejecting ioctl requests with bd_oblocknr set to 0 at the beginning of each iteration. [ryusuke: slightly modified the commit message and comments for accuracy]

Affected products

VendorProductVersions
LinuxLinux7942b919f7321f95a777d396ff7894a7a83dc9b0 to <e0a0c4903cbba351f0f5b5d104960d3a5b23202f; 7942b919f7321f95a777d396ff7894a7a83dc9b0 to <9472d37799a0b9ff9b99639f35961ac2f0b3c9be; 7942b919f7321f95a777d396ff7894a7a83dc9b0 to <65e07964b4b2daf9a54e686cf0fa72d74a9648a8; 7942b919f7321f95a777d396ff7894a7a83dc9b0 to <b88f905d4449b70da6bda547be546e365e44352e; 7942b919f7321f95a777d396ff7894a7a83dc9b0 to <4525658002be3ad310b16bf8db48c8adb6a55d32; 7942b919f7321f95a777d396ff7894a7a83dc9b0 to <e5ff0ba4b6983cdbcc826efc201e7179ece5d46f; 7942b919f7321f95a777d396ff7894a7a83dc9b0 to <94094e70fe292c9566502772d4d4d6d6a99204b1; 7942b919f7321f95a777d396ff7894a7a83dc9b0 to <be3e5d10643d3be1cbac9d9939f220a99253f980
LinuxLinux2.6.30; 0 to <2.6.30; 5.10.258 to <=5.10.*; 5.15.209 to <=5.15.*; 6.1.175 to <=6.1.*; 6.6.141 to <=6.6.*; 6.12.91 to <=6.12.*; 6.18.33 to <=6.18.*; 7.0.10 to <=7.0.*; 7.1 to <=*

References

Authoritative sources

This page is a snapshot. For the latest enrichment and updates, view the record on CVE.org or the NVD.

Generated from the official CVE List on 27 Jun 2026 07:02 UTC.