From: Andrew Pinski <pinskia@gmail.com>
To: 老小孩老小孩 <arabain@126.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Inquiry about ARM gcc5 CVE-2023-4039 Patch
Date: Mon, 23 Oct 2023 20:00:51 -0700 [thread overview]
Message-ID: <CA+=Sn1=u2bpthcpg_3LzWXrTv=aK_oF5XFpPBgDuohEao4qHSg@mail.gmail.com> (raw)
In-Reply-To: <24f0570b.1ae8.18b5f9a70c6.Coremail.arabain@126.com>
On Mon, Oct 23, 2023 at 7:54 PM 老小孩老小孩 <arabain@126.com> wrote:
>
> Dear arms,
>
> I hope this message finds you well.
>
> I am writing to inquire about the issue of ARM gcc5 CVE-2023-4039. According to the advisory on GitHub (https://github.com/metaredteam/external-disclosures/security/advisories/GHSA-x7ch-h5rf-w2mf), this bug affects versions from 5.4.0 to the trunk as of May 15, 2023.
>
> However, I noticed that currently, patches are only provided for gcc7 and above, as per the information available on the ARM Security Center (https://developer.arm.com/Arm%20Security%20Center/GCC%20Stack%20Protector%20Vulnerability%20AArch64).
>
> Given the potential impact of this vulnerability, I am particularly interested in a patch for gcc5. Could you please provide information on whether a patch for gcc5 is available or planned? If not, could you suggest any possible workarounds or mitigation strategies for systems that are currently using gcc5?
>
> I appreciate your attention to this matter and look forward to your response.
THIS should NEVER have been a security CVE in the first place.
This is not a security issue with any correct code that GCC will process.
GCC does not consider this a security issue according to its security policy.
See the "Security features implemented in GCC" section of
https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=SECURITY.txt;hb=HEAD
for more information on that policy.
Thanks,
Andrew Pinski
>
> Best regards,
prev parent reply other threads:[~2023-10-24 3:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 2:53 老小孩老小孩
2023-10-24 3:00 ` Andrew Pinski [this message]
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='CA+=Sn1=u2bpthcpg_3LzWXrTv=aK_oF5XFpPBgDuohEao4qHSg@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=arabain@126.com \
--cc=gcc-patches@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).