CVE-2022-50428
published 2025-10-01CVE-2022-50428: 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…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.15%
4.4th percentile
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.
Affected
12 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.4-1 (bookworm) | linux 6.1.4-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= aa75f4d3daaeb1389b9cce9d6b84401eaf228d4e < 18f28f13301d1afb8cea9c4ddcecdbff14488ec6 | 18f28f13301d1afb8cea9c4ddcecdbff14488ec6 |
| linux | linux | >= aa75f4d3daaeb1389b9cce9d6b84401eaf228d4e < 5ca65dffdead16572ca046c43fb576b227f7f635 | 5ca65dffdead16572ca046c43fb576b227f7f635 |
| linux | linux | >= aa75f4d3daaeb1389b9cce9d6b84401eaf228d4e < 5439ad45c0d0c8db41eb6f4dce6f778f15a5ee16 | 5439ad45c0d0c8db41eb6f4dce6f778f15a5ee16 |
| linux | linux | >= aa75f4d3daaeb1389b9cce9d6b84401eaf228d4e < 48a6a66db82b8043d298a630f22c62d43550cae5 | 48a6a66db82b8043d298a630f22c62d43550cae5 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 5.10 < 5.15.87 | 5.15.87 |
| linux | linux_kernel | >= 5.16 < 6.0.18 | 6.0.18 |
| linux | linux_kernel | >= 6.1 < 6.1.4 | 6.1.4 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-362x-q9rc-h58c: In the Linux kernel, the following vulnerability has been resolved:
ext4: fix off-by-one errors in fast-commit block filling
Due to several differen
ghsa_unreviewed·2025-10-01
CVE-2022-50428 [MEDIUM] CWE-193 GHSA-362x-q9rc-h58c: In the Linux kernel, the following vulnerability has been resolved:
ext4: fix off-by-one errors in fast-commit block filling
Due to several differen
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
OSV
CVE-2022-50428: 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
osv·2025-10-01·CVSS 5.5
CVE-2022-50428 [MEDIUM] CVE-2022-50428: 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
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 the
Red Hat
kernel: ext4: fix off-by-one errors in fast-commit block filling
vendor_redhat·2025-10-01·CVSS 5.5
CVE-2022-50428 [MEDIUM] kernel: ext4: fix off-by-one errors in fast-commit block filling
kernel: ext4: fix off-by-one errors in fast-commit block filling
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
Debian
CVE-2022-50428: linux - In the Linux kernel, the following vulnerability has been resolved: ext4: fix o...
vendor_debian·2022·CVSS 5.5
CVE-2022-50428 [MEDIUM] CVE-2022-50428: linux - In the Linux kernel, the following vulnerability has been resolved: ext4: fix o...
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 the
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2022-50428 kernel: ext4: fix off-by-one errors in fast-commit block filling
bugzilla·2025-10-01·CVSS 5.5
CVE-2022-50428 [MEDIUM] CVE-2022-50428 kernel: ext4: fix off-by-one errors in fast-commit block filling
CVE-2022-50428 kernel: ext4: fix off-by-one errors in fast-commit block filling
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
Bugzilla
CVE-2022-40155 xstream: Xstream to serialise XML data was vulnerable to Denial of Service attacks
bugzilla·2022-10-13
CVE-2022-40155 [MEDIUM] CVE-2022-40155 xstream: Xstream to serialise XML data was vulnerable to Denial of Service attacks
CVE-2022-40155 xstream: Xstream to serialise XML data was vulnerable to Denial of Service attacks
Those using Xstream to serialise XML data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack overflow. This effect may support a denial of service attack.
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50428
https://github.com/x-stream/xstream/issues/304
Discussion:
Created xstream tracking bugs for this issue:
Affects: epel-all [bug 2134299]
Affects: fedora-all [bug 2134300]
---
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):
https://access.redhat.com/security/cve/cve-2022-40155
---
This issue has bee
2025-10-01
Published