Skip to content
Noroxi
CVE-2023-53503· NVD / CVE Program· CNA Linux

ext4: allow ext4_get_group_info() to fail

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 100c0ad6c04597fefeaaba2bb1827cc015d95067, 31668cebf45adfb6283e465e641c4f5a21b07afa, 5354b2af34064a4579be8bc0e2f15a7b70f14b5f.

Low priority for now. Upgrade to Linux Linux 100c0ad6c04597fefeaaba2bb1827cc015d95067, 31668cebf45adfb6283e465e641c4f5a21b07afa, 5354b2af34064a4579be8bc0e2f15a7b70f14b5f or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Oct 1, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-53503

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.11 and later · before 5.10.181
  • linux linux kernel5.11 and later · before 5.15.113
  • linux linux kernel5.16 and later · before 6.1.30
  • linux linux kernel6.2 and later · before 6.3.4
  • linux linux kernel6.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.11affected
    • 2f2e09eb15849562aede80ed007658e4504ded26 and later · before 100c0ad6c04597fefeaaba2bb1827cc015d95067affected · git
    • 2f2e09eb15849562aede80ed007658e4504ded26 and later · before 620a3c28221bb219b81bc0bffd065cc187494302affected · git
    • 2f2e09eb15849562aede80ed007658e4504ded26 and later · before b4319e457d6e3fb33e443efeaf4634fc36e8a9edaffected · git
    • 2f2e09eb15849562aede80ed007658e4504ded26 and later · before 31668cebf45adfb6283e465e641c4f5a21b07afaaffected · git
    • 2f2e09eb15849562aede80ed007658e4504ded26 and later · before 5354b2af34064a4579be8bc0e2f15a7b70f14b5faffected · git
    • before 3.11not affected · semver
    • 5.10.181 and later · up to and including 5.10.*not affected · semver
    • 5.15.113 and later · up to and including 5.15.*not affected · semver
    • 6.1.30 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.37-16.1.37-1
Debian:13linuxbefore 6.3.7-16.3.7-1
Red Hat:rhel_eus:9.4::appstreambpftool-debuginfobefore 0:7.3.0-427.47.1.el9_40:7.3.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-develbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debuginfobefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-develbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-debuginfobefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-develbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfobefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-develbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-devel-matchedbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-docbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debuginfobefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-tools-debuginfobefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4

+56

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-53498Oct 1, 2025 · drm/amd/display: Fix potential null dereference
    22Monitor
  • ← EarlierCVE-2023-53501Oct 1, 2025 · iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind
    18Monitor
  • Later →CVE-2023-53505Oct 1, 2025 · clk: tegra: tegra124-emc: Fix potential memory leak
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux100c0ad6c04597fefeaaba2bb1827cc015d95067Vendor (CNA)
Linux Linux31668cebf45adfb6283e465e641c4f5a21b07afaVendor (CNA)
Linux Linux5354b2af34064a4579be8bc0e2f15a7b70f14b5fVendor (CNA)
Linux Linux620a3c28221bb219b81bc0bffd065cc187494302Vendor (CNA)
Linux Linuxb4319e457d6e3fb33e443efeaf4634fc36e8a9edVendor (CNA)
debian:linux6.1.37-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records