CVE-2022-50673
Last modified
CVE-2022-50673 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ext4: fix use-after-free in ext4_orphan_cleanup I caught a issue as follows: ================================================================== BUG: KASAN: use-after-free in __list_add_valid+0x28/0x1a0 Read of size 8 at addr ffff88814b13f378 by task mount/710 CPU: 1 PID: 710 Comm: mount Not tainted 6.1.0-rc3-next #370 Call Trace: <TASK> dump_stack_lvl+0x73/0x9f print_report+0x25d/0x759 kasan_report+0xc0/0x120 __asan_load8+0x99/0x140 __list_add_valid+0x28/0x1a0 ext4_orphan_cleanup+0x564/0x9d0 [ext4] __ext4_fill_super+0x48e2/0x5300 [ext4] ext4_fill_super+0x19f/0x3a0 [ext4] get_tree_bdev+0x27b/0x450 ext4_get_tree+0x19/0x30 [ext4] vfs_get_tree+0x49/0x150 path_mount+0xaae/0x1350 do_mount+0xe2/0x110 __x64_sys_mount+0xf0/0x190 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK> [...] ================================================================== Above issue may happen as follows: ------------------------------------- ext4_fill_super ext4_orphan_cleanup --- loop1: assume last_orphan is 12 --- list_add(&EXT4_I(inode)->i_orphan, &EXT4_SB(sb)->s_orphan) ext4_truncate --> return 0 ext4_inode_attach_jinode --> return -ENOMEM iput(inode) --> free inode<12> --- loop2: last_orphan is still 12 --- list_add(&EXT4_I(inode)->i_orphan, &EXT4_SB(sb)->s_orphan); // use inode<12> and trigger UAF To solve this issue, we need to propagate the return value of ext4_inode_attach_jinode() appropriately.. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: ext4: fix use-after-free in ext4_orphan_cleanup I caught a issue as follows: ================================================================== BUG: KASAN: use-after-free in __list_add_valid+0x28/0x1a0 Read of size 8 at addr ffff88814b13f378 by task mount/710 CPU: 1 PID: 710 Comm: mount Not tainted 6.1.0-rc3-next #370 Call Trace: <TASK> dump_stack_lvl+0x73/0x9f print_report+0x25d/0x759 kasan_report+0xc0/0x120 __asan_load8+0x99/0x140 __list_add_valid+0x28/0x1a0 ext4_orphan_cleanup+0x564/0x9d0 [ext4] __ext4_fill_super+0x48e2/0x5300 [ext4] ext4_fill_super+0x19f/0x3a0 [ext4] get_tree_bdev+0x27b/0x450 ext4_get_tree+0x19/0x30 [ext4] vfs_get_tree+0x49/0x150 path_mount+0xaae/0x1350 do_mount+0xe2/0x110 __x64_sys_mount+0xf0/0x190 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK> [...] ================================================================== Above issue may happen as follows: ------------------------------------- ext4_fill_super ext4_orphan_cleanup --- loop1: assume last_orphan is 12 --- list_add(&EXT4_I(inode)->i_orphan, &EXT4_SB(sb)->s_orphan) ext4_truncate --> return 0 ext4_inode_attach_jinode --> return -ENOMEM iput(inode) --> free inode<12> --- loop2: last_orphan is still 12 --- list_add(&EXT4_I(inode)->i_orphan, &EXT4_SB(sb)->s_orphan); // use inode<12> and trigger UAF To solve this issue, we need to propagate the return value of ext4_inode_attach_jinode() appropriately.
Metrics
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13, < 7f801a1593cb957f73659732836b2dafbdfc7709; >= 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13, < 026a4490b5381229a30f23d073b58e8e35ee6858; >= 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13, < 7223d5e75f26352354ea2c0ccf8b579821b52adf; >= 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13, < cf0e0817b0f925b70d101d7014ea81b7094e1159; >= 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13, < c2bdbd4c69308835d1b6f6ba74feeccbfe113478; >= 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13, < 7908b8a541b1578cc61b4da7f19b604a931441da; >= 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13, < a71248b1accb2b42e4980afef4fa4a27fa0e36f5 |
| Linux | Linux | 4.10 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2022-50673?
How severe is CVE-2022-50673?
How do I fix CVE-2022-50673?
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-50667In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50668In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2022-50669In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50670In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50671In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2022-50672In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50674In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50675In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50676In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2022-50677In the Linux kernel, the following vulnerability has been re…7
- CVE-2022-50678In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50679In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2022-50673?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
