From: 老小孩老小孩 <arabain@126.com>
To: gcc-patches@gcc.gnu.org
Subject: Inquiry about ARM gcc5 CVE-2023-4039 Patch
Date: Tue, 24 Oct 2023 10:53:58 +0800 (CST) [thread overview]
Message-ID: <24f0570b.1ae8.18b5f9a70c6.Coremail.arabain@126.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
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.
Best regards,
next reply other threads:[~2023-10-24 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 2:53 老小孩老小孩 [this message]
2023-10-24 3:00 ` Andrew Pinski
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=24f0570b.1ae8.18b5f9a70c6.Coremail.arabain@126.com \
--to=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).