ext4: set goal start correctly in ext4_mb_normalize_request
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c9de560ded61faa5b754137b7753da252391c55a · < c6bee8970075b256fc1b07bf4873049219380818| No fix yet |
| Linux Linux |
|
|
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 ]
From the CVE record · Linux
The Linux kernel’s ext4 code can calculate an invalid goal start or pass an underflowed value to a function that later triggers a BUG_ON. The input does not specify how an attacker could trigger this condition or whether access or user interaction is required.
Engineers running Linux systems that use ext4 should check their kernel versions; affected versions are not specified.