linux-kernel.vger.kernel.org archive mirror
 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.7-rc6
Date: Thu, 21 May 2020 16:01:42 -0700	[thread overview]
Message-ID: <3155dfe9-0b22-9519-f84f-152542606325@canonical.com> (raw)

Hi Linus,

Can you please pull the following bug fixes for apparmor

Thanks!

- John

The following changes since commit b85051e755b0e9d6dd8f17ef1da083851b83287d:

  Merge tag 'fixes-for-5.7-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux (2020-05-20 13:23:55 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor tags/apparmor-pr-2020-05-21

for you to fetch changes up to c54d481d71c6849e044690d3960aaebc730224cc:

  apparmor: Fix use-after-free in aa_audit_rule_init (2020-05-21 15:25:51 -0700)

----------------------------------------------------------------
+ Bug Fixes
  - Fix use-after-free in aa_audit_rule_init
  - Fix refcnt leak in policy_update
  - Fix potential label refcnt leak in aa_change_profile

----------------------------------------------------------------
Navid Emamdoost (1):
      apparmor: Fix use-after-free in aa_audit_rule_init

Xiyu Yang (2):
      apparmor: fix potential label refcnt leak in aa_change_profile
      apparmor: Fix aa_label refcnt leak in policy_update

 security/apparmor/apparmorfs.c | 3 ++-
 security/apparmor/audit.c      | 3 ++-
 security/apparmor/domain.c     | 3 +--
 3 files changed, 5 insertions(+), 4 deletions(-)

             reply	other threads:[~2020-05-21 23:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 23:01 John Johansen [this message]
2020-05-21 23:50 ` [GIT PULL] apparmor bug fixes for v5.7-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=3155dfe9-0b22-9519-f84f-152542606325@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;
as well as URLs for NNTP newsgroup(s).