Bug 2267505 (CVE-2024-26621) - CVE-2024-26621 kernel: mm: huge_memory: don't force huge page alignment on 32 bit
Summary: CVE-2024-26621 kernel: mm: huge_memory: don't force huge page alignment on 32...
Status: NEW
Alias: CVE-2024-26621
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Product Security
QA Contact:
Depends On: 2267506
Blocks: 2267686
TreeView+ depends on / blocked
Reported: 2024-03-03 08:17 UTC by ybuenos
Modified: 2024-06-09 17:04 UTC (History)
52 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description ybuenos 2024-03-03 08:17:23 UTC
In the Linux kernel, the following vulnerability has been resolved:

mm: huge_memory: don't force huge page alignment on 32 bit

The Linux kernel CVE team has assigned CVE-2024-26621 to this issue.

Upstream advisory:

Comment 1 ybuenos 2024-03-03 08:18:13 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2267506]

Comment 5 Justin M. Forbes 2024-03-04 20:53:19 UTC
This was fixed for Fedora with the 6.7.6 stable kernel updates.

Comment 6 Audra Mitchell 2024-03-12 21:02:15 UTC
This does not impact RHEL8 or RHEL9 at this time as we do not have this code in our kernel. The issue was not introduced until v6.7 which we have not pulled into RHEL8 or RHEL9...

As an aside, we do have these two patch which introduces the same code- but also removes it at the same time- so we can disregard:
eebc80b8a167 Revert "mm: align larger anonymous mappings on THP boundaries"
c97e82038959 mm: align larger anonymous mappings on THP boundaries

Closing the triaging jiras accordingly...

Comment 7 Alex 2024-06-09 17:04:47 UTC
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2024-26621 is: CHECK	Maybe valid. Check manually. with impact LOW (that is an approximation based on flags  ; 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.