public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ricbal02 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114837] New: [11/12/13/14] Fix to security weaknesses in PCS for CMSE
Date: Wed, 24 Apr 2024 15:40:05 +0000	[thread overview]
Message-ID: <bug-114837-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114837
           Summary: [11/12/13/14] Fix to security weaknesses in PCS for
                    CMSE
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ricbal02 at gcc dot gnu.org
  Target Milestone: ---

Security weaknesses exist in PCS for CMSE. To resolve this a patch will be
upstreamed and backported which will:

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 will fix the following: CVE-2024-0151.

             reply	other threads:[~2024-04-24 15:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 15:40 ricbal02 at gcc dot gnu.org [this message]
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
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@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).