gfs2: Always check inode size of inline inodes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b3b94faa5fe5968827ba0640ee9fba4b3e7f736e · < 70376c7ff31221f1d21db5611d8209e677781d3a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gfs2: Always check inode size of inline inodes
Check if the inode size of stuffed (inline) inodes is within the allowed range when reading inodes from disk (gfs2_dinode_in()). This prevents us from on-disk corruption.
The two checks in stuffed_readpage() and gfs2_unstuffer_page() that just truncate inline data to the maximum allowed size don't actually make sense, and they can be removed now as well.
From the CVE record · Linux
The Linux kernel’s gfs2 code did not check whether a stuffed (inline) inode’s size was within the allowed range when reading it from disk. An out-of-range inode size could cause on-disk corruption; the input does not specify attacker access requirements or user interaction.
Engineers running Linux systems that use gfs2 should check their kernel versions; affected versions are not specified.