CVE-2024-42105

/// Technical description

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

nilfs2: fix inode number range checks

Patch series "nilfs2: fix potential issues related to reserved inodes".

This series fixes one use-after-free issue reported by syzbot, caused by

nilfs2's internal inode being exposed in the namespace on a corrupted

filesystem, and a couple of flaws that cause problems if the starting

number of non-reserved inodes written in the on-disk super block is

intentionally (or corruptly) changed from its default value.

This patch (of 3):

In the current implementation of nilfs2, "nilfs->ns_first_ino", which

gives the first non-reserved inode number, is read from the superblock,

but its lower limit is not checked.

As a result, if a number that overlaps with the inode number range of

reserved inodes such as the root directory or metadata files is set in the

super block parameter, the inode number test macros (NILFS_MDT_INODE and

NILFS_VALID_INODE) will not function properly.

In addit

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References