CVE-2023-53564
ocfs2: fix defrag path triggering jbd2 ASSERT
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix defrag path triggering jbd2 ASSERT code path: ocfs2_ioctl_move_extents ocfs2_move_extents ocfs2_defrag_extent __ocfs2_move_extent + ocfs2_journal_access_di + ocfs2_split_extent //sub-paths call jbd2_journal_restart + ocfs2_journal_dirty //crash by jbs2 ASSERT crash stacks: PID: 11297 TASK: ffff974a676dcd00 CPU: 67 COMMAND: "defragfs.ocfs2" #0 [ffffb25d8dad3900] machine_kexec at ffffffff8386fe01 #1 [ffffb25d8dad3958] __crash_kexec at ffffffff8395959d #2 [ffffb25d8dad3a20] crash_kexec at ffffffff8395a45d #3 [ffffb25d8dad3a38] oops_end at ffffffff83836d3f #4 [ffffb25d8dad3a58] do_trap at ffffffff83833205 #5 [ffffb25d8dad3aa0] do_invalid_op at ffffffff83833aa6 #6 [ffffb25d8dad3ac0] invalid_op at ffffffff84200d18 [exception RIP: jbd2_journal_dirty_metadata+0x2ba] RIP: ffffffffc09ca54a RSP: ffffb25d8dad3b70 RFLAGS: 00010207 RAX: 0000000000000000 RBX: ffff9706eedc5248 RCX: 0000000000000000 RDX: 0000000000000001 RSI: ffff97337029ea28 RDI: ffff9706eedc5250 RBP: ffff9703c3520200 R8: 000000000f46b0b2 R9: 0000000000000000 R10: 0000000000000001 R11: 00000001000000fe R12: ffff97337029ea28 R13: 0000000000000000 R14: ffff9703de59bf60 R15: ffff9706eedc5250 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #7 [ffffb25d8dad3ba8] ocfs2_journal_dirty at ffffffffc137fb95 [ocfs2] #8 [ffffb25d8dad3be8] __ocfs2_move_extent at ffffffffc139a950 [ocfs2] #9 [ffffb25d8dad3c80] ocfs2_defrag_extent at ffffffffc139b2d2 [ocfs2] Analysis This bug has the same root cause of 'commit 7f27ec978b0e ("ocfs2: call ocfs2_journal_access_di() before ocfs2_journal_dirty() in ocfs2_write_end_nolock()")'. For this bug, jbd2_journal_restart() is called by ocfs2_split_extent() during defragmenting. How to fix For ocfs2_split_extent() can handle journal operations totally by itself. Caller doesn't need to call journal access/dirty pair, and caller only needs to call journal start/stop pair. The fix method is to remove journal access/dirty from __ocfs2_move_extent(). The discussion for this patch: https://oss.oracle.com/pipermail/ocfs2-devel/2023-February/000647.html
Timeline
ID reserved
By Linux
Published
- 7 months later
· 7 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.15% · top 96% of all CVEs (7 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Weakness
Affected products
- affected 8f603e567aa7a243e68ca48b4f105b990851360f – < 5f43d34a51ed30e6a60f7e59d224a63014fe2cd5
- affected 8f603e567aa7a243e68ca48b4f105b990851360f – < 7f3b1c28e2908755fb248d3ee8ff56826f2387db
- affected 8f603e567aa7a243e68ca48b4f105b990851360f – < 669134a66d37258e1c4a5cfbd5b82f547ae30fca
- affected 8f603e567aa7a243e68ca48b4f105b990851360f – < 2c559b3ba8e0b9e3c4bb08159a28ccadc698410f
- affected 8f603e567aa7a243e68ca48b4f105b990851360f – < 33665d1042666f2e5c736a3df1f453e31f030663
- affected 8f603e567aa7a243e68ca48b4f105b990851360f – < 8163ea90d89b7012dd1fa4b28edf5db0c641eca7
- affected 8f603e567aa7a243e68ca48b4f105b990851360f – < 590507ebabd33cd93324c04f9a5538309a5ba934
- affected 8f603e567aa7a243e68ca48b4f105b990851360f – < 60eed1e3d45045623e46944ebc7c42c30a4350f0
- affected 3.0
- unaffected < 3.0
- unaffected 4.14.308 – ≤ 4.14.*
- unaffected 4.19.276 – ≤ 4.19.*
- unaffected 5.4.235 – ≤ 5.4.*
- unaffected 5.10.173 – ≤ 5.10.*
- unaffected 5.15.99 – ≤ 5.15.*
- unaffected 6.1.16 – ≤ 6.1.*
- unaffected 6.2.3 – ≤ 6.2.*
- unaffected 6.3 – ≤ *
References (8)
- https://git.kernel.org/stable/c/5f43d34a51ed30e6a60f7e59d224a63014fe2cd5 (opens in a new tab)
- https://git.kernel.org/stable/c/7f3b1c28e2908755fb248d3ee8ff56826f2387db (opens in a new tab)
- https://git.kernel.org/stable/c/669134a66d37258e1c4a5cfbd5b82f547ae30fca (opens in a new tab)
- https://git.kernel.org/stable/c/2c559b3ba8e0b9e3c4bb08159a28ccadc698410f (opens in a new tab)
- https://git.kernel.org/stable/c/33665d1042666f2e5c736a3df1f453e31f030663 (opens in a new tab)
- https://git.kernel.org/stable/c/8163ea90d89b7012dd1fa4b28edf5db0c641eca7 (opens in a new tab)
- https://git.kernel.org/stable/c/590507ebabd33cd93324c04f9a5538309a5ba934 (opens in a new tab)
- https://git.kernel.org/stable/c/60eed1e3d45045623e46944ebc7c42c30a4350f0 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2023-53564)Record last updated .