From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-return-11776-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Received: (qmail 31510 invoked by alias); 1 Oct 2010 12:01:27 -0000
Received: (qmail 31321 invoked by uid 48); 1 Oct 2010 12:01:06 -0000
Date: Fri, 01 Oct 2010 12:01:00 -0000
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Message-ID: <20101001120105.12077.ppluzhnikov@google.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug libc/12077] New: strncmp over-reads its buffer, may cause SIGSEGV
X-Bugzilla-Reason: CC
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
X-SW-Source: 2010-10/txt/msg00001.txt.bz2

Attached test case crashes in 64-bit mode
  ./a.out $j
  ./a.out $j 1
for all values of $j between 1 and 15

It does not crash in 32-bit mode (the bug appears to be in sysdeps/x86_64/strcmp.S).

The bug is not present in glibc-2.7; is present in 2.11.1 and current trunk.

-- 
           Summary: strncmp over-reads its buffer, may cause SIGSEGV
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: critical
          Priority: P2
         Component: libc
        AssignedTo: drepper dot fsp at gmail dot com
        ReportedBy: ppluzhnikov at google dot com
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: x86_64-linux-gnu
  GCC host triplet: x86_64-linux-gnu
GCC target triplet: x86_64-linux-gnu


http://sourceware.org/bugzilla/show_bug.cgi?id=12077

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.