nilfs2: reject invalid file types when reading inodes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 05fe58fdc10df9ebea04c0eaed57adc47af5c184 · < 79663a15a1c70ca84f86f2dbba07b423fe7d5d4f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: reject invalid file types when reading inodes
To prevent inodes with invalid file types from tripping through the vfs and causing malfunctions or assertion failures, add a missing sanity check when reading an inode from a block device. If the file type is not valid, treat it as a filesystem error.
From the CVE record · Linux
The Linux kernel’s nilfs2 filesystem does not check for invalid file types when reading inodes from a block device. An invalid file type can pass through the VFS and cause malfunctions or assertion failures. The input does not specify whether an attacker needs network access, authentication, or user interaction.
Engineers running Linux kernels with nilfs2 should check their installations; affected versions are not specified.