🛡️ CVE-2022-50277 on Debian — linux
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.
Distribution advisory
This page covers CVE-2022-50277 as tracked by Debian, for the package linux. The fix is available in version 6.1.4-1; earlier versions remain affected.
How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.
Affected software
DEBIAN-CVE-2022-50277 is recorded against 1 package.
- linux (fixed in 6.1.4-1)
Timeline and source
Published on 15 September 2025 and last revised on 4 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
CVE-2022-50277 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| linux | — | 6.1.4-1 |
References
Similar Threats
- Unknown CGA-23jx-hhcx-m389
- Unknown CGA-2qp7-6757-fmgc
- Unknown CGA-2rj5-jc55-r267
- Unknown CGA-3m96-cwq8-6xmx
- Unknown CGA-3qj9-973w-fh9g
More DEBIAN CVE 2022 advisories
Browse all of DEBIAN CVE 2022 in the advisory index.
- DEBIAN-CVE-2022-50269
- DEBIAN-CVE-2022-50270
- DEBIAN-CVE-2022-50271
- DEBIAN-CVE-2022-50272
- DEBIAN-CVE-2022-50273
- DEBIAN-CVE-2022-50274
- DEBIAN-CVE-2022-50275
- DEBIAN-CVE-2022-50276
- DEBIAN-CVE-2022-50278
- DEBIAN-CVE-2022-50279
- DEBIAN-CVE-2022-50280
- DEBIAN-CVE-2022-50281
- DEBIAN-CVE-2022-50282
- DEBIAN-CVE-2022-50283
- DEBIAN-CVE-2022-50284
- DEBIAN-CVE-2022-50285
Vulnerability Monitoring
Track new vulnerabilities in linux
DEBIAN-CVE-2022-50277 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.