CVE-2022-50755
Last modified
CVE-2022-50755 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: udf: Avoid double brelse() in udf_rename() syzbot reported a warning like below [1]: VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0 ... Call Trace: <TASK> invalidate_bh_lru+0x99/0x150 smp_call_function_many_cond+0xe2a/0x10c0 ? generic_remap_file_range_prep+0x50/0x50 ? __brelse+0xa0/0xa0 ? __mutex_lock+0x21c/0x12d0 ? smp_call_on_cpu+0x250/0x250 ? rcu_read_lock_sched_held+0xb/0x60 ? lock_release+0x587/0x810 ? __brelse+0xa0/0xa0 ? generic_remap_file_range_prep+0x50/0x50 on_each_cpu_cond_mask+0x3c/0x80 blkdev_flush_mapping+0x13a/0x2f0 blkdev_put_whole+0xd3/0xf0 blkdev_put+0x222/0x760 deactivate_locked_super+0x96/0x160 deactivate_super+0xda/0x100 cleanup_mnt+0x222/0x3d0 task_work_run+0x149/0x240 ? task_work_cancel+0x30/0x30 do_exit+0xb29/0x2a40 ? reacquire_held_locks+0x4a0/0x4a0 ? do_raw_spin_lock+0x12a/0x2b0 ? mm_update_next_owner+0x7c0/0x7c0 ? rwlock_bug.part.0+0x90/0x90 ? zap_other_threads+0x234/0x2d0 do_group_exit+0xd0/0x2a0 __x64_sys_exit_group+0x3a/0x50 do_syscall_64+0x34/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd The cause of the issue is that brelse() is called on both ofibh.sbh and ofibh.ebh by udf_find_entry() when it returns NULL. However, brelse() is called by udf_rename(), too. EPSS estimates a 0.25% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: udf: Avoid double brelse() in udf_rename() syzbot reported a warning like below [1]: VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0 ... Call Trace: <TASK> invalidate_bh_lru+0x99/0x150 smp_call_function_many_cond+0xe2a/0x10c0 ? generic_remap_file_range_prep+0x50/0x50 ? __brelse+0xa0/0xa0 ? __mutex_lock+0x21c/0x12d0 ? smp_call_on_cpu+0x250/0x250 ? rcu_read_lock_sched_held+0xb/0x60 ? lock_release+0x587/0x810 ? __brelse+0xa0/0xa0 ? generic_remap_file_range_prep+0x50/0x50 on_each_cpu_cond_mask+0x3c/0x80 blkdev_flush_mapping+0x13a/0x2f0 blkdev_put_whole+0xd3/0xf0 blkdev_put+0x222/0x760 deactivate_locked_super+0x96/0x160 deactivate_super+0xda/0x100 cleanup_mnt+0x222/0x3d0 task_work_run+0x149/0x240 ? task_work_cancel+0x30/0x30 do_exit+0xb29/0x2a40 ? reacquire_held_locks+0x4a0/0x4a0 ? do_raw_spin_lock+0x12a/0x2b0 ? mm_update_next_owner+0x7c0/0x7c0 ? rwlock_bug.part.0+0x90/0x90 ? zap_other_threads+0x234/0x2d0 do_group_exit+0xd0/0x2a0 __x64_sys_exit_group+0x3a/0x50 do_syscall_64+0x34/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd The cause of the issue is that brelse() is called on both ofibh.sbh and ofibh.ebh by udf_find_entry() when it returns NULL. However, brelse() is called by udf_rename(), too. So, b_count on buffer_head becomes unbalanced. This patch fixes the issue by not calling brelse() by udf_rename() when udf_find_entry() returns NULL.
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 | >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31, < 78eba2778ae10fb2a9d450e14d26eb6f6bf1f906; >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31, < 9d2cad69547abea961fa80426d600b861de1952b; >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31, < d6da7ec0f94f5208c848e0e94b70f54a0bd9c587; >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31, < 156d440dea97deada629bb51cb17887abd862605; >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31, < 40dba68d418237b1ae2beaa06d46a94dd946278e; >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31, < e7a6a53c871460727be09f4414ccb29fb8697526; >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31, < 4fca09045509f5bde8fc28e68fbca38cb4bdcf2e; >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31, < 090bf49833c51da297ec74f98ad2bf44daea9311; >= 231473f6ddcef9c01993e0bfe36acc6f8e425c31, < c791730f2554a9ebb8f18df9368dc27d4ebc38c2 |
| Linux | Linux | 4.2 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2022-50755?
How severe is CVE-2022-50755?
How do I fix CVE-2022-50755?
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-50749In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50750In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50751In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50752In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50753In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50754In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50756In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50757In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50758In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50759In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50760In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50761In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2022-50755?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
