mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicholas Dudar <main.kalliope@gmail.com>
To: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com, akpm@linux-foundation.org
Cc: martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
	jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
	davem@davemloft.net, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org, deller@gmx.de
Subject: [PATCH bpf] bpf: Fix page double free in test_bpf skb setup
Date: Wed, 16 Sep 2026 22:38:34 -0400	[thread overview]
Message-ID: <20260917023834.2760055-1-main.kalliope@gmail.com> (raw)

build_test_skb() transfers page ownership to an skb with
skb_add_rx_frag(). If either allocation in the second loop iteration fails,
kfree_skb() releases page[0], but the error path then falls through and
frees page[0] again.

Return after freeing skb[0], since page[0] is already owned by the skb at
that point; the raw page cleanup is only correct for the first iteration.

Fixes: 76db8087c4c9 ("net: bpf: add a test for skb_segment in test_bpf module")
Assisted-by: Codex:gpt-6-astra
Signed-off-by: Nicholas Dudar <main.kalliope@gmail.com>
---
Please queue this fix for stable. The double-free has been present since
v4.17 and is reachable when the test_bpf skb test encounters an allocation
failure.

A separate bpf-next patch allowing TEST_BPF=y depends on this fix and will
be posted after this patch.

---
 lib/test_bpf.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/test_bpf.c b/lib/test_bpf.c
index af6f3340c034..6104b97764bb 100644
--- a/lib/test_bpf.c
+++ b/lib/test_bpf.c
@@ -15214,6 +15214,7 @@ err_skb1:
 	__free_page(page[1]);
 err_page1:
 	kfree_skb(skb[0]);
+	return NULL;
 err_skb0:
 	__free_page(page[0]);
 err_page0:

base-commit: c0b95a11b38b47ed4b88fa2cebd86bfc4b244c5d

             reply	other threads:[~2026-09-17  2:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17  2:38 Nicholas Dudar [this message]
2026-09-17  3:11 ` Alexei Starovoitov

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=20260917023834.2760055-1-main.kalliope@gmail.com \
    --to=main.kalliope@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=deller@gmx.de \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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

all inboxes | Powered by JetHome®