From: f6bvp <bernard.f6bvp@gmail.com>
To: linux-hams@vger.kernel.org
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
f6bvp <bernard.f6bvp@gmail.com>
Subject: [PATCH net-next 3/3] rose: guard rose_neigh_put() against NULL in timer expiry
Date: Mon, 13 Apr 2026 19:42:38 +0200 [thread overview]
Message-ID: <20260413174238.112418-3-bernard.f6bvp@gmail.com> (raw)
In-Reply-To: <20260413174238.112418-1-bernard.f6bvp@gmail.com>
In rose_timer_expiry(), ROSE_STATE_2 calls rose_neigh_put() on
rose->neighbour without checking whether it is NULL first. The pointer
can be NULL if the connection was already being torn down by a
concurrent code path (e.g. rose_kill_by_neigh()), leading to a
NULL-pointer dereference.
Add a NULL check before the put and clear the pointer afterwards.
Signed-off-by: f6bvp <bernard.f6bvp@gmail.com>
---
net/rose/rose_timer.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/net/rose/rose_timer.c b/net/rose/rose_timer.c
index bb60a1654d61..d997d24ab081 100644
--- a/net/rose/rose_timer.c
+++ b/net/rose/rose_timer.c
@@ -180,7 +180,10 @@ static void rose_timer_expiry(struct timer_list *t)
break;
case ROSE_STATE_2: /* T3 */
- rose_neigh_put(rose->neighbour);
+ if (rose->neighbour) {
+ rose_neigh_put(rose->neighbour);
+ rose->neighbour = NULL;
+ }
rose_disconnect(sk, ETIMEDOUT, -1, -1);
break;
--
2.51.0
next prev parent reply other threads:[~2026-04-13 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 6:39 [PATCH] rose: Fix use-after-free in rose_timer_expiry Deepanshu Kartikey
2026-01-19 20:19 ` F6BVP
2026-04-13 17:42 ` [PATCH net-next 1/3] rose: fix race between loopback timer and module removal f6bvp
2026-04-13 17:42 ` [PATCH net-next 2/3] rose: clear neighbour pointer after rose_neigh_put() in state machines f6bvp
2026-04-13 20:53 ` Jakub Kicinski
2026-04-13 17:42 ` f6bvp [this message]
2026-04-13 21:21 ` [PATCH net-next 1/3] rose: fix race between loopback timer and module removal Andrew Lunn
2026-04-13 21:34 ` Jakub Kicinski
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=20260413174238.112418-3-bernard.f6bvp@gmail.com \
--to=bernard.f6bvp@gmail.com \
--cc=edumazet@google.com \
--cc=linux-hams@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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