public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114837] [11/12/13] Fix to security weaknesses in arm PCS for CMSE
Date: Thu, 25 Apr 2024 14:44:08 +0000	[thread overview]
Message-ID: <bug-114837-4-3gbqXRoM7N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114837-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114837

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Richard Ball
<ricbal02@gcc.gnu.org>:

https://gcc.gnu.org/g:441e194abcf3211de647d74c892f90879ae9ca8c

commit r12-10394-g441e194abcf3211de647d74c892f90879ae9ca8c
Author: Richard Ball <richard.ball@arm.com>
Date:   Thu Apr 25 15:30:42 2024 +0100

    arm: Zero/Sign extends for CMSE security

    Co-Authored by: Andre Simoes Dias Vieira <Andre.SimoesDiasVieira@arm.com>

    This patch makes the following changes:

    1) When calling a secure function from non-secure code then any arguments
       smaller than 32-bits that are passed in registers are zero- or
sign-extended.
    2) After a non-secure function returns into secure code then any return
value
       smaller than 32-bits that is passed in a register is  zero- or
sign-extended.

    This patch addresses the following CVE-2024-0151.

    gcc/ChangeLog:
            PR target/114837
            * config/arm/arm.cc (cmse_nonsecure_call_inline_register_clear):
            Add zero/sign extend.
            (arm_expand_prologue): Add zero/sign extend.

    gcc/testsuite/ChangeLog:

            * gcc.target/arm/cmse/extend-param.c: New test.
            * gcc.target/arm/cmse/extend-return.c: New test.

    (cherry picked from commit ad45086178d833254d66fab518b14234418f002b)

  parent reply	other threads:[~2024-04-25 14:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 15:40 [Bug target/114837] New: [11/12/13/14] Fix to security weaknesses in " ricbal02 at gcc dot gnu.org
2024-04-24 15:40 ` [Bug target/114837] " ricbal02 at gcc dot gnu.org
2024-04-24 15:58 ` ricbal02 at gcc dot gnu.org
2024-04-25 14:34 ` [Bug target/114837] [11/12/13/14] Fix to security weaknesses in arm " cvs-commit at gcc dot gnu.org
2024-04-25 14:35 ` ricbal02 at gcc dot gnu.org
2024-04-25 14:40 ` [Bug target/114837] [11/12/13] " cvs-commit at gcc dot gnu.org
2024-04-25 14:44 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-25 14:46 ` cvs-commit at gcc dot gnu.org
2024-04-25 14:48 ` ricbal02 at gcc dot gnu.org
2024-04-25 14:48 ` ricbal02 at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-114837-4-3gbqXRoM7N@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).