public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "goldstein.w.n at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/28755] New: overflow bug in wcsncmp_avx2 and wcsncmp_evex
Date: Sun, 09 Jan 2022 10:30:11 +0000	[thread overview]
Message-ID: <bug-28755-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=28755

            Bug ID: 28755
           Summary: overflow bug in wcsncmp_avx2 and wcsncmp_evex
           Product: glibc
           Version: 2.34
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: string
          Assignee: unassigned at sourceware dot org
          Reporter: goldstein.w.n at gmail dot com
  Target Milestone: ---

Similiar to [BZ 27974](https://sourceware.org/bugzilla/show_bug.cgi?id=27974).
The multiply of length by sizeof (wchar_t) can overflow if length is >= 2^62
which can lead to incorrect results.

For example:

#include <wchar.h>
int
main(int argc, char ** argv) {
    assert(__wcsncmp_evex(L"abc", L"abd", (1UL << 62)) != 0);
    assert(__wcsncmp_avx2(L"abc", L"abd", (1UL << 62)) != 0);
}

Will fail on either assert.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-01-09 10:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 10:30 goldstein.w.n at gmail dot com [this message]
2022-01-09 14:07 ` [Bug string/28755] " hjl.tools at gmail dot com
2022-01-10  0:29 ` goldstein.w.n at gmail dot com
2022-01-11  3:07 ` goldstein.w.n at gmail dot com
2022-01-27  4:24 ` cvs-commit at gcc dot gnu.org
2022-01-27  4:58 ` cvs-commit at gcc dot gnu.org
2022-01-27 13:14 ` cvs-commit at gcc dot gnu.org
2022-01-27 13:29 ` cvs-commit at gcc dot gnu.org
2022-01-27 13:33 ` cvs-commit at gcc dot gnu.org
2022-01-27 15:28 ` cvs-commit at gcc dot gnu.org
2022-01-27 16:12 ` cvs-commit at gcc dot gnu.org
2022-01-27 16:14 ` hjl.tools at gmail dot com
2022-02-17 19:04 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:14 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:22 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:27 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:32 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:40 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:43 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:48 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:52 ` cvs-commit at gcc dot gnu.org

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=bug-28755-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).