Answer in brief
CVE-2022-50428 records a Medium severity (CVSS 5.5) vulnerability in ext4: fix off-by-one errors in fast-commit block filling. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=aa75f4d3daaeb1389b9cce9d6b84401eaf228d4e <18f28f13301d1afb8cea9c4ddcecdbff14488ec6 || >=aa75f4d3daaeb1389b9cce9d6b84401eaf228d4e <5ca65dffdead16572ca046c43fb576b227f7f635 || >=aa75f4d3daaeb1389b9cce9d6b84401eaf228d4e <5439ad45c0d0c8db41eb6f4dce6f778f15a5ee16 || >=aa75f4d3daaeb1389b9cce9d6b84401eaf228d4e <48a6a66db82b8043d298a630f22c62d43550cae5 | 18f28f13301d1afb8cea9c4ddcecdbff14488ec6, 5ca65dffdead16572ca046c43fb576b227f7f635, 5439ad45c0d0c8db41eb6f4dce6f778f15a5ee16, 48a6a66db82b8043d298a630f22c62d43550cae5 |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Oct 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.