public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alex Coplan <acoplan@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r11-10469] varasm: Fix type confusion bug
Date: Mon, 16 Jan 2023 13:15:09 +0000 (GMT)	[thread overview]
Message-ID: <20230116131509.A8D3C3858CDB@sourceware.org> (raw)

https://gcc.gnu.org/g:260297e42ca9eddf31aae4acb8a214d3f96a4b16

commit r11-10469-g260297e42ca9eddf31aae4acb8a214d3f96a4b16
Author: Alex Coplan <alex.coplan@arm.com>
Date:   Thu Dec 1 17:36:02 2022 +0000

    varasm: Fix type confusion bug
    
    This patch fixes a type confusion bug in varasm.c:assemble_variable.
    The problem is that the current code calls:
    
      sect = get_variable_section (decl, false);
    
    and then accesses sect->named.name without checking whether the section
    is in fact a named section. In the surrounding else clause, we only know
    that SECTION_STYLE (sect) != SECTION_NOSWITCH, so it is possible that
    the section is an unnamed section.
    
    In practice, this means that we end up doing a wild string compare
    between a function pointer and the string literal ".vtable_map_vars".
    This is because sect->named.name aliases sect->unnamed.callback in the
    section union.
    
    This can be seen in GDB with a simple testcase such as "int x;".
    
    This patch fixes the issue by checking the SECTION_STYLE of the section
    is in fact SECTION_NAMED before trying to do the string comparison.
    
    We drop the existing check of whether sect->named.name is non-NULL
    because this should presumably always be the case for a named section.
    
    gcc/ChangeLog:
    
            * varasm.c (assemble_variable): Fix type confusion bug when
            checking for ".vtable_map_vars" section.
    
    (cherry picked from commit de144fdab17dbbb64ccb540056ab78b4ffb3fbbc)

Diff:
---
 gcc/varasm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/varasm.c b/gcc/varasm.c
index 93b9c8ef0ee..8e456576010 100644
--- a/gcc/varasm.c
+++ b/gcc/varasm.c
@@ -2380,7 +2380,7 @@ assemble_variable (tree decl, int top_level ATTRIBUTE_UNUSED,
   else
     {
       /* Special-case handling of vtv comdat sections.  */
-      if (sect->named.name
+      if (SECTION_STYLE (sect) == SECTION_NAMED
 	  && (strcmp (sect->named.name, ".vtable_map_vars") == 0))
 	handle_vtv_comdat_section (sect, decl);
       else

                 reply	other threads:[~2023-01-16 13:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230116131509.A8D3C3858CDB@sourceware.org \
    --to=acoplan@gcc.gnu.org \
    --cc=gcc-cvs@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).