CVE-2024-53112: ocfs2: uncache inode which has failed entering the group
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> ? diebody+0x5f/0xb0 ? die+0x9e/0xc0 ? dotrap+0x15a/0x3a0 ? ocfs2setnewbufferuptodate+0x145/0x160 ? doerrortrap+0x1dc/0x2c0 ? ocfs2setnewbufferuptodate+0x145/0x160 ? pfxdoerrortrap+0x10/0x10 ? handleinvalidop+0x34/0x40 ? ocfs2setnewbufferuptodate+0x145/0x160 ? excinvalidop+0x38/0x50 ? asmexcinvalidop+0x1a/0x20 ? ocfs2setnewbufferuptodate+0x2e/0x160 ? ocfs2setnewbufferuptodate+0x144/0x160 ? ocfs2setnewbufferuptodate+0x145/0x160 ocfs2groupadd+0x39f/0x15a0 ? pfxocfs2groupadd+0x10/0x10 ? pfxlockacquire+0x10/0x10 ? mntgetwriteaccess+0x68/0x2b0 ? pfxlockrelease+0x10/0x10 ? rcureadlockanyheld+0xb7/0x160 ? pfxrcureadlockanyheld+0x10/0x10 ? smacklog+0x123/0x540 ? mntgetwriteaccess+0x68/0x2b0 ? mntgetwriteaccess+0x68/0x2b0 ? mntgetwriteaccess+0x226/0x2b0 ocfs2ioctl+0x65e/0x7d0 ? pfxocfs2ioctl+0x10/0x10 ? smackfileioctl+0x29e/0x3a0 ? pfxsmackfileioctl+0x10/0x10 ? lockdephardirqsonprepare+0x43d/0x780 ? pfxlockdephardirqsonprepare+0x10/0x10 ? pfxocfs2ioctl+0x10/0x10 sesysioctl+0xfb/0x170 dosyscall64+0xf3/0x230 entrySYSCALL64afterhwframe+0x77/0x7f ... </TASK>
When 'ioctl(OCFS2IOCGROUPADD, ...)' has failed for the particular inode in 'ocfs2verifygroupandinput()', corresponding buffer head remains cached and subsequent call to the same 'ioctl()' for the same inode issues the BUG() in 'ocfs2setnewbufferuptodate()' (trying to cache the same buffer head of that inode). Fix this by uncaching the buffer head with 'ocfs2removefromcache()' on error path in 'ocfs2groupadd()'.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-53112?
CVE-2024-53112 is classified with high severity due to its potential impact on system stability and security.
How do I fix CVE-2024-53112?
To fix CVE-2024-53112, update your Linux kernel to a version that has addressed the vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-53112?
CVE-2024-53112 affects Linux kernel versions from 2.6.25 to 4.19.325, 4.20 to 6.1.119, 6.2 to 6.6.63, and 6.7 to 6.11.10, along with the 6.12 release candidates.
What is the nature of the vulnerability described in CVE-2024-53112?
CVE-2024-53112 involves an issue in the ocfs2 filesystem that causes the kernel to encounter a bug when an inode fails to enter the group.
Is there a workaround for CVE-2024-53112 until I can apply the fix?
A temporary workaround may include disabling the ocfs2 filesystem, but it is recommended to update to patched versions as soon as possible.