public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/25733] mallopt(M_MXFAST) can set global_max_fast to 0
Date: Tue, 31 Mar 2020 17:30:59 +0000 [thread overview]
Message-ID: <bug-25733-131-fV9Wgj775c@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25733-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25733
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
Flags| |security-
--- Comment #3 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to dj@redhat.com from comment #2)
> It looks like changing "s == 0" to "s < SMALLBIN_WIDTH" in the
> set_max_fast() macro (around line 1622 in malloc/malloc.c) ensures that
> global_max_fast is never set to zero. This fix should apply and work for
> all current glibc versions.
Is this issue a security defect?
How likely is it that someone would call mallopt(M_MXFAST, <a value of 1-7>)?
I will argue that I think it is very unlikely someone would use this interface
with those values, so therefore I don't think this is a security bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-03-31 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 17:36 [Bug malloc/25733] New: " maxkamper at outlook dot com
2020-03-26 17:41 ` [Bug malloc/25733] " maxkamper at outlook dot com
2020-03-31 17:16 ` dj at redhat dot com
2020-03-31 17:30 ` carlos at redhat dot com [this message]
2020-03-31 17:44 ` dj at redhat dot com
2020-04-06 20:27 ` dj at redhat dot com
2020-04-06 21:04 ` dj at redhat dot com
2020-07-08 16:47 ` jsm28 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-25733-131-fV9Wgj775c@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).