netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Deepak Sharma <deepak.sharma.472935@gmail.com>
Cc: krzk@kernel.org, vadim.fedorenko@linux.dev,
	netdev@vger.kernel.org, stable@vger.kernel.org,
	linux-kernel-mentees@lists.linux.dev,
	syzbot+740e04c2a93467a0f8c8@syzkaller.appspotmail.com
Subject: Re: [PATCH net v3] net: nfc: nci: Add parameter validation for packet data
Date: Fri, 19 Sep 2025 19:52:32 +0100	[thread overview]
Message-ID: <20250919185232.GF589507@horms.kernel.org> (raw)
In-Reply-To: <20250919064545.4252-1-deepak.sharma.472935@gmail.com>

On Fri, Sep 19, 2025 at 12:15:44PM +0530, Deepak Sharma wrote:
> Syzbot reported an uninit-value bug at nci_init_req for commit
> 5aca7966d2a7 ("Merge tag 'perf-tools-fixes-for-v6.17-2025-09-16'..).
> 
> This bug arises due to very limited and poor input validation
> that was done at nic_valid_size(). This validation only
> validates the skb->len (directly reflects size provided at the
> userspace interface) with the length provided in the buffer
> itself (interpreted as NCI_HEADER). This leads to the processing
> of memory content at the address assuming the correct layout
> per what opcode requires there. This leads to the accesses to
> buffer of `skb_buff->data` which is not assigned anything yet.
> 
> Following the same silent drop of packets of invalid sizes at
> `nic_valid_size()`, add validation of the data in the respective
> handlers and return error values in case of failure. Release
> the skb if error values are returned from handlers in 
> `nci_nft_packet` and effectively do a silent drop
> 
> Possible TODO: because we silently drop the packets, the
> call to `nci_request` will be waiting for completion of request
> and will face timeouts. These timeouts can get excessively logged
> in the dmesg. A proper handling of them may require to export
> `nci_request_cancel` (or propagate error handling from the
> nft packets handlers).
> 
> Reported-by: syzbot+740e04c2a93467a0f8c8@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=740e04c2a93467a0f8c8
> Fixes: 6a2968aaf50c ("NFC: basic NCI protocol implementation)

There is a typo in the fixes tag. It should be:

Fixes: 6a2968aaf50c ("NFC: basic NCI protocol implementation")
                                                           ^^^
I expect there is no need to repost to address this.

> Tested-by: syzbot+740e04c2a93467a0f8c8@syzkaller.appspotmail.com
> Signed-off-by: Deepak Sharma <deepak.sharma.472935@gmail.com>

...

      parent reply	other threads:[~2025-09-19 18:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19  6:45 [PATCH net v3] net: nfc: nci: Add parameter validation for packet data Deepak Sharma
2025-09-19 10:59 ` Vadim Fedorenko
2025-09-19 18:52 ` Simon Horman [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=20250919185232.GF589507@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=deepak.sharma.472935@gmail.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+740e04c2a93467a0f8c8@syzkaller.appspotmail.com \
    --cc=vadim.fedorenko@linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).