public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zhuorong.lin at outlook dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nptl/29755] New: pthread_getname_np() have out-of-bounds memory access Date: Mon, 07 Nov 2022 07:26:56 +0000 [thread overview] Message-ID: <bug-29755-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29755 Bug ID: 29755 Summary: pthread_getname_np() have out-of-bounds memory access Product: glibc Version: 2.34 Status: UNCONFIRMED Severity: minor Priority: P2 Component: nptl Assignee: unassigned at sourceware dot org Reporter: zhuorong.lin at outlook dot com CC: drepper.fsp at gmail dot com Target Milestone: --- When the return value of buf is n = 0, the following buf[n-1] will out-of-bounds memory access #define FMT "/proc/self/task/%u/comm" char fname[sizeof (FMT) + 8]; sprintf (fname, FMT, (unsigned int) pd->tid); int fd = __open64_nocancel (fname, O_RDONLY); if (fd == -1) return errno; int res = 0; ssize_t n = TEMP_FAILURE_RETRY (__read_nocancel (fd, buf, len)); // if n == 0 if (n < 0) res = errno; else { if (buf[n - 1] == '\n') // out-of-bounds memory access buf[n - 1] = '\0'; else if (n == len) res = ERANGE; else buf[n] = '\0'; } __close_nocancel_nostatus (fd); -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-11-07 7:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-07 7:26 zhuorong.lin at outlook dot com [this message] 2022-11-07 14:11 ` [Bug nptl/29755] " schwab@linux-m68k.org 2022-11-08 8:13 ` sam at gentoo dot org 2022-11-08 8:54 ` zhuorong.lin at outlook dot com 2022-11-08 16:51 ` adhemerval.zanella at linaro dot 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-29755-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: linkBe 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).