CVE-2023-53091
published 2025-05-02CVE-2023-53091: In the Linux kernel, the following vulnerability has been resolved: ext4: update s_journal_inum if it changes after journal replay When mounting a crafted ext4…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.20%
10.2th percentile
In the Linux kernel, the following vulnerability has been resolved:
ext4: update s_journal_inum if it changes after journal replay
When mounting a crafted ext4 image, s_journal_inum may change after journal
replay, which is obviously unreasonable because we have successfully loaded
and replayed the journal through the old s_journal_inum. And the new
s_journal_inum bypasses some of the checks in ext4_get_journal(), which
may trigger a null pointer dereference problem. So if s_journal_inum
changes after the journal replay, we ignore the change, and rewrite the
current journal_inum to the superblock.
Affected
22 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.25-1 (bookworm) | linux 6.1.25-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 3.16.85 < 3.17 | 3.17 |
| linux | linux | >= 345c0dbf3a30872d9b204db96b5857cd00808cae < 499fef2030fb754c68b1c7cb3a799a3bc1d0d925 | 499fef2030fb754c68b1c7cb3a799a3bc1d0d925 |
| linux | linux | >= 345c0dbf3a30872d9b204db96b5857cd00808cae < 70e66bdeae4d0f7c8e87762f425b68aedd5e8955 | 70e66bdeae4d0f7c8e87762f425b68aedd5e8955 |
| linux | linux | >= 345c0dbf3a30872d9b204db96b5857cd00808cae < ee0c5277d4fab920bd31345c49e193ecede9ecef | ee0c5277d4fab920bd31345c49e193ecede9ecef |
| linux | linux | >= 345c0dbf3a30872d9b204db96b5857cd00808cae < 3039d8b8692408438a618fac2776b629852663c3 | 3039d8b8692408438a618fac2776b629852663c3 |
| linux | linux | >= 4.14.178 < 4.15 | 4.15 |
| linux | linux | >= 4.19.73 < 4.20 | 4.20 |
| linux | linux | >= 4.4.221 < 4.5 | 4.5 |
| linux | linux | >= 4.9.221 < 4.10 | 4.10 |
| linux | linux_kernel | < 5.15.104 | 5.15.104 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 5.16 < 6.1.21 | 6.1.21 |
| linux | linux_kernel | >= 6.2 < 6.2.8 | 6.2.8 |
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.
Red Hat
kernel: ext4: update s_journal_inum if it changes after journal replay
vendor_redhat·2025-05-02·CVSS 5.5
CVE-2023-53091 [MEDIUM] kernel: ext4: update s_journal_inum if it changes after journal replay
kernel: ext4: update s_journal_inum if it changes after journal replay
In the Linux kernel, the following vulnerability has been resolved:
ext4: update s_journal_inum if it changes after journal replay
When mounting a crafted ext4 image, s_journal_inum may change after journal
replay, which is obviously unreasonable because we have successfully loaded
and replayed the journal through the old s_journal_inum. And the new
s_journal_inum bypasses some of the checks in ext4_get_journal(), which
may trigger a null pointer dereference problem. So if s_journal_inum
changes after the journal replay, we ignore the change, and rewrite the
current journal_inum to the superblock.
Statement: This issue can only be triggered by mounting a maliciously crafted ext4 image with an inconsistent journal stat
Debian
CVE-2023-53091: linux - In the Linux kernel, the following vulnerability has been resolved: ext4: updat...
vendor_debian·2023·CVSS 5.5
CVE-2023-53091 [MEDIUM] CVE-2023-53091: linux - In the Linux kernel, the following vulnerability has been resolved: ext4: updat...
In the Linux kernel, the following vulnerability has been resolved: ext4: update s_journal_inum if it changes after journal replay When mounting a crafted ext4 image, s_journal_inum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the journal through the old s_journal_inum. And the new s_journal_inum bypasses some of the checks in ext4_get_journal(), which may trigger a null pointer dereference problem. So if s_journal_inum changes after the journal replay, we ignore the change, and rewrite the current journal_inum to the superblock.
Scope: local
bookworm: resolved (fixed in 6.1.25-1)
bullseye: open
forky: resolved (fixed in 6.1.25-1)
sid: resolved (fixed in 6.1.25-1)
trixie: resolved (fixed in 6.1.25-1)
OSV
CVE-2023-53091: In the Linux kernel, the following vulnerability has been resolved: ext4: update s_journal_inum if it changes after journal replay When mounting a cra
osv·2025-05-02·CVSS 5.5
CVE-2023-53091 [MEDIUM] CVE-2023-53091: In the Linux kernel, the following vulnerability has been resolved: ext4: update s_journal_inum if it changes after journal replay When mounting a cra
In the Linux kernel, the following vulnerability has been resolved: ext4: update s_journal_inum if it changes after journal replay When mounting a crafted ext4 image, s_journal_inum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the journal through the old s_journal_inum. And the new s_journal_inum bypasses some of the checks in ext4_get_journal(), which may trigger a null pointer dereference problem. So if s_journal_inum changes after the journal replay, we ignore the change, and rewrite the current journal_inum to the superblock.
GHSA
GHSA-ghqh-9ppg-g8cf: In the Linux kernel, the following vulnerability has been resolved:
ext4: update s_journal_inum if it changes after journal replay
When mounting a c
ghsa_unreviewed·2025-05-02
CVE-2023-53091 [MEDIUM] CWE-476 GHSA-ghqh-9ppg-g8cf: In the Linux kernel, the following vulnerability has been resolved:
ext4: update s_journal_inum if it changes after journal replay
When mounting a c
In the Linux kernel, the following vulnerability has been resolved:
ext4: update s_journal_inum if it changes after journal replay
When mounting a crafted ext4 image, s_journal_inum may change after journal
replay, which is obviously unreasonable because we have successfully loaded
and replayed the journal through the old s_journal_inum. And the new
s_journal_inum bypasses some of the checks in ext4_get_journal(), which
may trigger a null pointer dereference problem. So if s_journal_inum
changes after the journal replay, we ignore the change, and rewrite the
current journal_inum to the superblock.
No detection rules found.
No public exploits indexed.
2025-05-02
Published