Re: [PATCH iproute2 0/5] netlink receive path hardening

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:

On Sun,  8 Nov 2026 17:43:57 -0800 you wrote:
> Six scanner reports all landed on the same code, so they are better
> fixed together than one at a time. The time() seeding was parallel
> discovery: Florian reported it on netdev independently of the two
> scanner findings that flagged it.
> 
> The common thread is that iproute2 trusted whatever came back from its
> own socket. The sender went unchecked until after the framing checks,
> and in the ss -D case until after the datagram had been written to the
> dump file. The framing walk assumed every message in a datagram is
> padded. Any process with CAP_NET_ADMIN over the namespace could use
> that to inject events into a monitor, or to keep a dump from ever
> completing.
> 
> [...]

Here is the summary with links:
  - [iproute2,1/5] netlink: use a counter for sequence numbers
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=23df79c6c71c
  - [iproute2,2/5] netlink: ignore messages not sent by the kernel
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=29548251e33f
  - [iproute2,3/5] netlink: connect sockets to the kernel
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=31232dbd684f
  - [iproute2,4/5] netlink: handle unpadded last message in receive loops
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=51d90a2d062f
  - [iproute2,5/5] libnetlink: do not read past datagram when recording dump
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=575421242b2e

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