All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Zihan Xi <zihanx@nebusec.ai>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org
Subject: Re: [PATCH net v2 0/1] net: l2tp: do not propagate multicast notification errors
Date: Mon, 24 Aug 2026 18:50:19 +0000	[thread overview]
Message-ID: <178759741938.3062482.8274115990086952612.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1787247008.git.zihanx@nebusec.ai>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 20 Aug 2026 18:40:27 +0000 you wrote:
> Hi Linux kernel maintainers,
> 
> We found and validated a issue in net/l2tp/l2tp_netlink.c. The bug is reachable by a
> non-root user via user and net namespace.
> The failure is observed on the unpatched kernel, not theoretical: the original PoC
> returned ENOBUFS after publishing live objects and then accumulated sessions.
> Here, that reachability statement refers to the finite state-commit trigger;
> the OOM transcript below is a separate root initramfs leak-mode run (UID 0,
> PID 1) used to make the leak and panic deterministic.
> We've tested it, and it should not affect any other functionality.
> Regression coverage includes the root namespace and an unprivileged user/net
> namespace, with notification-queue pressure and successful ACK paths for all
> three state-changing PoC commands; tunnel_modify was reviewed as a
> notification-only command path but was not a separate PoC trigger.
> No broader regression suite was run.
> The finite fixed-kernel runs returned ACK success for all three state-changing
> PoC commands in both namespaces. The leak run returned ENOBUFS and reached OOM
> after 41984 hidden Ethernet sessions.
> 
> [...]

Here is the summary with links:
  - [net,v2,1/1] net: l2tp: do not propagate multicast notification errors
    https://git.kernel.org/netdev/net/c/af20e269f745

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



      parent reply	other threads:[~2026-08-24 18:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 18:40 [PATCH net v2 0/1] net: l2tp: do not propagate multicast notification errors Zihan Xi
2026-08-20 18:40 ` [PATCH net v2 1/1] " Zihan Xi
2026-08-24 11:21   ` Simon Horman
2026-08-24 18:50 ` 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=178759741938.3062482.8274115990086952612.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=zihanx@nebusec.ai \
    /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.