Bug 1225045 (CVE-2021-47326) - VUL-0: REJECTED: CVE-2021-47326: kernel: x86/signal: Detect and prevent an alternate signal stack overflow
Summary: VUL-0: REJECTED: CVE-2021-47326: kernel: x86/signal: Detect and prevent an al...
Status: RESOLVED INVALID
Alias: CVE-2021-47326
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/406962/
Whiteboard: CVSSv3.1:SUSE:CVE-2021-47326:5.5:(AV:...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-22 15:53 UTC by SMASH SMASH
Modified: 2024-05-23 14:01 UTC (History)
4 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-05-22 15:53:39 UTC
In the Linux kernel, the following vulnerability has been resolved:

x86/signal: Detect and prevent an alternate signal stack overflow

The kernel pushes context on to the userspace stack to prepare for the
user's signal handler. When the user has supplied an alternate signal
stack, via sigaltstack(2), it is easy for the kernel to verify that the
stack size is sufficient for the current hardware context.

Check if writing the hardware context to the alternate stack will exceed
it's size. If yes, then instead of corrupting user-data and proceeding with
the original signal handler, an immediate SIGSEGV signal is delivered.

Refactor the stack pointer check code from on_sig_stack() and use the new
helper.

While the kernel allows new source code to discover and use a sufficient
alternate signal stack size, this check is still necessary to protect
binaries with insufficient alternate signal stack size from data
corruption.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-47326
https://www.cve.org/CVERecord?id=CVE-2021-47326
https://git.kernel.org/stable/c/00fcd8f33e9b9f57115c3b1cfc4cb96450c18796
https://git.kernel.org/stable/c/2beb4a53fc3f1081cedc1c1a198c7f56cc4fc60c
https://git.kernel.org/stable/c/74569cb9ed7bc60e395927f55d3dc3be143a0164
https://git.kernel.org/stable/c/74d6fcea1d896800e60f1c675137efebd1a6c9a6
https://git.kernel.org/stable/c/afb04d0b5543a5bf8e157b9119fbfc52606f4c11
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2021/CVE-2021-47326.mbox
Comment 2 Nikolay Borisov 2024-05-23 10:20:46 UTC
Disputed, let's see what the resolution will be... https://lore.kernel.org/all/06570587-dc49-4885-83da-7a386f012106@suse.com/
Comment 5 Andrea Mattiazzo 2024-05-23 14:01:09 UTC
Thanks a lot, will close it.