ext4: update s_journal_inum if it changes after journal replay
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ext4: update s_journal_inum if it changes after journal replay
When mounting a crafted ext4 image, s_journal_inum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the journal through the old s_journal_inum. And the new s_journal_inum bypasses some of the checks in ext4_get_journal(), which may trigger a null pointer dereference problem. So if s_journal_inum changes after the journal replay, we ignore the change, and rewrite the current journal_inum to the superblock.
From the CVE record · Linux
The Linux kernel’s ext4 filesystem may use an unchecked journal inode number after replaying the journal on a crafted ext4 image. An attacker who can cause that image to be mounted may trigger a null pointer dereference.
Anyone running the Linux kernel with ext4 support should check whether their kernel includes the fix; affected versions were not provided.