CVE-2022-50567
fs: jfs: fix shift-out-of-bounds in dbAllocAG
- 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: fs: jfs: fix shift-out-of-bounds in dbAllocAG Syzbot found a crash : UBSAN: shift-out-of-bounds in dbAllocAG. The underlying bug is the missing check of bmp->db_agl2size. The field can be greater than 64 and trigger the shift-out-of-bounds. Fix this bug by adding a check of bmp->db_agl2size in dbMount since this field is used in many following functions. The upper bound for this field is L2MAXL2SIZE - L2MAXAG, thanks for the help of Dave Kleikamp. Note that, for maintenance, I reorganized error handling code of dbMount.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.12
References 9
git.kernel.org
- stable/c/d3b486946a4e62c7ef6023f7d9c1d049051384ba
- stable/c/3115313cf03113e87c87adee18ee49a20bbdb9ba
- stable/c/eea87acb6027be3dd4d3c57186bb22800d57fdda
- stable/c/359616ce587e524107730504891afa4b1a8be58c
- stable/c/3e997e4ce8ae7ab89d72334120f6aee49c5bbdbd
- stable/c/0536f76a2bca83d1a3740517ba22cc93a44b3099
- stable/c/2c575c8905f7a8b32d5611b91856b69bac2a5bf1
- stable/c/67973caae78e21ee46a7281aaa8ca364eb9c444f
- stable/c/898f706695682b9954f280d95e49fa86ffa55d08