From: Xiyu Yang <hidden> Date: 2021-09-09 04:33:37
The reference count leak issue may take place in an error handling
path. If both conditions of tunnel->version == L2TP_HDR_VER_3 and the
return value of l2tp_v3_ensure_opt_in_linear is nonzero, the function
would directly jump to label invalid, without decrementing the reference
count of the l2tp_session object session increased earlier by
l2tp_tunnel_get_session(). This may result in refcount leaks.
Fix this issue by decrease the reference count before jumping to the
label invalid.
Signed-off-by: Xiyu Yang <redacted>
Signed-off-by: Xin Xiong <redacted>
Signed-off-by: Xin Tan <redacted>
---
net/l2tp/l2tp_core.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
From: Tom Parkin <hidden> Date: 2021-09-09 09:07:48
On Thu, Sep 09, 2021 at 12:32:00 +0800, Xiyu Yang wrote:
The reference count leak issue may take place in an error handling
path. If both conditions of tunnel->version == L2TP_HDR_VER_3 and the
return value of l2tp_v3_ensure_opt_in_linear is nonzero, the function
would directly jump to label invalid, without decrementing the reference
count of the l2tp_session object session increased earlier by
l2tp_tunnel_get_session(). This may result in refcount leaks.
I agree with your analysis. Thanks for catching this!
quoted hunk
Fix this issue by decrease the reference count before jumping to the
label invalid.
Signed-off-by: Xiyu Yang <redacted>
Signed-off-by: Xin Xiong <redacted>
Signed-off-by: Xin Tan <redacted>
---
net/l2tp/l2tp_core.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
The error paths in l2tp_udp_recv_core are a bit convoluted because of
the check (!session || !session->recv_skb) which may or may not need
to drop a session reference if triggered.
I think it could be simplified since session->recv_skb is always set
for all the current session types in the tree, but doing that is probably
a little patch series on its own.
From: Tom Parkin <hidden> Date: 2021-09-09 09:10:12
On Thu, Sep 09, 2021 at 10:01:56 +0100, Tom Parkin wrote:
On Thu, Sep 09, 2021 at 12:32:00 +0800, Xiyu Yang wrote:
quoted
The reference count leak issue may take place in an error handling
path. If both conditions of tunnel->version == L2TP_HDR_VER_3 and the
return value of l2tp_v3_ensure_opt_in_linear is nonzero, the function
would directly jump to label invalid, without decrementing the reference
count of the l2tp_session object session increased earlier by
l2tp_tunnel_get_session(). This may result in refcount leaks.
I agree with your analysis. Thanks for catching this!
Also: I forgot to mention I think this fixes:
4522a70db7aa ("l2tp: fix reading optional fields of L2TPv3")
quoted
Fix this issue by decrease the reference count before jumping to the
label invalid.
Signed-off-by: Xiyu Yang <redacted>
Signed-off-by: Xin Xiong <redacted>
Signed-off-by: Xin Tan <redacted>
---
net/l2tp/l2tp_core.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
The error paths in l2tp_udp_recv_core are a bit convoluted because of
the check (!session || !session->recv_skb) which may or may not need
to drop a session reference if triggered.
I think it could be simplified since session->recv_skb is always set
for all the current session types in the tree, but doing that is probably
a little patch series on its own.
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Thu, 9 Sep 2021 12:32:00 +0800 you wrote:
The reference count leak issue may take place in an error handling
path. If both conditions of tunnel->version == L2TP_HDR_VER_3 and the
return value of l2tp_v3_ensure_opt_in_linear is nonzero, the function
would directly jump to label invalid, without decrementing the reference
count of the l2tp_session object session increased earlier by
l2tp_tunnel_get_session(). This may result in refcount leaks.
[...]