selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Garrett Tucker <gtucker@redhat.com>
To: selinux@vger.kernel.org
Subject: libsepol CVE patch issue
Date: Fri, 23 Jul 2021 11:42:50 -0400	[thread overview]
Message-ID: <CAEN2sdo3wVKXnEUASFTbhR81kOYNgU1CbR0XMUNCTt8keOHC6A@mail.gmail.com> (raw)

Hi everyone, I'm a product security engineer at Red Hat and we noticed
that libsepol CVE-2021-36087 was assigned, and marked as resolved
within the OSS-Fuzz project. The patch info provided for the CVE
appears to be wrong, and after looking into the provided commits and
commit ranges, these seem to be the wrong commits and commit ranges
for this CVE.

Would anyone be able to confirm if there is a fix for this CVE, and if
so, point us towards the correct patch for this.

All the best,

Garrett


             reply	other threads:[~2021-07-23 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 15:42 Garrett Tucker [this message]
2021-07-23 17:18 ` libsepol CVE patch issue James Carter
2021-07-23 17:32   ` Garrett Tucker

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=CAEN2sdo3wVKXnEUASFTbhR81kOYNgU1CbR0XMUNCTt8keOHC6A@mail.gmail.com \
    --to=gtucker@redhat.com \
    --cc=selinux@vger.kernel.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 NNTP newsgroup(s).