mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ilia Gavrilov <Ilia.Gavrilov@infotecs.ru>
To: Allison Henderson <achender@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	Ka-Cheong Poon <ka-cheong.poon@oracle.com>,
	Santosh Shilimkar <santosh.shilimkar@oracle.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"rds-devel@oss.oracle.com" <rds-devel@oss.oracle.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>
Subject: Re: [PATCH net] rds: Fix inet6_addr_lst NULL dereference when IPv6 is disabled
Date: Thu, 9 Jul 2026 15:51:45 +0000	[thread overview]
Message-ID: <01d99faa-c8c3-438e-852b-92ba230b8b4a@infotecs.ru> (raw)
In-Reply-To: <a724cf77f2338776f44b465a25009c22a0ee7c43.camel@kernel.org>

On 7/9/26 6:41 PM, Allison Henderson wrote:
> On Wed, 2026-07-08 at 11:59 +0000, Ilia Gavrilov wrote:
>> When booting with the 'ipv6.disable=1' parameter, inet6_addr_lst
>> is never initialized because inet6_init() exits before addrconf_init()
>> is called to initialize it. An attempt to bind an RDS socket to
>> an ipv6 address results in a crash in __ipv6_chk_addr_and_flags()
> 
> Hello Ilia,
> 
> Thanks for the catch.  Some comments below:
> 
>>
>> KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
>> RIP: 0010:__ipv6_chk_addr_and_flags+0x1df/0x7e0
>> Call Trace:
>>  <TASK>
>>  ipv6_chk_addr+0x3b/0x50
>>  rds_tcp_laddr_check+0x155/0x3b0 [rds_tcp]
>>  rds_trans_get_preferred+0x15d/0x2d0 [rds]
>>  ? trace_hardirqs_on+0x2d/0x110
>>  rds_bind+0x1433/0x1d60 [rds]
>>  ? rds_remove_bound+0xd50/0xd50 [rds]
>>  ? aa_af_perm+0x250/0x250
>>  ? __might_fault+0xde/0x190
>>  ? __sys_bind+0x1dc/0x210
>>  __sys_bind+0x1dc/0x210
>>  ? __ia32_sys_socketpair+0x100/0x100
>>  ? restore_fpregs_from_fpstate+0x53/0x100
>>  __x64_sys_bind+0x73/0xb0
>>  ? syscall_enter_from_user_mode+0x1c/0x50
>>  do_syscall_64+0x34/0x80
>>  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
>> RIP: 0033:0x7f47f8269ea9
>>  </TASK>
>>
>> The following code reproduces the issue:
>>
>> struct sockaddr_in6 addr;
>> s = socket(PF_RDS, SOCK_SEQPACKET, 0);
>>
>> memset(&addr, 0, sizeof(addr));
>> inet_pton(AF_INET6, ADDRESS, &addr.sin6_addr);
>> addr.sin6_family = AF_INET6;
>> addr.sin6_port = htons(PORT);
>>
>> bind(s, &addr, sizeof(addr);
> nit: missing paren here
> 
>>
>> Found by InfoTeCS on behalf of Linux Verification Center
>> (linuxtesting.org) with Syzkaller.
>>
>> Fixes: eee2fa6ab322 ("rds: Changing IP address internal representation to struct in6_addr")
>> Fixes: 1e2b44e78eea ("rds: Enable RDS IPv6 support")
>> Signed-off-by: Ilia Gavrilov <Ilia.Gavrilov@infotecs.ru>
>> ---
>>  net/rds/ib.c  | 4 ++++
>>  net/rds/tcp.c | 8 +++++---
>>  2 files changed, 9 insertions(+), 3 deletions(-)
>>
>> diff --git a/net/rds/ib.c b/net/rds/ib.c
>> index 39f87272e071..8f9cf491984f 100644
>> --- a/net/rds/ib.c
>> +++ b/net/rds/ib.c
>> @@ -429,6 +429,10 @@ static int rds_ib_laddr_check_cm(struct net *net, const struct in6_addr *addr,
>>  		sa = (struct sockaddr *)&sin;
>>  	} else {
>>  #if IS_ENABLED(CONFIG_IPV6)
>> +		if (!ipv6_mod_enabled()) {
>> +			ret = -EADDRNOTAVAIL;
>> +			goto out;
>> +		}
>>  		memset(&sin6, 0, sizeof(sin6));
>>  		sin6.sin6_family = AF_INET6;
>>  		sin6.sin6_addr = *addr;
>> diff --git a/net/rds/tcp.c b/net/rds/tcp.c
>> index a1de114d5e2e..955d92277d5a 100644
>> --- a/net/rds/tcp.c
>> +++ b/net/rds/tcp.c
>> @@ -366,9 +366,11 @@ int rds_tcp_laddr_check(struct net *net, const struct in6_addr *addr,
>>  		rcu_read_unlock();
>>  	}
>>  #if IS_ENABLED(CONFIG_IPV6)
>> -	ret = ipv6_chk_addr(net, addr, dev, 0);
>> -	if (ret)
>> -		return 0;
>> +	if (ipv6_mod_enabled()) {
>> +		ret = ipv6_chk_addr(net, addr, dev, 0);
>> +		if (ret)
>> +			return 0;
>> +	}
> 
> There's another ipv6_chk_addr() in __rds_find_ifindex() with the same issue that affects inbound link-local IPv6
> connects.  Can you add a similar guard there too?  Then I think that should cover all the points of exposure.  Thanks
> for working on this.
> 
> Allison
> 

Thanks for the review, I'll add the guard in the next patch version.

>>  #endif
>>  	return -EADDRNOTAVAIL;
>>  }
> 


      reply	other threads:[~2026-07-09 15:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 11:59 Ilia Gavrilov
2026-07-09 15:41 ` Allison Henderson
2026-07-09 15:51   ` Ilia Gavrilov [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=01d99faa-c8c3-438e-852b-92ba230b8b4a@infotecs.ru \
    --to=ilia.gavrilov@infotecs.ru \
    --cc=achender@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=ka-cheong.poon@oracle.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rds-devel@oss.oracle.com \
    --cc=santosh.shilimkar@oracle.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

all inboxes | Powered by JetHome®