CVE-2024-53112

ocfs2: uncache inode which has failed entering the group

MEDIUM
5.5
CVSS Score
Published: December 2, 2024 at 01:44 PM UTC
Updated: June 17, 2026 at 08:08 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: uncache inode which has failed entering the group Syzbot has reported the following BUG: kernel BUG at fs/ocfs2/uptodate.c:509! ... Call Trace: <TASK> ? __die_body+0x5f/0xb0 ? die+0x9e/0xc0 ? do_trap+0x15a/0x3a0 ? ocfs2_set_new_buffer_uptodate+0x145/0x160 ? do_error_trap+0x1dc/0x2c0 ? ocfs2_set_new_buffer_uptodate+0x145/0x160 ? __pfx_do_error_trap+0x10/0x10 ? handle_invalid_op+0x34/0x40 ? ocfs2_set_new_buffer_uptodate+0x145/0x160 ? exc_invalid_op+0x38/0x50 ? asm_exc_invalid_op+0x1a/0x20 ? ocfs2_set_new_buffer_uptodate+0x2e/0x160 ? ocfs2_set_new_buffer_uptodate+0x144/0x160 ? ocfs2_set_new_buffer_uptodate+0x145/0x160 ocfs2_group_add+0x39f/0x15a0 ? __pfx_ocfs2_group_add+0x10/0x10 ? __pfx_lock_acquire+0x10/0x10 ? mnt_get_write_access+0x68/0x2b0 ? __pfx_lock_release+0x10/0x10 ? rcu_read_lock_any_held+0xb7/0x160 ? __pfx_rcu_read_lock_any_held+0x10/0x10 ? smack_log+0x123/0x540 ? mnt_get_write_access+0x68/0x2b0 ? mnt_get_write_access+0x68/0x2b0 ? mnt_get_write_access+0x226/0x2b0 ocfs2_ioctl+0x65e/0x7d0 ? __pfx_ocfs2_ioctl+0x10/0x10 ? smack_file_ioctl+0x29e/0x3a0 ? __pfx_smack_file_ioctl+0x10/0x10 ? lockdep_hardirqs_on_prepare+0x43d/0x780 ? __pfx_lockdep_hardirqs_on_prepare+0x10/0x10 ? __pfx_ocfs2_ioctl+0x10/0x10 __se_sys_ioctl+0xfb/0x170 do_syscall_64+0xf3/0x230 entry_SYSCALL_64_after_hwframe+0x77/0x7f ... </TASK> When 'ioctl(OCFS2_IOC_GROUP_ADD, ...)' has failed for the particular inode in 'ocfs2_verify_group_and_input()', corresponding buffer head remains cached and subsequent call to the same 'ioctl()' for the same inode issues the BUG() in 'ocfs2_set_new_buffer_uptodate()' (trying to cache the same buffer head of that inode). Fix this by uncaching the buffer head with 'ocfs2_remove_from_cache()' on error path in 'ocfs2_group_add()'.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.25 ≤ v < 4.19.3252.6.25 ≤ v < 5.10.2312.6.25 ≤ v < 5.15.1742.6.25 ≤ v < 5.4.2872.6.25 ≤ v < 6.1.1192.6.25 ≤ v < 6.11.102.6.25 ≤ v < 6.122.6.25 ≤ v < 6.6.634.20 ≤ v < 6.1.1196.2 ≤ v < 6.6.636.7 ≤ v < 6.11.106.12 rc16.12 rc26.12 rc36.12 rc46.12 rc56.12 rc66.12 rc77909f2bf835376a20d6dbf853eb459a27566eba2
Vendor states this is fixed in 0e04746db2ec4aec04cef5763b9d9aa32829ae2f (fixed)
Vendor states this is fixed in 28d4ed71ae0b4baedca3e85ee6d8f227ec75ebf6 (fixed)
Vendor states this is fixed in 5ae8cc0b0c027e9cab22596049bc4dd1cbc37ee4 (fixed)
Vendor states this is fixed in 620d22598110b0d0cb97a3fcca65fc473ea86e73 (fixed)
Vendor states this is fixed in 737f34137844d6572ab7d473c998c7f977ff30eb (fixed)
Vendor states this is fixed in 843dfc804af4b338ead42331dd58081b428ecdf8 (fixed)
Vendor states this is fixed in ac0cfe8ac35cf1be54131b90d114087b558777ca (fixed)
Vendor states this is fixed in b751c50e19d66cfb7360c0b55cf17b0722252d12 (fixed)
Vendor states this is fixed in 2.6.25 (unaffected)
Vendor states this is fixed in 4.19.325 (unaffected)
Vendor states this is fixed in 5.10.231 (unaffected)
Vendor states this is fixed in 5.15.174 (unaffected)
Vendor states this is fixed in 5.4.287 (unaffected)
Vendor states this is fixed in 6.1.119 (unaffected)
Vendor states this is fixed in 6.11.10 (unaffected)
Vendor states this is fixed in 6.12 (unaffected)
Vendor states this is fixed in 6.6.63 (unaffected)

References (10)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card