From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Siddhesh Poyarekar <sipoyare@redhat.com>,
Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 4/5] gdb: in SECURITY.txt, add notes on reporting exec and debug bugs
Date: Mon, 12 Oct 2026 14:49:13 +0100 [thread overview]
Message-ID: <8152e3e493133b41bcf71f4af9309bff3322f10b.1791812758.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1791812758.git.aburgess@redhat.com>
The previous commit clarified the wording about bugs related to
parsing malformed executables and debug information. Bugs in this
area can be security bugs, but will not be treated with high priority
by the GDB project.
Given this, it does not seem sensible to me that these bugs should be
reported via the more secret bug reporting path. At the end of the
day fixing these bugs is unlikely to be a priority, so the bugs will
likely end up in the public bugzilla anyway.
I propose that we advise that these bugs just be added to the public
bugzilla from the start.
I'm aware that this advice might be a little contentious, and that is
why I've carved this change out from the previous one. This makes it
easier for people to agree with the previous commit, but disagree with
this one.
---
gdb/SECURITY.txt | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/gdb/SECURITY.txt b/gdb/SECURITY.txt
index 533b70b5875..b484a1f65a1 100644
--- a/gdb/SECURITY.txt
+++ b/gdb/SECURITY.txt
@@ -238,6 +238,13 @@ Reporting Non-Security Bugs
https://sourceware.org/bugzilla/
+ Bugs related to parsing malformed executables and debug information
+ should be reported through the public bugzilla. This is an area of
+ GDB containing known bugs, and as discussed above, it is advised
+ that users mitigate these bugs by running within a sandboxed
+ environment. As such, these bugs are considered to pose limited
+ risk to users.
+
Reporting Security Bugs
-----------------------
--
2.25.4
next prev parent reply other threads:[~2026-10-12 13:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 13:49 [PATCH 0/5] SECURITY.txt changes Andrew Burgess
2026-10-12 13:49 ` [PATCH 1/5] gdb: fix minor grammar error in SECURITY.txt Andrew Burgess
2026-10-14 15:02 ` Tom Tromey
2026-10-12 13:49 ` [PATCH 2/5] gdb: extend SECURITY.txt to highlight additional remote debugging risks Andrew Burgess
2026-10-13 15:22 ` Siddhesh Poyarekar
2026-10-14 15:08 ` Tom Tromey
2026-10-14 16:10 ` Siddhesh Poyarekar
2026-10-16 14:24 ` Andrew Burgess
2026-10-16 14:27 ` Siddhesh Poyarekar
2026-10-12 13:49 ` [PATCH 3/5] gdb: extend SECURITY.txt discussion of DWARF/BFD parser bugs Andrew Burgess
2026-10-13 15:30 ` Siddhesh Poyarekar
2026-10-14 15:12 ` Tom Tromey
2026-10-14 16:16 ` Siddhesh Poyarekar
2026-10-14 17:28 ` Carlos O'Donell
2026-10-12 13:49 ` Andrew Burgess [this message]
2026-10-12 13:49 ` [PATCH 5/5] gdb: improve SECURITY.txt relating to embedded language bugs Andrew Burgess
2026-10-14 15:44 ` [PATCH 0/5] SECURITY.txt changes Tom Tromey
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=8152e3e493133b41bcf71f4af9309bff3322f10b.1791812758.git.aburgess@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sipoyare@redhat.com \
/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