[Bug sanitizer/105396] [9/10 Regression] missed stack-buffer-overflow by -O0

cvs-commit at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Wed May 11 06:26:52 GMT 2022


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

--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:4431014dc2e905a427d1e9dd4f4d494ae2d7ab96

commit r9-10152-g4431014dc2e905a427d1e9dd4f4d494ae2d7ab96
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Apr 27 08:34:18 2022 +0200

    asan: Fix up asan_redzone_buffer::emit_redzone_byte [PR105396]

    On the following testcase, we have in main's frame 3 variables,
    some red zone padding, 4 byte d, followed by 12 bytes of red zone padding,
then
    8 byte b followed by 24 bytes of red zone padding, then 40 bytes c followed
    by some red zone padding.
    The intended content of shadow memory for that is (note, each byte
describes
    8 bytes of memory):
    f1 f1 f1 f1 04 f2 00 f2 f2 f2 00 00 00 00 00 f3 f3 f3 f3 f3
    left red    d  mr b  middle r c              right red zone

    f1 is left red zone magic
    f2 is middle red zone magic
    f3 is right red zone magic
    00 when all 8 bytes are accessible
    01-07 when only 1 to 7 bytes are accessible followed by inaccessible bytes

    The -fdump-rtl-expand-details dump makes it clear that it misbehaves:
    Flushing rzbuffer at offset -160 with: f1 f1 f1 f1
    Flushing rzbuffer at offset -128 with: 04 f2 00 00
    Flushing rzbuffer at offset -128 with: 00 00 00 f2
    Flushing rzbuffer at offset -96 with: f2 f2 00 00
    Flushing rzbuffer at offset -64 with: 00 00 00 f3
    Flushing rzbuffer at offset -32 with: f3 f3 f3 f3
    In the end we end up with
    f1 f1 f1 f1 00 00 00 f2 f2 f2 00 00 00 00 00 f3 f3 f3 f3 f3
    shadow bytes because at offset -128 there are 2 overlapping stores
    as asan_redzone_buffer::emit_redzone_byte has flushed the temporary 4 byte
    buffer in the middle.

    The function is called with an offset and value.  If the passed offset is
    consecutive with the prev_offset + buffer size (off == offset), then
    we handle it correctly, similarly if the new offset is far enough from the
    old one (we then flush whatever was in the buffer and if needed add up to 3
    bytes of 00 before actually pushing value.

    But what isn't handled correctly is when the offset isn't consecutive to
    what has been added last time, but it is in the same 4 byte word of shadow
    memory (32 bytes of actual memory), like the above case where
    we have consecutive 04 f2 and then skip one shadow memory byte (aka 8 bytes
    of real memory) and then want to emit f2.  Emitting that as a store
    of little-endian 0x0000f204 followed by a store of 0xf2000000 to the same
    address doesn't work, we want to emit 0xf200f204.

    The following patch does that by pushing 1 or 2 00 bytes.
    Additionally, as a small cleanup, instead of using
          m_shadow_bytes.safe_push (value);
          flush_if_full ();
    in all of if, else if and else bodies it sinks those 2 stmts to the end
    of function as all do the same thing.

    2022-04-27  Jakub Jelinek  <jakub@redhat.com>

            PR sanitizer/105396
            * asan.c (asan_redzone_buffer::emit_redzone_byte): Handle the case
            where offset is bigger than off but smaller than m_prev_offset + 32
            bits by pushing one or more 0 bytes.  Sink the
            m_shadow_bytes.safe_push (value); flush_if_full (); statements from
            all cases to the end of the function.

            * gcc.dg/asan/pr105396.c: New test.

    (cherry picked from commit 9715f10c0651c9549b479b69d67be50ac4bd98a6)


More information about the Gcc-bugs mailing list