LSM: general protection fault in legacy_parse_param
authorCasey Schaufler <casey@schaufler-ca.com>
Thu, 27 Jan 2022 04:51:00 +0000 (04:51 +0000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 8 Apr 2022 12:23:54 +0000 (14:23 +0200)
commitf3f93a1aaafc3032e0a9655fb43deccfb3e953a3
treee2a940093e94eca5eefa1b4e19430adf92cfed59
parentc331c9d1d2b7a5ce875f8f1ac53e3987f73ecc75
LSM: general protection fault in legacy_parse_param

[ Upstream commit ecff30575b5ad0eda149aadad247b7f75411fd47 ]

The usual LSM hook "bail on fail" scheme doesn't work for cases where
a security module may return an error code indicating that it does not
recognize an input.  In this particular case Smack sees a mount option
that it recognizes, and returns 0. A call to a BPF hook follows, which
returns -ENOPARAM, which confuses the caller because Smack has processed
its data.

The SELinux hook incorrectly returns 1 on success. There was a time
when this was correct, however the current expectation is that it
return 0 on success. This is repaired.

Reported-by: syzbot+d1e3b1d92d25abf97943@syzkaller.appspotmail.com
Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
Acked-by: James Morris <jamorris@linux.microsoft.com>
Signed-off-by: Paul Moore <paul@paul-moore.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
security/security.c
security/selinux/hooks.c