From: Casey Schaufler <casey@schaufler-ca.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Security Module list
<linux-security-module@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: [GIT PULL] Smack patches for v5.9
Date: Tue, 4 Aug 2020 10:49:09 -0700 [thread overview]
Message-ID: <8ce85723-5656-0ee8-67a7-35597d9df0dd@schaufler-ca.com> (raw)
In-Reply-To: 8ce85723-5656-0ee8-67a7-35597d9df0dd.ref@schaufler-ca.com
Hello Linus
Here are three minor fixes to Smack for the v5.9 release.
All were found by automated checkers and have straight forward
resolution.
--
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
https://github.com/cschaufler/smack-next smack-for-5.9
for you to fetch changes up to 42a2df3e829f3c5562090391b33714b2e2e5ad4a:
Smack: prevent underflow in smk_set_cipso() (2020-07-27 13:35:12 -0700)
----------------------------------------------------------------
Dan Carpenter (2):
Smack: fix another vsscanf out of bounds
Smack: prevent underflow in smk_set_cipso()
Eric Biggers (1):
Smack: fix use-after-free in smk_write_relabel_self()
security/smack/smackfs.c | 19 ++++++++++++++++---
1 file changed, 16 insertions(+), 3 deletions(-)
next parent reply other threads:[~2020-08-04 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8ce85723-5656-0ee8-67a7-35597d9df0dd.ref@schaufler-ca.com>
2020-08-04 17:49 ` Casey Schaufler [this message]
2020-08-04 21:26 ` [GIT PULL] Smack patches for v5.9 Linus Torvalds
2020-08-04 21:43 ` Casey Schaufler
2020-08-04 21:48 ` Casey Schaufler
2020-08-06 18:09 ` pr-tracker-bot
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=8ce85723-5656-0ee8-67a7-35597d9df0dd@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.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).