CVE-2023-53091

ext4: update s_journal_inum if it changes after journal replay

MEDIUM
5.5
CVSS Score
Published: May 2, 2025 at 03:55 PM UTC
Updated: June 17, 2026 at 06:44 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 3.16.85v ≥ 4.14.178v ≥ 4.19.73v ≥ 4.4.221v ≥ 4.9.221v < 5.15.1043.16.85 ≤ v < 3.174.14.178 ≤ v < 4.154.19.73 ≤ v < 4.204.4.221 ≤ v < 4.54.9.221 ≤ v < 4.105.16 ≤ v < 6.1.215.2 ≤ v < 5.15.1045.2 ≤ v < 6.1.215.2 ≤ v < 6.2.85.2 ≤ v < 6.36.2 ≤ v < 6.2.82fd4629de51974002f4e9cf1a35a1926dd6c9d993.16.85345c0dbf3a30872d9b204db96b5857cd00808cae4.14.1784.19.734.4.2214.9.2215.251890201da4d654f6ca131bc45a0e892bb10de1d795762468125a6412c089651e74f780bee1541187eff961ca9f364be255d279346517ba0158ec8e3a9855260fe8d8680bf8c4f0d8303b696c861e99b
Vendor states this is fixed in 3039d8b8692408438a618fac2776b629852663c3 (fixed)
Vendor states this is fixed in 499fef2030fb754c68b1c7cb3a799a3bc1d0d925 (fixed)
Vendor states this is fixed in 70e66bdeae4d0f7c8e87762f425b68aedd5e8955 (fixed)
Vendor states this is fixed in ee0c5277d4fab920bd31345c49e193ecede9ecef (fixed)
Affected range stops below 3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.15.104 (unaffected)
Vendor states this is fixed in 5.2 (unaffected)
Vendor states this is fixed in 6.1.21 (unaffected)
Vendor states this is fixed in 6.2.8 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3039d8b8692408438a618fac2776b629852663c3
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/499fef2030fb754c68b1c7cb3a799a3bc1d0d925
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/70e66bdeae4d0f7c8e87762f425b68aedd5e8955
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ee0c5277d4fab920bd31345c49e193ecede9ecef

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card