mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: shaurya <ssranevjti@gmail.com>
To: syzbot+be97dd4da14ae88b6ba4@syzkaller.appspotmail.com
Cc: davem@davemloft.net, edumazet@google.com,
	herbert@gondor.apana.org.au, horms@kernel.org, kuba@kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	pabeni@redhat.com, steffen.klassert@secunet.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] kernel BUG in set_ipsecrequest
Date: Sun, 19 Oct 2025 23:59:34 +0530	[thread overview]
Message-ID: <1b4aeb68-bf9a-40a1-ab86-a52ef91eb3a4@gmail.com> (raw)
In-Reply-To: <68f1d9d6.050a0220.91a22.0419.GAE@google.com>

#syz test: 
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master


 From 123c5ac9ba261681b58a6217409c94722fde4249 Mon Sep 17 00:00:00 2001
From: Shaurya Rane <ssrane_b23@ee.vjti.ac.in>
Date: Sun, 19 Oct 2025 23:18:30 +0530
Subject: [PATCH] net: key: Validate address family in set_ipsecrequest()

syzbot reported a kernel BUG in set_ipsecrequest() due to an
skb_over_panic when processing XFRM_MSG_MIGRATE messages.

The root cause is that set_ipsecrequest() does not validate the
address family parameter before using it to calculate buffer sizes.
When an unsupported family value (such as 0) is passed,
pfkey_sockaddr_len() returns 0, leading to incorrect size calculations.

In pfkey_send_migrate(), the buffer size is calculated based on
pfkey_sockaddr_pair_size(), which uses pfkey_sockaddr_len(). When
family=0, this returns 0, so only sizeof(struct sadb_x_ipsecrequest)
(16 bytes) is allocated per entry. However, set_ipsecrequest() is
called multiple times in a loop (once for old_family, once for
new_family, for each migration bundle), repeatedly calling skb_put_zero()
with 16 bytes each time.

This causes the tail pointer to exceed the end pointer of the skb,
triggering skb_over_panic:
   tail: 0x188 (392 bytes)
   end:  0x180 (384 bytes)

Fix this by validating that pfkey_sockaddr_len() returns a non-zero
value before proceeding with buffer operations. This ensures proper
size calculations and prevents buffer overflow. Checking socklen
instead of just family==0 provides comprehensive validation for all
unsupported address families.

Reported-by: syzbot+be97dd4da14ae88b6ba4@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=be97dd4da14ae88b6ba4
Fixes: 08de61beab8a ("[PFKEYV2]: Extension for dynamic update of 
endpoint address(es)")

Signed-off-by: Shaurya Rane <ssrane_b23@ee.vjti.ac.in>
---
  net/key/af_key.c | 4 ++++
  1 file changed, 4 insertions(+)

diff --git a/net/key/af_key.c b/net/key/af_key.c
index 2ebde0352245..713344c594d4 100644
--- a/net/key/af_key.c
+++ b/net/key/af_key.c
@@ -3526,6 +3526,10 @@ static int set_ipsecrequest(struct sk_buff *skb,
      int socklen = pfkey_sockaddr_len(family);
      int size_req;

+    /* Reject invalid/unsupported address families */
+    if (!socklen)
+        return -EINVAL;
+
      size_req = sizeof(struct sadb_x_ipsecrequest) +
             pfkey_sockaddr_pair_size(family);

-- 
2.34.1



  parent reply	other threads:[~2025-10-19 18:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  5:53 syzbot
2025-10-17 10:53 ` syzbot
2025-10-19  2:34 ` [PATCH] key: No support for family zero Edward Adam Davis
2025-10-27 21:00   ` Simon Horman
2025-10-19 18:29 ` shaurya [this message]
2025-10-19 18:32   ` [syzbot] [net?] kernel BUG in set_ipsecrequest syzbot
2025-10-20  2:57 ` Forwarded: [Testing] net: key: Validate address family in set_ipsecrequest() syzbot
2025-10-20  7:30 ` Forwarded: [PATCH] Fix integer overflow " syzbot
2025-10-20  7:54 ` Forwarded: Re: [syzbot] [net?] kernel BUG in set_ipsecrequest syzbot
2025-10-20 11:19 ` Forwarded: syzbot
2025-10-21  3:00 ` [PATCH] fix integer overflow in set_ipsecrequest clingfei
2025-10-23 12:24 ` [PATCH net] net: key: Fix potential " clingfei
2025-10-27 20:37   ` Simon Horman
2026-06-24 13:29 ` Forwarded: syzbot
     [not found] <81eb1a55-dd34-43d1-93d1-33d0f24c7622@ee.vjti.ac.in>
2025-10-19 18:31 ` [syzbot] [net?] kernel BUG in set_ipsecrequest syzbot
     [not found] <ac912e45-9267-4c0c-b700-dd1b602ef2c0@gmail.com>
2025-10-19 18:32 ` syzbot
2025-10-20  2:49 [PATCH] net: key: Validate address family in set_ipsecrequest() SHAURYA RANE
2025-10-20  2:52 ` [syzbot] [net?] kernel BUG in set_ipsecrequest syzbot
     [not found] <20251020025728.15250-1-ssranevjti@gmail.com>
2025-10-20  3:16 ` syzbot
2025-10-20  6:00 1599101385
2025-10-20  6:01 ` syzbot
2025-10-20  6:03 1599101385
2025-10-20  7:30 [PATCH] Fix integer overflow in set_ipsecrequest() clingfei
2025-10-20  7:36 ` [syzbot] [net?] kernel BUG in set_ipsecrequest syzbot
2025-10-20  7:46   ` clingfei
2025-10-20  7:48     ` syzbot
     [not found] <CADPKJ-7HnHKJ6RxzUcLh8NSXRq+99aim5tTvhz8j1s-TMx9saA@mail.gmail.com>
2025-10-20  7:56 ` syzbot
     [not found] <20251020111926.938354-1-1599101385@qq.com>
2025-10-20 13:48 ` syzbot
2025-11-06 13:56 [PATCH 3/3] net: key: Validate address family in set_ipsecrequest() clingfei
2025-11-06 14:22 ` [syzbot] [net?] kernel BUG in set_ipsecrequest syzbot

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=1b4aeb68-bf9a-40a1-ab86-a52ef91eb3a4@gmail.com \
    --to=ssranevjti@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=steffen.klassert@secunet.com \
    --cc=syzbot+be97dd4da14ae88b6ba4@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome