From: Simon Horman <horms@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Kangzheng Gu <xiaoguai0992@gmail.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
kees@kernel.org, thorsten.blum@linux.dev, arnd@arndb.de,
sjur.brandeland@stericsson.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v5] net: caif: fix stack out-of-bounds write in cfctrl_link_setup()
Date: Tue, 14 Apr 2026 12:29:51 +0100 [thread overview]
Message-ID: <20260414112951.GD469338@kernel.org> (raw)
In-Reply-To: <255224dc-0a55-4a0c-95f3-b84d4c6b3897@redhat.com>
On Mon, Apr 13, 2026 at 11:30:53AM +0200, Paolo Abeni wrote:
> On 4/12/26 3:57 PM, Simon Horman wrote:
> > I am wondering if it would be best to follow the pattern for
> > writing linkparam.u.utility.name elsewhere in this function.
> > That:
> > 1. Uses a somewhat more succinct loop control structure
> > 2. Silently truncates input without updating cmdrsp if overrun would occur
> >
> > Something like this (compile tested only!):
> >
> > diff --git a/net/caif/cfctrl.c b/net/caif/cfctrl.c
> > index c6cc2bfed65d..ba184c11386e 100644
> > --- a/net/caif/cfctrl.c
> > +++ b/net/caif/cfctrl.c
> > @@ -15,6 +15,7 @@
> > #include <net/caif/cfctrl.h>
> >
> > #define container_obj(layr) container_of(layr, struct cfctrl, serv.layer)
> > +#define RFM_VOLUME_LEN 20
> > #define UTILITY_NAME_LENGTH 16
> > #define CFPKT_CTRL_PKT_LEN 20
> >
> > @@ -414,10 +415,11 @@ static int cfctrl_link_setup(struct cfctrl *cfctrl, struct cfpkt *pkt, u8 cmdrsp
> > */
> > linkparam.u.rfm.connid = cfpkt_extr_head_u32(pkt);
> > cp = (u8 *) linkparam.u.rfm.volume;
> > - for (tmp = cfpkt_extr_head_u8(pkt);
> > - cfpkt_more(pkt) && tmp != '\0';
> > - tmp = cfpkt_extr_head_u8(pkt))
> > + caif_assert(sizeof(linkparam.u.rfm.volume) >= RFM_VOLUME_LEN);
> > + for(i = 0; i < RFM_VOLUME_LEN - 1 && cfpkt_more(pkt); i++) {
> > + tmp = cfpkt_extr_head_u8(pkt);
> > *cp++ = tmp;
> > + }
> > *cp = '\0';
> >
> > if (CFCTRL_ERR_BIT & cmdrsp)
>
> I agree that the code suggested by Simon is clearer. Note that AFAICS it
> lacks an additional `tmp!= '\0'` check to break the loop, but even with
> that added it should be preferable.
Sorry, I left out the `tmp!= '\0' check.
That was unintentional and I agree it should be there.
next prev parent reply other threads:[~2026-04-14 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKvcANP6ihR9ZJpm73ep6aTPqzcpVhTHsVSgGBd28HwwfdBcxw@mail.gmail.com>
2026-03-29 19:03 ` [PATCH v3] net: caif: fix stack out-of-bounds write in cfctrl_link_setup() Kangzheng Gu
2026-03-30 6:53 ` [PATCH v4] " Kangzheng Gu
2026-04-02 9:05 ` Paolo Abeni
2026-04-08 12:53 ` [PATCH v5] " Kangzheng Gu
2026-04-12 13:57 ` Simon Horman
2026-04-13 9:30 ` Paolo Abeni
2026-04-14 11:29 ` Simon Horman [this message]
2026-04-20 8:09 ` Kangzheng Gu
2026-04-20 8:14 ` Arnd Bergmann
2026-04-20 13:38 ` Kangzheng Gu
2026-03-30 14:24 ` [PATCH v3] " kernel test robot
2026-03-30 15:32 ` kernel test robot
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=20260414112951.GD469338@kernel.org \
--to=horms@kernel.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sjur.brandeland@stericsson.com \
--cc=stable@vger.kernel.org \
--cc=thorsten.blum@linux.dev \
--cc=xiaoguai0992@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.