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-53503ext4: allow ext4_get_group_info() to fail

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: allow ext4_get_group_info() to fail Previously, ext4_get_group_info() would treat an invalid group number as BUG(), since in theory it should never happen. However, if a malicious attaker (or fuzzer) modifies the superblock via the block device while it is the file system is mounted, it is possible for s_first_data_block to get set to a very large number. In that case, when calculating the block group of some block number (such as the starting block of a preallocation region), could result in an underflow and very large block group number. Then the BUG_ON check in ext4_get_group_info() would fire, resutling in a denial of service attack that can be triggered by root or someone with write access to the block device. For a quality of implementation perspective, it's best that even if the system administrator does something that they shouldn't, that it will not trigger a BUG. So instead of BUG'ing, ext4_get_group_info() will call ext4_error and return NULL. We also add fallback code in all of the callers of ext4_get_group_info() that it might NULL. Also, since ext4_get_group_info() was already borderline to be an inline function, un-inline it. The results in a next reduction of the compiled text size of ext4 by roughly 2k.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 13 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-53503, 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.16% · top 95% of all CVEs (13 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 2f2e09eb15849562aede80ed007658e4504ded26 – < 100c0ad6c04597fefeaaba2bb1827cc015d95067
    • affected 2f2e09eb15849562aede80ed007658e4504ded26 – < 620a3c28221bb219b81bc0bffd065cc187494302
    • affected 2f2e09eb15849562aede80ed007658e4504ded26 – < b4319e457d6e3fb33e443efeaf4634fc36e8a9ed
    • affected 2f2e09eb15849562aede80ed007658e4504ded26 – < 31668cebf45adfb6283e465e641c4f5a21b07afa
    • affected 2f2e09eb15849562aede80ed007658e4504ded26 – < 5354b2af34064a4579be8bc0e2f15a7b70f14b5f
  • Linux · Linux

    • affected 3.11
    • unaffected < 3.11
    • unaffected 5.10.181 – ≤ 5.10.*
    • unaffected 5.15.113 – ≤ 5.15.*
    • unaffected 6.1.30 – ≤ 6.1.*
    • unaffected 6.3.4 – ≤ 6.3.*
    • unaffected 6.4 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .