Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-53091ext4: update s_journal_inum if it changes after journal replay

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 18 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53091, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 345c0dbf3a30872d9b204db96b5857cd00808cae – < 499fef2030fb754c68b1c7cb3a799a3bc1d0d925
    • affected 345c0dbf3a30872d9b204db96b5857cd00808cae – < 70e66bdeae4d0f7c8e87762f425b68aedd5e8955
    • affected 345c0dbf3a30872d9b204db96b5857cd00808cae – < ee0c5277d4fab920bd31345c49e193ecede9ecef
    • affected 345c0dbf3a30872d9b204db96b5857cd00808cae – < 3039d8b8692408438a618fac2776b629852663c3
    • affected 51890201da4d654f6ca131bc45a0e892bb10de1d
    • affected 7eff961ca9f364be255d279346517ba0158ec8e3
    • affected a9855260fe8d8680bf8c4f0d8303b696c861e99b
    • affected 795762468125a6412c089651e74f780bee154118
    • affected 2fd4629de51974002f4e9cf1a35a1926dd6c9d99
    • affected 3.16.85 – < 3.17
    • affected 4.4.221 – < 4.5
    • affected 4.9.221 – < 4.10
    • affected 4.14.178 – < 4.15
    • affected 4.19.73 – < 4.20
  • Linux · Linux

    • affected 5.2
    • unaffected < 5.2
    • unaffected 5.15.104 – ≤ 5.15.*
    • unaffected 6.1.21 – ≤ 6.1.*
    • unaffected 6.2.8 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53091 badge
[![CVE-2023-53091](https://cveledger.app/badge/CVE-2023-53091.svg)](https://cveledger.app/cve/CVE-2023-53091)

Record last updated .