---
id: CVE-2023-53091
title: 'ext4: update s_journal_inum if it changes after journal replay'
summary: |-
  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 u…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 345c0dbf3a30872d9b204db96b5857cd00808cae <
    499fef2030fb754c68b1c7cb3a799a3bc1d0d925
  - >-
    Linux >= 345c0dbf3a30872d9b204db96b5857cd00808cae <
    70e66bdeae4d0f7c8e87762f425b68aedd5e8955
  - >-
    Linux >= 345c0dbf3a30872d9b204db96b5857cd00808cae <
    ee0c5277d4fab920bd31345c49e193ecede9ecef
  - >-
    Linux >= 345c0dbf3a30872d9b204db96b5857cd00808cae <
    3039d8b8692408438a618fac2776b629852663c3
  - Linux 51890201da4d654f6ca131bc45a0e892bb10de1d
  - Linux 7eff961ca9f364be255d279346517ba0158ec8e3
  - Linux a9855260fe8d8680bf8c4f0d8303b696c861e99b
  - Linux 795762468125a6412c089651e74f780bee154118
  - Linux 2fd4629de51974002f4e9cf1a35a1926dd6c9d99
  - Linux >= 3.16.85 < 3.17
  - Linux >= 4.4.221 < 4.5
  - Linux >= 4.9.221 < 4.10
  - Linux >= 4.14.178 < 4.15
  - Linux >= 4.19.73 < 4.20
  - Linux 5.2
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-05T20:16:57.244669Z'
published: '2025-05-02'
updated: '2026-11-05'
sourceUpdated: '2026-11-05T20:21:00.270Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2023-53091'
references:
  - url: 'https://git.kernel.org/stable/c/499fef2030fb754c68b1c7cb3a799a3bc1d0d925'
  - url: 'https://git.kernel.org/stable/c/70e66bdeae4d0f7c8e87762f425b68aedd5e8955'
  - url: 'https://git.kernel.org/stable/c/ee0c5277d4fab920bd31345c49e193ecede9ecef'
  - url: 'https://git.kernel.org/stable/c/3039d8b8692408438a618fac2776b629852663c3'
tags:
  - cve.org
epss: 0.00215
epssPercentile: 0.11999
ingestedAt: '2026-11-05T22:38:31.767Z'
---

## Overview

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

- `Linux >= 345c0dbf3a30872d9b204db96b5857cd00808cae < 499fef2030fb754c68b1c7cb3a799a3bc1d0d925`
- `Linux >= 345c0dbf3a30872d9b204db96b5857cd00808cae < 70e66bdeae4d0f7c8e87762f425b68aedd5e8955`
- `Linux >= 345c0dbf3a30872d9b204db96b5857cd00808cae < ee0c5277d4fab920bd31345c49e193ecede9ecef`
- `Linux >= 345c0dbf3a30872d9b204db96b5857cd00808cae < 3039d8b8692408438a618fac2776b629852663c3`
- `Linux 51890201da4d654f6ca131bc45a0e892bb10de1d`
- `Linux 7eff961ca9f364be255d279346517ba0158ec8e3`
- `Linux a9855260fe8d8680bf8c4f0d8303b696c861e99b`
- `Linux 795762468125a6412c089651e74f780bee154118`
- `Linux 2fd4629de51974002f4e9cf1a35a1926dd6c9d99`
- `Linux >= 3.16.85 < 3.17`
- `Linux >= 4.4.221 < 4.5`
- `Linux >= 4.9.221 < 4.10`
- `Linux >= 4.14.178 < 4.15`
- `Linux >= 4.19.73 < 4.20`
- `Linux 5.2`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.