Bug 2363456 (CVE-2022-49804) - CVE-2022-49804 kernel: s390: avoid using global register for current_stack_pointer
Summary: CVE-2022-49804 kernel: s390: avoid using global register for current_stack_po...
Keywords:
Status: NEW
Alias: CVE-2022-49804
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:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-01 15:05 UTC by OSIDB Bzimport
Modified: 2025-06-20 15:54 UTC (History)
4 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-01 15:05:19 UTC
In the Linux kernel, the following vulnerability has been resolved:

s390: avoid using global register for current_stack_pointer

Commit 30de14b1884b ("s390: current_stack_pointer shouldn't be a
function") made current_stack_pointer a global register variable like
on many other architectures. Unfortunately on s390 it uncovers old
gcc bug which is fixed only since gcc-9.1 [gcc commit 3ad7fed1cc87
("S/390: Fix PR89775. Stackpointer save/restore instructions removed")]
and backported to gcc-8.4 and later. Due to this bug gcc versions prior
to 8.4 generate broken code which leads to stack corruptions.

Current minimal gcc version required to build the kernel is declared
as 5.1. It is not possible to fix all old gcc versions, so work
around this problem by avoiding using global register variable for
current_stack_pointer.

Comment 1 Avinash Hanwate 2025-05-02 05:28:19 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025050127-CVE-2022-49804-0866@gregkh/T


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