s390: avoid using global register for current_stack_pointer
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel a478952a8ac44e32316dc046a063a7dc34825aa6 and Kernel e3c11025bcd2142a61abe5806b2f86a0e78118df.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.18, >=30de14b1884ba609fc1acfba5b40309e3a6ccefe <a478952a8ac44e32316dc046a063a7dc34825aa6, >=30de14b1884ba609fc1acfba5b40309e3a6ccefe <e3c11025bcd2142a61abe5806b2f86a0e78118df | a478952a8ac44e32316dc046a063a7dc34825aa6, e3c11025bcd2142a61abe5806b2f86a0e78118df |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket