[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ad0fedfd-e25b-4054-aabf-ebac46dbbcd1@redhat.com>
Date: Fri, 28 Nov 2025 16:01:47 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Geliang Tang <geliang@...nel.org>,
John Fastabend <john.fastabend@...il.com>, Jakub Kicinski <kuba@...nel.org>,
Sabrina Dubroca <sd@...asysnail.net>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Simon Horman <horms@...nel.org>
Cc: Geliang Tang <tanggeliang@...inos.cn>, netdev@...r.kernel.org,
mptcp@...ts.linux.dev, Hui Zhu <zhuhui@...inos.cn>
Subject: Re: [PATCH net-next] tls: check return value of
strp_load_anchor_with_queue
On 11/28/25 1:55 PM, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@...inos.cn>
>
> In tls_strp_load_anchor_with_queue(), when first is null, strp->anchor is
> not successfully initialized. Accessing strp->anchor afterward will result
> in a memory access error (for example, BUG: KASAN: slab-use-after-free in
> skb_copy_bits).
tls_strp_load_anchor_with_queue() has:
WARN_ON_ONCE(!first)
and AFAICS all the tls_strp_load_anchor_with_queue() call sites ensure
that the receive queue is not empty before invoking such function.
Hitting the above condition is a symtom of a prior issue that must be
identified and fixed. Please try to solve such problem instead.
/P
Powered by blists - more mailing lists