CVE-2022-50581
Last modified
CVE-2022-50581 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: hfs: fix OOB Read in __hfs_brec_find Syzbot reported a OOB read bug: ================================================================== BUG: KASAN: slab-out-of-bounds in hfs_strcmp+0x117/0x190 fs/hfs/string.c:84 Read of size 1 at addr ffff88807eb62c4e by task kworker/u4:1/11 CPU: 1 PID: 11 Comm: kworker/u4:1 Not tainted 6.1.0-rc6-syzkaller-00308-g644e9524388a #0 Workqueue: writeback wb_workfn (flush-7:0) Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report+0xcd/0x100 mm/kasan/report.c:495 hfs_strcmp+0x117/0x190 fs/hfs/string.c:84 __hfs_brec_find+0x213/0x5c0 fs/hfs/bfind.c:75 hfs_brec_find+0x276/0x520 fs/hfs/bfind.c:138 hfs_write_inode+0x34c/0xb40 fs/hfs/inode.c:462 write_inode fs/fs-writeback.c:1440 [inline] If the input inode of hfs_write_inode() is incorrect: struct inode struct hfs_inode_info struct hfs_cat_key struct hfs_name u8 len # len is greater than HFS_NAMELEN(31) which is the maximum length of an HFS filename OOB read occurred: hfs_write_inode() hfs_brec_find() __hfs_brec_find() hfs_cat_keycmp() hfs_strcmp() # OOB read occurred due to len is too large Fix this by adding a Check on len in hfs_write_inode() before calling hfs_brec_find().. EPSS estimates a 0.24% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: hfs: fix OOB Read in __hfs_brec_find Syzbot reported a OOB read bug: ================================================================== BUG: KASAN: slab-out-of-bounds in hfs_strcmp+0x117/0x190 fs/hfs/string.c:84 Read of size 1 at addr ffff88807eb62c4e by task kworker/u4:1/11 CPU: 1 PID: 11 Comm: kworker/u4:1 Not tainted 6.1.0-rc6-syzkaller-00308-g644e9524388a #0 Workqueue: writeback wb_workfn (flush-7:0) Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report+0xcd/0x100 mm/kasan/report.c:495 hfs_strcmp+0x117/0x190 fs/hfs/string.c:84 __hfs_brec_find+0x213/0x5c0 fs/hfs/bfind.c:75 hfs_brec_find+0x276/0x520 fs/hfs/bfind.c:138 hfs_write_inode+0x34c/0xb40 fs/hfs/inode.c:462 write_inode fs/fs-writeback.c:1440 [inline] If the input inode of hfs_write_inode() is incorrect: struct inode struct hfs_inode_info struct hfs_cat_key struct hfs_name u8 len # len is greater than HFS_NAMELEN(31) which is the maximum length of an HFS filename OOB read occurred: hfs_write_inode() hfs_brec_find() __hfs_brec_find() hfs_cat_keycmp() hfs_strcmp() # OOB read occurred due to len is too large Fix this by adding a Check on len in hfs_write_inode() before calling hfs_brec_find().
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 8c40f2dbae603ef0bd21e87c63f54ec59fd88256; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < c886c10a6eddb99923b315f42bf63f448883ef9a; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 2344f17c0a89c181ab1a9fef57fd8c3bddfd6e30; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 90103ccb6e60aa4efe48993d23d6a528472f2233; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 4fd3a11804c8877ff11fec59c5c53f1635331e3e; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 367296925c7625c3969d2a78d7a3e1dee161beb5; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < e9e692917c6e10a7066c7a6d092dcdc3d4e329f3; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < bfc9d8f27f89717431a6aecce42ae230b437433f; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 8d824e69d9f3fa3121b2dda25053bae71e2460d2 |
| Linux | Linux | 2.6.12 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2022-50581?
How severe is CVE-2022-50581?
How do I fix CVE-2022-50581?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-50575In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50576In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50577In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50578In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50579In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50580In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50582In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50583In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50584The Core Config Manager (CCM) in Nagios XI versions prior to…5.4
- CVE-2022-50585The Core Config Manager (CCM) in Nagios XI versions prior to…5.4
- CVE-2022-50586Nagios XI versions prior to 5.8.9 are vulnerable to cross-si…5.4
- CVE-2022-50587Nagios XI versions prior to 5.8.9 are vulnerable to cross-si…5.4
Are you affected by CVE-2022-50581?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
