NFC on Linux
 help / color / mirror / Atom feed
From: Bryam Vargas <hexlabsecurity@proton.me>
To: Doruk Tan Ozturk <doruk@0sec.ai>
Cc: David Heidelberg <david@ixit.cz>, Simon Horman <horms@kernel.org>,
	oe-linux-nfc@lists.linux.dev
Subject: Re: [PATCH net] nfc: fdp: bound the device-supplied read size in fdp_nci_i2c_read()
Date: Fri, 24 Jul 2026 10:26:10 +0000	[thread overview]
Message-ID: <20260724102605.16377-1-hexlabsecurity@proton.me> (raw)
In-Reply-To: <20260720132133.69635-1-doruk@0sec.ai>

Doruk,

That's generous of you. We landed on the same missing bound;
your patch is a clean fix for the overflow itself. I'll repost my v2 as
v3 rebased on current net so David has something current to pick up -- it
keeps the lower-bound reject (len < FDP_NCI_I2C_MIN_PAYLOAD, the one Simon
flagged) and the skb leak fix in the same loop.

I'll Cc you on the v3.

Thanks,
Bryam


      reply	other threads:[~2026-07-24 10:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11 12:36 [PATCH net] nfc: fdp: bound the device-supplied read size in fdp_nci_i2c_read() Doruk Tan Ozturk
2026-07-20 10:16 ` Simon Horman
2026-07-20 10:19   ` David Heidelberg
2026-07-20 13:21     ` Doruk Tan Ozturk
2026-07-24 10:26       ` Bryam Vargas [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=20260724102605.16377-1-hexlabsecurity@proton.me \
    --to=hexlabsecurity@proton.me \
    --cc=david@ixit.cz \
    --cc=doruk@0sec.ai \
    --cc=horms@kernel.org \
    --cc=oe-linux-nfc@lists.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