ext4: add bounds checking in get_max_inline_xattr_value_size()
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.8epss 0.1%
exploitation probability
0.1%top 96% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/1d2caddbeeee56fbbc36b428c5b909c3ad88eb7fhttps://git.kernel.org/stable/c/2220eaf90992c11d888fe771055d4de330385f01https://git.kernel.org/stable/c/3d7b8fbcd2273e2b9f4c6de5ce2f4c0cd3cb1205https://git.kernel.org/stable/c/4597554b4f7b29e7fd78aa449bab648f8da4ee2chttps://git.kernel.org/stable/c/486efbbc9445dca7890a1b86adbccb88b91284b0https://git.kernel.org/stable/c/5a229d21b98d132673096710e8281ef522dab1d1https://git.kernel.org/stable/c/88a06a94942c5c0a896e9da1113a6bb29e36cbefhttps://git.kernel.org/stable/c/e780058bd75614b66882bc02620ddbd884171560https://git.kernel.org/stable/c/f22b274429e88d3dc7e79d375b56ce4f2f59f0b4