All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Raczynski <j.raczynski@samsung.com>
Cc: linux@armlinux.org.uk, andrew@lunn.ch, hkallweit1@gmail.com,
	netdev@vger.kernel.org, wenjing.shan@samsung.com
Subject: Re: [PATCH 1/2] net/mdiobus: Fix potential out-of-bounds read/write access
Date: Wed, 11 Jun 2025 12:10:31 +0000	[thread overview]
Message-ID: <174964383100.3294450.3135324219520894757.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250609153147.1435432-1-j.raczynski@samsung.com>

Hello:

This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Mon,  9 Jun 2025 17:31:46 +0200 you wrote:
> When using publicly available tools like 'mdio-tools' to read/write data
> from/to network interface and its PHY via mdiobus, there is no verification of
> parameters passed to the ioctl and it accepts any mdio address.
> Currently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,
> but it is possible to pass higher value than that via ioctl.
> While read/write operation should generally fail in this case,
> mdiobus provides stats array, where wrong address may allow out-of-bounds
> read/write.
> 
> [...]

Here is the summary with links:
  - [1/2] net/mdiobus: Fix potential out-of-bounds read/write access
    https://git.kernel.org/netdev/net/c/0e629694126c
  - [2/2] net/mdiobus: Fix potential out-of-bounds clause 45 read/write access
    https://git.kernel.org/netdev/net/c/260388f79e94

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2025-06-11 12:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250609144014eucas1p2ee94d7aabff15fbadcc1af1fa64ce22d@eucas1p2.samsung.com>
2025-06-09 14:37 ` [PATCH] net/mdiobus: Fix potential out-of-bounds read/write access Jakub Raczynski
2025-06-09 14:57   ` Russell King (Oracle)
2025-06-09 15:31     ` [PATCH 1/2] " Jakub Raczynski
2025-06-09 15:31       ` [PATCH 2/2] net/mdiobus: Fix potential out-of-bounds clause 45 " Jakub Raczynski
2025-06-11 12:10       ` patchwork-bot+netdevbpf [this message]
2025-06-25 15:23       ` [PATCH 1/2] net/mdiobus: Fix potential out-of-bounds " Dan Carpenter
2025-06-25 16:38         ` Andrew Lunn
2025-06-26  7:15         ` Russell King (Oracle)
2025-06-26  8:55           ` Jakub Raczynski

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=174964383100.3294450.3135324219520894757.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=hkallweit1@gmail.com \
    --cc=j.raczynski@samsung.com \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=wenjing.shan@samsung.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.