Riskcovery

CVE-2025-38337

jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata()

State
Published
Severity
Not scored
Published
Jul 10, 2025
Updated
May 11, 2026
Reserved
Apr 16, 2025

Read the record on cve.org

Description

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

jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata()

Since handle->h_transaction may be a NULL pointer, so we should change it to call is_handle_aborted(handle) first before dereferencing it.

And the following data-race was reported in my fuzzer:

================================================================== BUG: KCSAN: data-race in jbd2_journal_dirty_metadata / jbd2_journal_dirty_metadata

write to 0xffff888011024104 of 4 bytes by task 10881 on cpu 1: jbd2_journal_dirty_metadata+0x2a5/0x770 fs/jbd2/transaction.c:1556 __ext4_handle_dirty_metadata+0xe7/0x4b0 fs/ext4/ext4_jbd2.c:358 ext4_do_update_inode fs/ext4/inode.c:5220 [inline] ext4_mark_iloc_dirty+0x32c/0xd50 fs/ext4/inode.c:5869 __ext4_mark_inode_dirty+0xe1/0x450 fs/ext4/inode.c:6074 ext4_dirty_inode+0x98/0xc0 fs/ext4/inode.c:6103 ....

read to 0xffff888011024104 of 4 bytes by task 10880 on cpu 0: jbd2_journal_dirty_metadata+0xf2/0x770 fs/jbd2/transaction.c:1512 __ext4_handle_dirty_metadata+0xe7/0x4b0 fs/ext4/ext4_jbd2.c:358 ext4_do_update_inode fs/ext4/inode.c:5220 [inline] ext4_mark_iloc_dirty+0x32c/0xd50 fs/ext4/inode.c:5869 __ext4_mark_inode_dirty+0xe1/0x450 fs/ext4/inode.c:6074 ext4_dirty_inode+0x98/0xc0 fs/ext4/inode.c:6103 ....

value changed: 0x00000000 -> 0x00000001 ==================================================================

This issue is caused by missing data-race annotation for jh->b_modified. Therefore, the missing annotation needs to be added.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 6e06ae88edae77379bef7c0cb7d3c2dd88676867 to before 5c1a34ff5b0bfdfd2f9343aa9b08d25df618bac5Affected
  • 6e06ae88edae77379bef7c0cb7d3c2dd88676867 to before ec669e5bf409f16e464bfad75f0ba039a45de29aAffected
  • 6e06ae88edae77379bef7c0cb7d3c2dd88676867 to before 43d5e3bb5f1dcd91e30238ea0b59a5f77063f84eAffected
  • 6e06ae88edae77379bef7c0cb7d3c2dd88676867 to before 23361b479f2700c00960d3ae9cdc8ededa762d47Affected
  • 6e06ae88edae77379bef7c0cb7d3c2dd88676867 to before 2e7c64d7a92c031d016f11c8e8cb05131ab7b75aAffected
  • 6e06ae88edae77379bef7c0cb7d3c2dd88676867 to before f78b38af3540b4875147b7b884ee11a27b3dbf4cAffected
  • 6e06ae88edae77379bef7c0cb7d3c2dd88676867 to before a377996d714afb8d4d5f4906336f78510039da29Affected
  • 6e06ae88edae77379bef7c0cb7d3c2dd88676867 to before af98b0157adf6504fade79b3e6cb260c4ff68e37Affected
LinuxLinux
  • 4.3Affected
  • before 4.3Not affected
  • 5.4.295 through 5.4.*Not affected
  • 5.10.239 through 5.10.*Not affected
  • 5.15.186 through 5.15.*Not affected
  • 6.1.142 through 6.1.*Not affected
  • 6.6.95 through 6.6.*Not affected
  • 6.12.35 through 6.12.*Not affected
  • 6.15.4 through 6.15.*Not affected
  • 6.16 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.