diff options
author | Jia-Ju Bai <baijiaju1990@gmail.com> | 2019-07-23 18:00:15 +0800 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-10-07 18:59:33 +0200 |
commit | 88b4b5b7e2a89146ba2738d8ed0093150a4f0138 (patch) | |
tree | 5fb7e1792c958a1c90b55ee5a5787e8b6eb32cbf /drivers/pci/pci-sysfs.c | |
parent | 0728352751bbefc04a68150d82f84fe145eac2ce (diff) | |
download | linux-stable-88b4b5b7e2a89146ba2738d8ed0093150a4f0138.tar.gz linux-stable-88b4b5b7e2a89146ba2738d8ed0093150a4f0138.tar.bz2 linux-stable-88b4b5b7e2a89146ba2738d8ed0093150a4f0138.zip |
security: smack: Fix possible null-pointer dereferences in smack_socket_sock_rcv_skb()
[ Upstream commit 3f4287e7d98a2954f20bf96c567fdffcd2b63eb9 ]
In smack_socket_sock_rcv_skb(), there is an if statement
on line 3920 to check whether skb is NULL:
if (skb && skb->secmark != 0)
This check indicates skb can be NULL in some cases.
But on lines 3931 and 3932, skb is used:
ad.a.u.net->netif = skb->skb_iif;
ipv6_skb_to_auditdata(skb, &ad.a, NULL);
Thus, possible null-pointer dereferences may occur when skb is NULL.
To fix these possible bugs, an if statement is added to check skb.
These bugs are found by a static analysis tool STCheck written by us.
Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/pci/pci-sysfs.c')
0 files changed, 0 insertions, 0 deletions