From: patchwork-bot+netdevbpf@kernel.org
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: nicolas.ferre@microchip.com, claudiu.beznea@tuxon.dev,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com,
rafalo@cadence.com, Andrei.Pistirica@microchip.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org, stable@vger.kernel.org
Subject: Re: [PATCH net 1/2] net: macb: fix use-after-free access to PTP clock
Date: Thu, 19 Mar 2026 00:44:18 +0000 [thread overview]
Message-ID: <177388105853.935482.1067473312108784098.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260316103826.74506-1-pchelkin@ispras.ru>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 16 Mar 2026 13:38:24 +0300 you wrote:
> PTP clock is registered on every opening of the interface and destroyed on
> every closing. However it may be accessed via get_ts_info ethtool call
> which is possible while the interface is just present in the kernel.
>
> BUG: KASAN: use-after-free in ptp_clock_index+0x47/0x50 drivers/ptp/ptp_clock.c:426
> Read of size 4 at addr ffff8880194345cc by task syz.0.6/948
>
> [...]
Here is the summary with links:
- [net,1/2] net: macb: fix use-after-free access to PTP clock
https://git.kernel.org/netdev/net/c/8da13e6d63c1
- [net,2/2] net: macb: fix uninitialized rx_fs_lock
https://git.kernel.org/netdev/net/c/34b11cc56e43
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-03-19 0:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 10:38 [PATCH net 1/2] net: macb: fix use-after-free access to PTP clock Fedor Pchelkin
2026-03-19 0:44 ` 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=177388105853.935482.1067473312108784098.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Andrei.Pistirica@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=pchelkin@ispras.ru \
--cc=rafalo@cadence.com \
--cc=richardcochran@gmail.com \
--cc=stable@vger.kernel.org \
/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