Netdev List
 help / color / mirror / Atom feed
From: Maximilian Immanuel Brandtner <maxbr@linux.ibm.com>
To: john.fastabend@gmail.com, kuba@kernel.org, sd@queasysnail.net,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	horms@kernel.org, netdev@vger.kernel.org, svens@linux.ibm.com,
	brueckner@linux.ibm.com
Subject: Re: [PATCH net v2] tls: fix RX desync on overlapping skbs
Date: Fri, 14 Aug 2026 20:21:30 +0200	[thread overview]
Message-ID: <eaf24a5a2e83a7385e75e410475597f564b5ca15.camel@linux.ibm.com> (raw)
In-Reply-To: <20260813121337.3300688-1-maxbr@linux.ibm.com>

I just saw that for the v2 of this patch sashiko reported a supposed
potential null dereference which I believe to be an erroneous finding.

Sashiko claims that in tls_strp_check_queue_ok() after first =
skb_shinfo(strp->anchor)->frag_list; first may be NULL which would
result in a null dereference on seq = TCP_SKB_CB(first)->seq;

tls_strp_check_queue_ok(strp, TLS_HEADER_SIZE) is only called if inq >=
TLS_HEADER_SIZE. tcp_inq() counts real payload bytes so [copied_seq,
rcv_nxt) holds at least TLS_HEADER_SIZE bytes which live in sk-
>sk_receive_queue. tcp_recv_skb(sk, copied_seq) returns the skb
covering copied_seq. tls_strp_load_anchor_with_queue() stores it in
anchor->frag_list.

Therefore, skb_shinfo(strp->anchor)->frag_list != NULL for the check
introduced by this patch.

Kind regards,
Max Brandtner

      reply	other threads:[~2026-08-14 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 12:09 [PATCH net v2] tls: fix RX desync on overlapping skbs Maximilian Immanuel Brandtner
2026-08-14 18:21 ` Maximilian Immanuel Brandtner [this message]

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=eaf24a5a2e83a7385e75e410475597f564b5ca15.camel@linux.ibm.com \
    --to=maxbr@linux.ibm.com \
    --cc=brueckner@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sd@queasysnail.net \
    --cc=svens@linux.ibm.com \
    /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