[PATCH AUTOSEL 4.19 07/21] net: af_can: do not leave a dangling sk pointer in can_create()

From: Sasha Levin
Date: Sun Nov 24 2024 - 10:27:20 EST


From: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>

[ Upstream commit 811a7ca7320c062e15d0f5b171fe6ad8592d1434 ]

On error can_create() frees the allocated sk object, but sock_init_data()
has already attached it to the provided sock object. This will leave a
dangling sk pointer in the sock object and may cause use-after-free later.

Signed-off-by: Ignat Korchagin <ignat@xxxxxxxxxxxxxx>
Reviewed-by: Vincent Mailhol <mailhol.vincent@xxxxxxxxxx>
Reviewed-by: Kuniyuki Iwashima <kuniyu@xxxxxxxxxx>
Reviewed-by: Marc Kleine-Budde <mkl@xxxxxxxxxxxxxx>
Link: https://patch.msgid.link/20241014153808.51894-5-ignat@xxxxxxxxxxxxxx
Signed-off-by: Jakub Kicinski <kuba@xxxxxxxxxx>
Signed-off-by: Sasha Levin <sashal@xxxxxxxxxx>
---
net/can/af_can.c | 1 +
1 file changed, 1 insertion(+)

diff --git a/net/can/af_can.c b/net/can/af_can.c
index b3edb80921248..2e6fedffddd92 100644
--- a/net/can/af_can.c
+++ b/net/can/af_can.c
@@ -187,6 +187,7 @@ static int can_create(struct net *net, struct socket *sock, int protocol,
/* release sk on errors */
sock_orphan(sk);
sock_put(sk);
+ sock->sk = NULL;
}

errout:
--
2.43.0