CVE-2023-54021: ext4: set goal start correctly in ext4_mb_normalize_request
In the Linux kernel, the following vulnerability has been resolved:
ext4: set goal start correctly in ext4_mb_normalize_request
We need to set ac_g_ex to notify the goal start used in
ext4_mb_find_by_goal. Set ac_g_ex instead of ac_f_ex in
ext4_mb_normalize_request.
Besides we should assure goal start is in range [first_data_block,
blocks_count) as ext4_mb_initialize_context does.
[ Added a check to make sure size is less than ar->pright; otherwise
we could end up passing an underflowed value of ar->pright - size to
ext4_get_group_no_and_offset(), which will trigger a BUG_ON later on.
- TYT ]
Security readout for executives and security teams
Plain-English summary
CVE-2023-54021 is a Linux kernel ext4 filesystem bug. The public record describes incorrect goal-block handling that can reach a kernel BUG condition. Business urgency depends on whether affected Linux kernels and ext4 filesystems are present; the sources do not provide CVSS, confirmed impact scope, or exploitation evidence.
Executive priority
Treat as a kernel maintenance item until impact is clarified. Prioritize patching internet-facing, multi-user, and business-critical Linux systems using ext4, but avoid emergency escalation without vendor severity or exploitation evidence.
Technical view
The ext4 multiblock allocator used the wrong extent field in ext4_mb_normalize_request and lacked range checks for the allocation goal. The fix sets ac_g_ex correctly and checks bounds to prevent an underflow before ext4_get_group_no_and_offset(), which could later trigger BUG_ON.
Likely exposure
Potentially exposed systems are Linux hosts running affected kernel versions that use ext4. The CVE lists affected Linux versions including 2.6.25 through 6.4-era stable lines, but distro backports require vendor-specific verification.
Exploitation context
CISA KEV status is false in the source bundle. The provided sources do not claim active exploitation, public exploit availability, remote reachability, privilege impact, or a complete attacker model.
Researcher notes
The record is sparse: no CVSS, CWE, exploit status, or affected configuration detail beyond Linux kernel versions and stable commits. Analysis should focus on reproducing the allocator bounds condition safely and mapping distro backports.
Mitigation direction
Apply vendor kernel updates that include the referenced Linux stable fixes.
Prioritize Linux systems using ext4 on affected kernel branches.
Check distribution advisories for backported package names and fixed builds.
If no update is available, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory Linux kernel versions across servers, endpoints, and appliances.
Confirm whether ext4 filesystems are mounted or used on those systems.
Compare installed kernel builds against vendor fixed versions or stable commits.
Review kernel logs for ext4-related BUG, oops, or allocation errors.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-54021 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
9Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 24, 2025, 10:55 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.