nilfs2: fix OOB in nilfs_set_de_type
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2ba466d74ed74f073257f86e61519cb8f8f46184 · < 2382eae66b196c31893984a538908c3eb7506ff9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix OOB in nilfs_set_de_type
The size of the nilfs_type_by_mode array in the fs/nilfs2/dir.c file is defined as "S_IFMT >> S_SHIFT", but the nilfs_set_de_type() function, which uses this array, specifies the index to read from the array in the same way as "(mode & S_IFMT) >> S_SHIFT".
static void nilfs_set_de_type(struct nilfs_dir_entry *de, struct inode *inode) { umode_t mode = inode->i_mode;
de->file_type = nilfs_type_by_mode[(mode & S_IFMT)>>S_SHIFT]; // oob }
However, when the index is determined this way, an out-of-bounds (OOB) error occurs by referring to an index that is 1 larger than the array size when the condition "mode & S_IFMT == S_IFMT" is satisfied. Therefore, a patch to resize the nilfs_type_by_mode array should be applied to prevent OOB errors.
From the CVE record · Linux
The Linux kernel’s nilfs2 code can read past the nilfs_type_by_mode array when an inode’s mode satisfies mode & S_IFMT == S_IFMT. The input does not specify the resulting impact or whether exploitation requires local access, authentication, or user interaction.
Engineers running Linux kernels with nilfs2 should check their exposure; affected versions are not specified.