[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ-EccM49yBA+xgkR+3m5pEAJqmH_+FxfuAjijrQxaxxMUAt3Q@mail.gmail.com>
Date: Wed, 18 Sep 2019 10:41:06 -0700
From: Micah Morton <mortonm@...omium.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-security-module <linux-security-module@...r.kernel.org>
Subject: [GIT PULL] SafeSetID LSM changes for 5.4
The following changes since commit 609488bc979f99f805f34e9a32c1e3b71179d10b:
Linux 5.3-rc2 (2019-07-28 12:47:02 -0700)
are available in the Git repository at:
https://github.com/micah-morton/linux.git tags/safesetid-bugfix-5.4
for you to fetch changes up to 21ab8580b383f27b7f59b84ac1699cb26d6c3d69:
LSM: SafeSetID: Stop releasing uninitialized ruleset (2019-09-17
11:27:05 -0700)
----------------------------------------------------------------
Fix for SafeSetID bug that was introduced in 5.3
Jann Horn sent some patches to fix some bugs in SafeSetID for 5.3. After
he had done his testing there were a couple small code tweaks that went
in and caused this bug. From what I can see SafeSetID is broken in 5.3
and crashes the kernel every time during initialization if you try to
use it. I came across this bug when backporting Jann's changes for 5.3
to older kernels (4.14 and 4.19). I've tested on a Chrome OS device and
verified that this change fixes things. Unless I'm missing something it
doesn't seem super useful to have this change bake in linux-next, since it is
completely broken in 5.3 and nobody noticed.
Signed-off-by: Micah Morton <mortonm@...omium.org>
----------------------------------------------------------------
Micah Morton (1):
LSM: SafeSetID: Stop releasing uninitialized ruleset
security/safesetid/securityfs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Powered by blists - more mailing lists