ext4: fix i_data_sem unlock order in ext4_ind_migrate()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e8238f9a8339b3578c85e4192a7a23bc2bdc0333 · < d43776b907659affef1de888525847d64b244194| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ext4: fix i_data_sem unlock order in ext4_ind_migrate()
Fuzzing reports a possible deadlock in jbd2_log_wait_commit.
This issue is triggered when an EXT4_IOC_MIGRATE ioctl is set to require synchronous updates because the file descriptor is opened with O_SYNC. This can lead to the jbd2_journal_stop() function calling jbd2_might_wait_for_commit(), potentially causing a deadlock if the EXT4_IOC_MIGRATE call races with a write(2) system call.
This problem only arises when CONFIG_PROVE_LOCKING is enabled. In this case, the jbd2_might_wait_for_commit macro locks jbd2_handle in the jbd2_journal_stop function while i_data_sem is locked. This triggers lockdep because the jbd2_journal_start function might also lock the same jbd2_handle simultaneously.
Found by Linux Verification Center (linuxtesting.org) with syzkaller.
Rule: add
From the CVE record · Linux
A locking-order issue in the Linux kernel's ext4 migration path can cause a possible deadlock. It requires CONFIG_PROVE_LOCKING to be enabled and an EXT4_IOC_MIGRATE call on a file descriptor opened with O_SYNC to race with a write(2) call. The input does not specify authentication requirements.
Engineers running Linux kernels with CONFIG_PROVE_LOCKING enabled should check their ext4 installations; affected versions are not specified.