Vulnerability · Published Oct 1, 2025 · Assigned by Linux
CVE-2023-53503ext4: allow ext4_get_group_info() to fail
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 5% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.37-1 | DEBIAN-CVE-2023-53503 |
| Debian:13 | linux | 6.3.7-1 | DEBIAN-CVE-2023-53503 |
| Debian:14 | linux | 6.3.7-1 | DEBIAN-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux | 5.15.0-83.92 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1044.49 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1046.53 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1046.53.1 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1041.49 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1041.46 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1027.32 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1037.40 | UBUNTU-CVE-2023-53503 |
| Ubuntu:24.04:LTS | linux-intel | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1039.45 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1041.46 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-83.92 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1032.32 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1017.17 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1004.4 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1042.48 | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1037.40 | UBUNTU-CVE-2023-53503 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-53503 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1025.29 | UBUNTU-CVE-2023-53503 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 2f2e09eb15849562aede80ed007658e4504ded26 – before 100c0ad6c04597fefeaaba2bb1827cc015d950672f2e09eb15849562aede80ed007658e4504ded26 – before 620a3c28221bb219b81bc0bffd065cc1874943022f2e09eb15849562aede80ed007658e4504ded26 – before b4319e457d6e3fb33e443efeaf4634fc36e8a9ed2f2e09eb15849562aede80ed007658e4504ded26 – before 31668cebf45adfb6283e465e641c4f5a21b07afa2f2e09eb15849562aede80ed007658e4504ded26 – before 5354b2af34064a4579be8bc0e2f15a7b70f14b5f |
| Linux | Linux | 3.11 |
References
- https://git.kernel.org/stable/c/100c0ad6c04597fefeaaba2bb1827cc015d95067
- https://git.kernel.org/stable/c/620a3c28221bb219b81bc0bffd065cc187494302
- https://git.kernel.org/stable/c/b4319e457d6e3fb33e443efeaf4634fc36e8a9ed
- https://git.kernel.org/stable/c/31668cebf45adfb6283e465e641c4f5a21b07afa
- https://git.kernel.org/stable/c/5354b2af34064a4579be8bc0e2f15a7b70f14b5f