From: patchwork-bot+netdevbpf@kernel.org
To: Chengyu Liu <lui2012qwq@gmail.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, horms@kernel.org,
khc@pm.waw.pl
Subject: Re: [PATCH net-next v3 0/2] hdlc_cisco/hdlc_fr: shut down protocol timers on ->detach
Date: Tue, 10 Nov 2026 11:40:06 +0000 [thread overview]
Message-ID: <179431080617.3894066.4928049084608834040.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261103142015.1588144-1-lui2012qwq@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 3 Nov 2026 22:20:13 +0800 you wrote:
> Both cisco and fr arm a self-re-arming timer in ->start() but never shut
> it down on the protocol-detach path: detach_hdlc_protocol() calls only
> ->detach() (never ->stop()) and then kfree()s hdlc->state, so
> unregistering an up device leaves the timer armed on freed memory. This
> is the same defect class as CVE-2026-63803 ("hdlc_ppp: sync per-proto
> timers before freeing hdlc state").
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] hdlc_cisco: shut down the keepalive timer on ->detach
https://git.kernel.org/netdev/net-next/c/27e25418faf3
- [net-next,v3,2/2] hdlc_fr: shut down the LMI timer in fr_destroy()
https://git.kernel.org/netdev/net-next/c/d8186bd919e5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-10 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 14:20 [PATCH net-next v3 0/2] hdlc_cisco/hdlc_fr: shut down protocol timers on ->detach Chengyu Liu
2026-11-03 14:20 ` [PATCH net-next v3 1/2] hdlc_cisco: shut down the keepalive timer " Chengyu Liu
2026-11-03 14:20 ` [PATCH net-next v3 2/2] hdlc_fr: shut down the LMI timer in fr_destroy() Chengyu Liu
2026-11-10 11:40 ` patchwork-bot+netdevbpf [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=179431080617.3894066.4928049084608834040.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=horms@kernel.org \
--cc=khc@pm.waw.pl \
--cc=lui2012qwq@gmail.com \
--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