Bug 2271688 (CVE-2023-52622) - CVE-2023-52622 kernel: ext4: avoid online resizing failures due to oversized flex bg [NEEDINFO]
Summary: CVE-2023-52622 kernel: ext4: avoid online resizing failures due to oversized ...
Keywords:
Status: NEW
Alias: CVE-2023-52622
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2271689
Blocks: 2271782
TreeView+ depends on / blocked
 
Reported: 2024-03-26 21:39 UTC by Marco Benatto
Modified: 2024-06-09 16:22 UTC (History)
51 users (show)

Fixed In Version: kernel 4.19.307, kernel 5.4.269, kernel 5.10.210, kernel 5.15.149, kernel 6.1.77, kernel 6.6.16, kernel 6.7.4, kernel 6.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:
mbenatto: needinfo? (rkeshri)


Attachments (Terms of Use)

Description Marco Benatto 2024-03-26 21:39:43 UTC
In the Linux kernel, the following vulnerability has been resolved:

ext4: avoid online resizing failures due to oversized flex bg

The Linux kernel CVE team has assigned CVE-2023-52622 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/20240326171931.1354035-5-lee@kernel.org/T

Comment 1 Marco Benatto 2024-03-26 21:40:20 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2271689]

Comment 5 Justin M. Forbes 2024-03-27 20:36:55 UTC
This was fixed for Fedora with the 6.7.4 stable kernel updates.

Comment 6 Eric Sandeen 2024-04-08 19:25:36 UTC
This appears to be a warning about a too-large allocation failing, an error which is handled properly.

What is the security issue here? I don't see one.

Comment 7 Marco Benatto 2024-04-19 22:14:07 UTC
In reply to comment #6:
> This appears to be a warning about a too-large allocation failing, an error
> which is handled properly.
> 
> What is the security issue here? I don't see one.

Hi Sandeen,

this CVE was assigned by the kernel CNA. We are currently checking how to handle this situation.

@Rohit for awareness

Comment 8 Alex 2024-06-09 16:22:36 UTC
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2023-52622 is: CHECK	Maybe valid. Check manually. with impact LOW (that is an approximation based on flags DISK WARNONLY  ; these flags parsed automatically based on patch data). Such automatic check happens only for Low/Moderates (and only when not from reporter, but parsing already existing CVE). Highs always checked manually (I check it myself and then we check it again in Remediation team). In rare cases some of the Moderates could be increased to High later.


Note You need to log in before you can comment on or make changes to this bug.