Linux Security Modules development
 help / color / mirror / Atom feed
From: John Johansen <john.johansen@canonical.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKLM <linux-kernel@vger.kernel.org>,
	"open list:SECURITY SUBSYSTEM" 
	<linux-security-module@vger.kernel.org>
Subject: [GIT PULL] apparmor bug fixes for v5.3-rc6
Date: Tue, 18 Jun 2019 18:44:31 -0700	[thread overview]
Message-ID: <cfc8f629-4ffa-e64e-f23f-2f4cffca4f18@canonical.com> (raw)

Hi Linus,

Can you please pull the following bug fixes for apparmor

Thanks!

- John


The following changes since commit 9e0babf2c06c73cda2c0cd37a1653d823adb40ec:

  Linux 5.2-rc5 (2019-06-16 08:49:45 -1000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor tags/apparmor-pr-2019-06-18

for you to fetch changes up to 156e42996bd84eccb6acf319f19ce0cb140d00e3:

  apparmor: reset pos on failure to unpack for various functions (2019-06-18 16:04:16 -0700)

----------------------------------------------------------------
+ Bug Fixes
  - Fix PROFILE_MEDIATES for untrusted input
  - enforce nullbyte at end of tag string
  - reset pos on failure to unpack for various functions

----------------------------------------------------------------
Jann Horn (1):
      apparmor: enforce nullbyte at end of tag string

John Johansen (1):
      apparmor: fix PROFILE_MEDIATES for untrusted input

Mike Salvatore (1):
      apparmor: reset pos on failure to unpack for various functions

 security/apparmor/include/policy.h | 11 ++++++++-
 security/apparmor/policy_unpack.c  | 49 +++++++++++++++++++++++++++++++-------
 2 files changed, 50 insertions(+), 10 deletions(-)

             reply	other threads:[~2019-06-19  1:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19  1:44 John Johansen [this message]
2019-06-19 19:00 ` [GIT PULL] apparmor bug fixes for v5.3-rc6 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=cfc8f629-4ffa-e64e-f23f-2f4cffca4f18@canonical.com \
    --to=john.johansen@canonical.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