From: Paolo Abeni <pabeni@redhat.com>
To: Kohei Enju <enjuk@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, horms@kernel.org,
kohei.enju@gmail.com, kuba@kernel.org, kuniyu@google.com,
linux-hams@vger.kernel.org, mingo@kernel.org,
netdev@vger.kernel.org,
syzbot+e04e2c007ba2c80476cb@syzkaller.appspotmail.com,
tglx@linutronix.de
Subject: Re: [PATCH net v1] rose: fix dangling neighbour pointers in rose_rt_device_down()
Date: Thu, 26 Jun 2025 11:31:04 +0200 [thread overview]
Message-ID: <7a25c9c4-610c-4e93-8855-1ec335cd2b64@redhat.com> (raw)
In-Reply-To: <20250625133911.29344-1-enjuk@amazon.com>
On 6/25/25 3:38 PM, Kohei Enju wrote:
>> Message-ID: <20250625095005.66148-2-enjuk@amazon.com> (raw)
>>
>> There are two bugs in rose_rt_device_down() that can lead to
>> use-after-free:
>>
>> 1. The loop bound `t->count` is modified within the loop, which can
>> cause the loop to terminate early and miss some entries.
>>
>> 2. When removing an entry from the neighbour array, the subsequent entries
>> are moved up to fill the gap, but the loop index `i` is still
>> incremented, causing the next entry to be skipped.
>>
>> For example, if a node has three neighbours (A, B, A) and A is being
>> removed:
>> - 1st iteration (i=0): A is removed, array becomes (B, A, A), count=2
>> - 2nd iteration (i=1): We now check A instead of B, skipping B entirely
>> - 3rd iteration (i=2): Loop terminates early due to count=2
>>
>> This leaves the second A in the array with count=2, but the rose_neigh
>> structure has been freed. Accessing code assumes that the first `count`
>> entries are valid pointers, causing a use-after-free when it accesses
>> the dangling pointer.
>
> (Resending because I forgot to cite the patch, please ignore the former
> reply from me. Sorry for messing up.)
This resend was not needed.
>
> The example ([Senario2] below) in the commit message was incorrect.
Please send an updated version of the patch including the correct
description in the commit message.
[...]
>> @@ -497,22 +497,14 @@ void rose_rt_device_down(struct net_device *dev)
>> t = rose_node;
>> rose_node = rose_node->next;
>>
>> - for (i = 0; i < t->count; i++) {
>> + for (i = t->count - 1; i >= 0; i--) {
>> if (t->neighbour[i] != s)
>> continue;
>>
>> t->count--;
>>
>> - switch (i) {
>> - case 0:
>> - t->neighbour[0] = t->neighbour[1];
>> - fallthrough;
>> - case 1:
>> - t->neighbour[1] = t->neighbour[2];
>> - break;
>> - case 2:
>> - break;
>> - }
>> + for (j = i; j < t->count; j++)
>> + t->neighbour[j] = t->neighbour[j + 1];
You can possibly use memmove() here instead of adding another loop.
/P
next prev parent reply other threads:[~2025-06-26 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 9:49 [PATCH net v1] rose: fix dangling neighbour pointers in rose_rt_device_down() Kohei Enju
2025-06-25 13:06 ` Kohei Enju
2025-06-25 13:38 ` Kohei Enju
2025-06-26 9:31 ` Paolo Abeni [this message]
2025-06-28 11:01 ` Kohei Enju
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=7a25c9c4-610c-4e93-8855-1ec335cd2b64@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enjuk@amazon.com \
--cc=horms@kernel.org \
--cc=kohei.enju@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-hams@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+e04e2c007ba2c80476cb@syzkaller.appspotmail.com \
--cc=tglx@linutronix.de \
/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).