CVE-2022-50082
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2022
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
ext4: fix warning in ext4_iomap_begin as race between bmap and write
In the Linux kernel, the following vulnerability has been resolved: ext4: fix warning in ext4_iomap_begin as race between bmap and write We got issue as follows: ------------[ cut here ]------------ WARNING: CPU: 3 PID: 9310 at fs/ext4/inode.c:3441 ext4_iomap_begin+0x182/0x5d0 RIP: 0010:ext4_iomap_begin+0x182/0x5d0 RSP: 0018:ffff88812460fa08 EFLAGS: 00010293 RAX: ffff88811f168000 RBX: 0000000000000000 RCX: ffffffff97793c12 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003 RBP: ffff88812c669160 R08: ffff88811f168000 R09: ffffed10258cd20f R10: ffff88812c669077 R11: ffffed10258cd20e R12: 0000000000000001 R13: 00000000000000a4 R14: 000000000000000c R15: ffff88812c6691ee FS: 00007fd0d6ff3740(0000) GS:ffff8883af180000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fd0d6dda290 CR3: 0000000104a62000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: iomap_apply+0x119/0x570 iomap_bmap+0x124/0x150 ext4_bmap+0x14f/0x250 bmap+0x55/0x80 do_vfs_ioctl+0x952/0xbd0 __x64_sys_ioctl+0xc6/0x170 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9 Above issue may happen as follows: bmap write bmap ext4_bmap iomap_bmap ext4_iomap_begin ext4_file_write_iter ext4_buffered_write_iter generic_perform_write ext4_da_write_begin ext4_da_write_inline_data_begin ext4_prepare_inline_data ext4_create_inline_data ext4_set_inode_flag(inode, EXT4_INODE_INLINE_DATA); if (WARN_ON_ONCE(ext4_has_inline_data(inode))) ->trigger bug_on To solved above issue hold inode lock in ext4_bamp.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| ac58e4fb03f9d111d733a4ad379d06eef3a24705 | affected | git | e1682c7171a6c0ff576fe8116b8cba5b8f538b94 | Unavailable | None listed |
| ac58e4fb03f9d111d733a4ad379d06eef3a24705 | affected | git | 30dfb75e1f8645404a536c74d468d498adcd4e74 | Unavailable | None listed |
| ac58e4fb03f9d111d733a4ad379d06eef3a24705 | affected | git | a9fe6d1e3d343d7309f501b1f48020ce7127221f | Unavailable | None listed |
| ac58e4fb03f9d111d733a4ad379d06eef3a24705 | affected | git | fa6482f374fda29a71ad44d76d35b4842d43cda4 | Unavailable | None listed |
| ac58e4fb03f9d111d733a4ad379d06eef3a24705 | affected | git | 51ae846cff568c8c29921b1b28eb2dfbcd4ac12d | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 5.7 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 5.7 | Unavailable | None listed |
| 5.10.137 | unaffected | semver | Unavailable | 5.10.* | None listed |
| 5.15.61 | unaffected | semver | Unavailable | 5.15.* | None listed |
| 5.18.18 | unaffected | semver | Unavailable | 5.18.* | None listed |
| 5.19.2 | unaffected | semver | Unavailable | 5.19.* | None listed |
| 6.0 | unaffected | original_commit_for_fix | Unavailable | * | None listed |