CVE-2024-50218
ocfs2: pass u64 to ocfs2_truncate_inline maybe overflow
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: ocfs2: pass u64 to ocfs2_truncate_inline maybe overflow Syzbot reported a kernel BUG in ocfs2_truncate_inline. There are two reasons for this: first, the parameter value passed is greater than ocfs2_max_inline_data_with_xattr, second, the start and end parameters of ocfs2_truncate_inline are "unsigned int". So, we need to add a sanity check for byte_start and byte_len right before ocfs2_truncate_inline() in ocfs2_remove_inode_range(), if they are greater than ocfs2_max_inline_data_with_xattr return -EINVAL.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.24
References 8
git.kernel.org
- stable/c/27d95867bee806cdc448d122bd99f1d8b0544035
- stable/c/95fbed8ae8c32c0977e6be1721c190d8fea23f2f
- stable/c/70767689ec6ee5f05fb0a2c17d7ec1927946e486
- stable/c/ecd62f684386fa64f9c0cea92eea361f4e6444c2
- stable/c/2fe5d62e122b040ce7fc4d31aa7fa96ae328cefc
- stable/c/88f97a4b5843ce21c1286e082c02a5fb4d8eb473
- stable/c/0b6b8c2055784261de3fb641c5d0d63964318e8f
- stable/c/bc0a2f3a73fcdac651fca64df39306d1e5ebe3b0