From: Xiaochen Zou <xzou017@ucr.edu>
To: greg@kroah.com
Cc: stable@vger.kernel.org, netdev@vger.kernel.org,
linux-can@vger.kernel.org
Subject: [PATCH 0/1] can: fix a potential UAF access in j1939_session_deactivate()
Date: Tue, 13 Jul 2021 13:21:44 -0700 [thread overview]
Message-ID: <aa64ef28-35d8-9deb-2756-8080296b7e3e@ucr.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
Xiaochen Zou (1):
can: fix a potential UAF access in j1939_session_deactivate(). Both
session and session->priv may be freed in
j1939_session_deactivate_locked(). It leads to potential UAF read
and write in j1939_session_list_unlock(). The free chain is
j1939_session_deactivate_locked()->j1939_session_put()->__j1939_session_release()->j1939_session_destroy().
To fix this bug, I moved j1939_session_put() behind
j1939_session_deactivate_locked(), and guarded it with a check of
active since the session would be freed only if active is true.
net/can/j1939/transport.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
--
2.17.1
From 9c4733d093e05db22eb89825579c83e020c3c1a6 Mon Sep 17 00:00:00 2001
From: Xiaochen Zou <xzou017@ucr.edu>
Date: Tue, 13 Jul 2021 13:15:59 -0700
Subject: [PATCH 1/1] can: fix a potential UAF access in
j1939_session_deactivate().
To: greg@kroah.com
Cc: stable@vger.kernel.org,netdev@vger.kernel.org,linux-can@vger.kernel.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------2.17.1"
This is a multi-part message in MIME format.
[-- Attachment #2: Attached Message Part --]
[-- Type: text/plain, Size: 620 bytes --]
Both session and session->priv may be freed in
j1939_session_deactivate_locked(). It leads to potential UAF read and write
in j1939_session_list_unlock(). The free chain is
j1939_session_deactivate_locked()->j1939_session_put()->__j1939_session_release()->j1939_session_destroy().
To fix this bug, I moved j1939_session_put() behind
j1939_session_deactivate_locked(), and guarded it with a check of active
since the session would be freed only if active is true.
Signed-off-by: Xiaochen Zou <xzou017@ucr.edu>
---
net/can/j1939/transport.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
[-- Attachment #3: 0001-can-fix-a-potential-UAF-access-in-j1939_session_deac.patch --]
[-- Type: text/x-patch, Size: 1387 bytes --]
diff --git a/net/can/j1939/transport.c b/net/can/j1939/transport.c
index c3946c355882..c64bd5e8118a 100644
--- a/net/can/j1939/transport.c
+++ b/net/can/j1939/transport.c
@@ -1067,7 +1067,6 @@ static bool j1939_session_deactivate_locked(struct j1939_session *session)
list_del_init(&session->active_session_list_entry);
session->state = J1939_SESSION_DONE;
- j1939_session_put(session);
}
return active;
@@ -1080,6 +1079,8 @@ static bool j1939_session_deactivate(struct j1939_session *session)
j1939_session_list_lock(session->priv);
active = j1939_session_deactivate_locked(session);
j1939_session_list_unlock(session->priv);
+ if (active)
+ j1939_session_put(session);
return active;
}
@@ -2127,6 +2128,7 @@ void j1939_simple_recv(struct j1939_priv *priv, struct sk_buff *skb)
int j1939_cancel_active_session(struct j1939_priv *priv, struct sock *sk)
{
struct j1939_session *session, *saved;
+ bool active;
netdev_dbg(priv->ndev, "%s, sk: %p\n", __func__, sk);
j1939_session_list_lock(priv);
@@ -2140,7 +2142,9 @@ int j1939_cancel_active_session(struct j1939_priv *priv, struct sock *sk)
j1939_session_put(session);
session->err = ESHUTDOWN;
- j1939_session_deactivate_locked(session);
+ active = j1939_session_deactivate_locked(session);
+ if (active)
+ j1939_session_put(session);
}
}
j1939_session_list_unlock(priv);
next reply other threads:[~2021-07-13 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 20:21 Xiaochen Zou [this message]
2021-07-14 6:49 ` [PATCH 0/1] can: fix a potential UAF access in j1939_session_deactivate() 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=aa64ef28-35d8-9deb-2756-8080296b7e3e@ucr.edu \
--to=xzou017@ucr.edu \
--cc=greg@kroah.com \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox