CVE-2022-50428 Details
Description
In the Linux kernel, the following vulnerability has been resolved: ext4: fix off-by-one errors in fast-commit block filling Due to several different off-by-one errors, or perhaps due to a late change in design that wasn't fully reflected in the code that was actually merged, there are several very strange constraints on how fast-commit blocks are filled with tlv entries: - tlvs must start at least 10 bytes before the end of the block, even though the minimum tlv length is 8. Otherwise, the replay code will ignore them. (BUG: ext4_fc_reserve_space() could violate this requirement if called with a len of blocksize - 9 or blocksize - 8. Fortunately, this doesn't seem to happen currently.) - tlvs must end at least 1 byte before the end of the block. Otherwise the replay code will consider them to be invalid. This quirk contributed to a bug (fixed by an earlier commit) where uninitialized memory was being leaked to disk in the last byte of blocks. Also, strangely these constraints don't apply to the replay code in e2fsprogs, which will accept any tlvs in the blocks (with no bounds checks at all, but that is a separate issue...). Given that this all seems to be a bug, let's fix it by just filling blocks with tlv entries in the natural way. Note that old kernels will be unable to replay fast-commit journals created by kernels that have this commit.
An off-by-one vulnerability has been identified in the Linux kernel's ext4 file system, specifically in how fast-commit blocks are populated with TLV (Type-Length-Value) entries. This issue arises from several off-by-one errors or a design change that was not properly implemented in the merged code. As a result, there are unusual constraints on filling fast-commit blocks: TLVs must start at least 10 bytes from the block's end, despite a minimum TLV length of 8 bytes, or the replay code will disregard them. Additionally, TLVs must finish at least 1 byte before the block's end, as the replay code will consider them invalid, leading to a previous bug where uninitialized memory was inadvertently written to disk.
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.
CISA-ADP
Assessed Nov 5, 2026References 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/18f28f13301d1afb8cea9c4ddcecdbff14488ec6 | kernel.org | Patch |
| https://git.kernel.org/stable/c/48a6a66db82b8043d298a630f22c62d43550cae5 | kernel.org | Patch |
| https://git.kernel.org/stable/c/5439ad45c0d0c8db41eb6f4dce6f778f15a5ee16 | kernel.org | Patch |
| https://git.kernel.org/stable/c/5ca65dffdead16572ca046c43fb576b227f7f635 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-193 | Off-by-one Error | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.10, < 5.15.87 >= 5.16, < 6.0.18 >= 6.1, < 6.1.4 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | kernel.org |
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jan 20, 2026 | Initial Analysis | [email protected] |
| Oct 1, 2025 | New CVE Received | kernel.org |