CVE-2022-50277 Details
Description
In the Linux kernel, the following vulnerability has been resolved: ext4: don't allow journal inode to have encrypt flag Mounting a filesystem whose journal inode has the encrypt flag causes a NULL dereference in fscrypt_limit_io_blocks() when the 'inlinecrypt' mount option is used. The problem is that when jbd2_journal_init_inode() calls bmap(), it eventually finds its way into ext4_iomap_begin(), which calls fscrypt_limit_io_blocks(). fscrypt_limit_io_blocks() requires that if the inode is encrypted, then its encryption key must already be set up. That's not the case here, since the journal inode is never "opened" like a normal file would be. Hence the crash. A reproducer is: mkfs.ext4 -F /dev/vdb debugfs -w /dev/vdb -R "set_inode_field <8> flags 0x80808" mount /dev/vdb /mnt -o inlinecrypt To fix this, make ext4 consider journal inodes with the encrypt flag to be invalid. (Note, maybe other flags should be rejected on the journal inode too. For now, this is just the minimal fix for the above issue.) I've marked this as fixing the commit that introduced the call to fscrypt_limit_io_blocks(), since that's what made an actual crash start being possible. But this fix could be applied to any version of ext4 that supports the encrypt feature.
A vulnerability in the ext4 filesystem of the Linux kernel allows a journal inode to have an encryption flag, which can lead to a null pointer dereference. This issue occurs when a filesystem is mounted with the 'inlinecrypt' option and the journal inode is encrypted. The problem arises because the encryption key for the journal inode is not set up, causing a crash when the filesystem operations attempt to access it. This vulnerability affects several versions of the Linux kernel that support the ext4 filesystem and the encryption feature.
The vulnerability has been addressed by modifying the ext4 filesystem to reject journal inodes with the encryption flag. Users should ensure they are using a version of the Linux kernel that includes this fix.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/105c78e12468413e426625831faa7db4284e1fec | kernel.org | Patch |
| https://git.kernel.org/stable/c/1f7a6626f611aa06d7907aa45b484708dd5ac8bc | kernel.org | Patch |
| https://git.kernel.org/stable/c/bcc5057e1781a3ee889225480d995c3b5cbde555 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-476 | NULL Pointer Dereference | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.18, < 6.0.18 >= 6.1, < 6.1.4 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 3, 2025 | Initial Analysis | [email protected] |
| Sep 15, 2025 | New CVE Received | kernel.org |