CVE-2023-54021
Description
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 ]
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
In the Linux kernel's ext4 filesystem, an incorrect goal start in mballoc block allocation can cause a BUG_ON crash via an underflowed block range.
Vulnerability
In the Linux kernel's ext4 filesystem, the function ext4_mb_normalize_request was mis-setting ac_f_ex instead of ac_g_ex [1]. This caused the block-allocation goal start to be improperly initialized, and additionally a missing size check against ar->pright could lead to an underflow: ar->pright - size would become a very large value, which when passed to ext4_get_group_no_and_offset() triggers a BUG_ON [2].
Exploitation
An attacker who can mount or interact with a specially corrupted ext4 filesystem, or trigger specific write allocation patterns that reach the flawed code path, could cause a denial of service (crash) of the kernel [1][2]. No special privileges are required beyond the ability to cause ext4 block allocation (e.g., by writing files).
Impact
The primary impact is a kernel panic (BUG_ON), which results in a denial of service for the system. There is no indication of privilege escalation or data corruption beyond the crash itself.
Mitigation
The fix was applied to the Linux kernel stable branches. Users should update to a kernel version containing the commit that corrects the goal start and adds the size check [1][2].
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
82479bb6cbdb4390eee955d4dcee78217a7ae3ca3005b502cbc4a3e1d07a8c6bee8970075abb330ffaa3ab07ffe6927c7Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/2479bb6cbdb4d56b807bbe5229e3e26a6f1f4530nvd
- git.kernel.org/stable/c/390eee955d4de4662db5e3e9e9a9eae020432cb7nvd
- git.kernel.org/stable/c/3ca3005b502ca8ea87d6a344323b179b48c4e4a3nvd
- git.kernel.org/stable/c/abb330ffaa3a0ae7ce632e28c9260b461c01f19fnvd
- git.kernel.org/stable/c/b07ffe6927c75d99af534d685282ea188d9f71a6nvd
- git.kernel.org/stable/c/bc4a3e1d07a86ae5845321d371190244acacb2f2nvd
- git.kernel.org/stable/c/c6bee8970075b256fc1b07bf4873049219380818nvd
- git.kernel.org/stable/c/cee78217a7ae72d11c2e21e1a5263b8044489823nvd
News mentions
0No linked articles in our index yet.