ext4: add bounds checking in get_max_inline_xattr_value_size()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 67cf5b09a46f72e048501b84996f2f77bc42e947 · < 1d2caddbeeee56fbbc36b428c5b909c3ad88eb7f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ext4: add bounds checking in get_max_inline_xattr_value_size()
Normally the extended attributes in the inode body would have been checked when the inode is first opened, but if someone is writing to the block device while the file system is mounted, it's possible for the inode table to get corrupted. Add bounds checking to avoid reading beyond the end of allocated memory if this happens.
From the CVE record · Linux
The Linux kernel’s ext4 code lacked bounds checking when determining the maximum inline extended-attribute value size. If someone writes to the block device while the file system is mounted, they can corrupt the inode table and cause a read beyond allocated memory. The input does not specify authentication or user-interaction requirements.
Engineers running Linux systems with mounted ext4 file systems should check their kernel; affected versions were not specified.