Back

HIGH

s390: avoid using global register for current_stack_pointer

Published May 1, 2025

Description

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.

Affected products

Remediation

No remediation recorded yet.

References (8)

Change history (0)

No recorded changes yet.

Sources

CVE.org / MITRE

Status PUBLISHED
Assigner Linux
Published May 1, 2025
Updated Aug 5, 2026
Reserved May 1, 2025

CISA Vulnrichment

No data

NVD

Status Modified
Modified Aug 4, 2026

Red Hat

Severity Moderate
Public date May 1, 2025
Bugzilla 2363456

ENISA EUVD

Assigner Linux
Published May 1, 2025
Updated Aug 5, 2026

GitHub

No data