Bug 2309796 (CVE-2024-44965) - CVE-2024-44965 kernel: x86/mm: Fix pti_clone_pgtable() alignment assumption
Summary: CVE-2024-44965 kernel: x86/mm: Fix pti_clone_pgtable() alignment assumption
Keywords:
Status: NEW
Alias: CVE-2024-44965
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2309899
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-09-04 19:21 UTC by OSIDB Bzimport
Modified: 2024-11-12 09:36 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2024:9315 0 None None None 2024-11-12 09:36:40 UTC

Description OSIDB Bzimport 2024-09-04 19:21:12 UTC
In the Linux kernel, the following vulnerability has been resolved:

x86/mm: Fix pti_clone_pgtable() alignment assumption

Guenter reported dodgy crashes on an i386-nosmp build using GCC-11
that had the form of endless traps until entry stack exhaust and then
#DF from the stack guard.

It turned out that pti_clone_pgtable() had alignment assumptions on
the start address, notably it hard assumes start is PMD aligned. This
is true on x86_64, but very much not true on i386.

These assumptions can cause the end condition to malfunction, leading
to a 'short' clone. Guess what happens when the user mapping has a
short copy of the entry text?

Use the correct increment form for addr to avoid alignment
assumptions.

Comment 3 errata-xmlrpc 2024-11-12 09:36:39 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2024:9315 https://access.redhat.com/errata/RHSA-2024:9315


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