Home

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.

PUBLISHED Reserved 2025-12-24 | Published 2025-12-24 | Updated 2025-12-24 | Assigner Linux

Product status

Default status
unaffected

1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before 78eba2778ae10fb2a9d450e14d26eb6f6bf1f906
affected

1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before 9d2cad69547abea961fa80426d600b861de1952b
affected

1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before d6da7ec0f94f5208c848e0e94b70f54a0bd9c587
affected

1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before 156d440dea97deada629bb51cb17887abd862605
affected

1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before 40dba68d418237b1ae2beaa06d46a94dd946278e
affected

1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before e7a6a53c871460727be09f4414ccb29fb8697526
affected

1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before 4fca09045509f5bde8fc28e68fbca38cb4bdcf2e
affected

1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before 090bf49833c51da297ec74f98ad2bf44daea9311
affected

1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (git) before c791730f2554a9ebb8f18df9368dc27d4ebc38c2
affected

Default status
affected

4.9.337 (semver)
unaffected

4.14.303 (semver)
unaffected

4.19.270 (semver)
unaffected

5.4.229 (semver)
unaffected

5.10.163 (semver)
unaffected

5.15.86 (semver)
unaffected

6.0.16 (semver)
unaffected

6.1.2 (semver)
unaffected

6.2 (original_commit_for_fix)
unaffected

References

git.kernel.org/...c/78eba2778ae10fb2a9d450e14d26eb6f6bf1f906

git.kernel.org/...c/9d2cad69547abea961fa80426d600b861de1952b

git.kernel.org/...c/d6da7ec0f94f5208c848e0e94b70f54a0bd9c587

git.kernel.org/...c/156d440dea97deada629bb51cb17887abd862605

git.kernel.org/...c/40dba68d418237b1ae2beaa06d46a94dd946278e

git.kernel.org/...c/e7a6a53c871460727be09f4414ccb29fb8697526

git.kernel.org/...c/4fca09045509f5bde8fc28e68fbca38cb4bdcf2e

git.kernel.org/...c/090bf49833c51da297ec74f98ad2bf44daea9311

git.kernel.org/...c/c791730f2554a9ebb8f18df9368dc27d4ebc38c2

cve.org (CVE-2022-50755)

nvd.nist.gov (CVE-2022-50755)

Download JSON

Data based on CVE®. Copyright © 1999-2025, The MITRE Corporation. All rights reserved.