All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Grund <theflamefire89@gmail.com>
To: stable@vger.kernel.org
Cc: Alexander Grund <theflamefire89@gmail.com>
Subject: [PATCH 4.9 0/1] security,selinux,smack: kill security_task_wait hook
Date: Mon, 11 Jul 2022 11:56:07 +0200	[thread overview]
Message-ID: <20220711095608.4723-1-theflamefire89@gmail.com> (raw)

The following (backported) patch removes a hook which has already been removed upstream. [1]
Reason is that a permission denial can lead to soft lockups and zombies.
A reproducer can be found in the initial report. [2]
I hence consider this a bugfix which is allowed for stable branches.

Background:
To reduce divergence of 4.9 to upstream before proposing to apply upstream commit
3dfc9b02864bt (LSM: Initialize security_hook_heads upon registration.)
I'm checking which changes to the LSM hooks may be applicable to 4.9 as
doing so after backporting 33dfc9b02864bt will lead to conflicts for each such commit.

[1] https://patchwork.kernel.org/project/linux-security-module/patch/1484069312-26653-1-git-send-email-sds@tycho.nsa.gov/
[2] https://patchwork.kernel.org/project/selinux/patch/58736B2E.90201@huawei.com

Stephen Smalley (1):
  security,selinux,smack: kill security_task_wait hook

 include/linux/lsm_hooks.h  |  7 -------
 include/linux/security.h   |  6 ------
 kernel/exit.c              | 19 ++-----------------
 security/security.c        |  6 ------
 security/selinux/hooks.c   |  6 ------
 security/smack/smack_lsm.c | 20 --------------------
 6 files changed, 2 insertions(+), 62 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-07-11 10:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  9:56 Alexander Grund [this message]
2022-07-11  9:56 ` [PATCH 4.9 1/1] security,selinux,smack: kill security_task_wait hook Alexander Grund
2022-07-23  8:37   ` Alexander Grund
2022-07-23 14:47     ` Greg KH

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=20220711095608.4723-1-theflamefire89@gmail.com \
    --to=theflamefire89@gmail.com \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.