CVE-2026-53039: ocfs2: validate group add input before caching

Published Jun 24, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ocfs2: validate group add input before caching

[BUG] OCFS2IOCGROUPADD can trigger a BUGON in ocfs2setnewbufferuptodate():

kernel BUG at fs/ocfs2/uptodate.c:509! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI RIP: 0010:ocfs2setnewbufferuptodate+0x194/0x1e0 fs/ocfs2/uptodate.c:509 Code: ffffe88f 42b9fe4c 89e64889 dfe8b4df Call Trace: ocfs2groupadd+0x3f1/0x1510 fs/ocfs2/resize.c:507 ocfs2ioctl+0x309/0x6e0 fs/ocfs2/ioctl.c:887 vfsioctl fs/ioctl.c:51 [inline] dosysioctl fs/ioctl.c:597 [inline] sesysioctl fs/ioctl.c:583 [inline] x64sysioctl+0x197/0x1e0 fs/ioctl.c:583 x64syscall+0x1144/0x26a0 arch/x86/include/generated/asm/syscalls64.h:17 dosyscallx64 arch/x86/entry/syscall64.c:63 [inline] dosyscall64+0x93/0xf80 arch/x86/entry/syscall64.c:94 entrySYSCALL64afterhwframe+0x76/0x7e RIP: 0033:0x7bbfb55a966d

[CAUSE] ocfs2groupadd() calls ocfs2setnewbufferuptodate() on a user-controlled group block before ocfs2verifygroupandinput() validates that block number. That helper is only valid for newly allocated metadata and asserts that the block is not already present in the chosen metadata cache. The code also uses INODECACHE(inode) even though the group descriptor belongs to mainbminode and later journal accesses use that cache context instead.

[FIX] Validate the on-disk group descriptor before caching it, then add it to the metadata cache tracked by INODECACHE(mainbminode). Keep the validation failure path separate from the later cleanup path so we only remove the buffer from that cache after it has actually been inserted. This keeps the group buffer lifetime consistent across validation, journaling, and cleanup.

Affected Software

8 affected components
Linux Linux kernel (ocfs2)
Linux Linux kernel>=2.6.25<5.10.258
Linux Linux kernel>=5.11<5.15.209
Linux Linux kernel>=5.16<6.1.175
Linux Linux kernel>=6.2<6.6.141
Linux Linux kernel>=6.7<6.12.91
Linux Linux kernel>=6.13<6.18.33
Linux Linux kernel>=6.19<7.0.10

Event History

Jun 24, 2026
CVE Published
via MITRE·04:29 PM
Data Sourced
via MITRE·04:29 PM
Description
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-53039?

CVE-2026-53039 has a medium severity level of 5.5 as per the CVSS 3.1 assessment.

2

How do I fix CVE-2026-53039?

To resolve CVE-2026-53039, you should apply the available patches as recommended by the Linux kernel.

3

What impact does CVE-2026-53039 have on my system?

CVE-2026-53039 can lead to a kernel panic due to an invalid opcode when triggering certain conditions in the ocfs2 filesystem.

4

Is there a patch available for CVE-2026-53039?

Yes, there is a patch available to fix CVE-2026-53039 in the Linux kernel.

5

Which Linux versions are affected by CVE-2026-53039?

CVE-2026-53039 affects the Linux kernel specifically in the ocfs2 filesystem implementations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203