Netdev List
 help / color / mirror / Atom feed
* [PATCH net] ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options
@ 2026-06-01 12:41 Eric Dumazet
  2026-06-01 15:34 ` Ido Schimmel
  0 siblings, 1 reply; 2+ messages in thread
From: Eric Dumazet @ 2026-06-01 12:41 UTC (permalink / raw)
  To: David S . Miller, Jakub Kicinski, Paolo Abeni
  Cc: Simon Horman, Ido Schimmel, David Ahern, netdev, eric.dumazet,
	Eric Dumazet, Tamir Shahar, Amit Klein

This patch restricts setting Loose Source and Record Route (LSRR)
and Strict Source and Record Route (SSRR) IP options to users
with CAP_NET_RAW capability.

This prevents unprivileged applications from forcing packets to route
through attacker-controlled nodes to leak TCP ISN and possibly other
protocol information.

While LSRR and SSRR are commonly filtered in many network environments,
they may still be supported and forwarded along some network paths.

RFC 7126 (Recommendations on Filtering of IPv4 Packets Containing
IPv4 Options) recommend to drop these options in 4.3 and 4.4.

Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Reported-by: Tamir Shahar <tamirthesis@gmail.com>
Reported-by: Amit Klein <aksecurity@gmail.com>
Signed-off-by: Eric Dumazet <edumazet@google.com>
---
 net/ipv4/ip_options.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/net/ipv4/ip_options.c b/net/ipv4/ip_options.c
index be8815ce3ac242372eeae4a97091cda26d40ceb0..ac0d147c4b8cc347839a044adc43897faffd95c8 100644
--- a/net/ipv4/ip_options.c
+++ b/net/ipv4/ip_options.c
@@ -283,6 +283,10 @@ int __ip_options_compile(struct net *net,
 		switch (*optptr) {
 		case IPOPT_SSRR:
 		case IPOPT_LSRR:
+			if (!skb && !ns_capable(net->user_ns, CAP_NET_RAW)) {
+				pp_ptr = optptr;
+				goto error;
+			}
 			if (optlen < 3) {
 				pp_ptr = optptr + 1;
 				goto error;
-- 
2.54.0.1013.g208068f2d8-goog


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH net] ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options
  2026-06-01 12:41 [PATCH net] ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options Eric Dumazet
@ 2026-06-01 15:34 ` Ido Schimmel
  0 siblings, 0 replies; 2+ messages in thread
From: Ido Schimmel @ 2026-06-01 15:34 UTC (permalink / raw)
  To: Eric Dumazet
  Cc: David S . Miller, Jakub Kicinski, Paolo Abeni, Simon Horman,
	David Ahern, netdev, eric.dumazet, Tamir Shahar, Amit Klein

On Mon, Jun 01, 2026 at 12:41:57PM +0000, Eric Dumazet wrote:
> This patch restricts setting Loose Source and Record Route (LSRR)
> and Strict Source and Record Route (SSRR) IP options to users
> with CAP_NET_RAW capability.
> 
> This prevents unprivileged applications from forcing packets to route
> through attacker-controlled nodes to leak TCP ISN and possibly other
> protocol information.
> 
> While LSRR and SSRR are commonly filtered in many network environments,
> they may still be supported and forwarded along some network paths.
> 
> RFC 7126 (Recommendations on Filtering of IPv4 Packets Containing
> IPv4 Options) recommend to drop these options in 4.3 and 4.4.
> 
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Reported-by: Tamir Shahar <tamirthesis@gmail.com>
> Reported-by: Amit Klein <aksecurity@gmail.com>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> ---
>  net/ipv4/ip_options.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/net/ipv4/ip_options.c b/net/ipv4/ip_options.c
> index be8815ce3ac242372eeae4a97091cda26d40ceb0..ac0d147c4b8cc347839a044adc43897faffd95c8 100644
> --- a/net/ipv4/ip_options.c
> +++ b/net/ipv4/ip_options.c
> @@ -283,6 +283,10 @@ int __ip_options_compile(struct net *net,
>  		switch (*optptr) {
>  		case IPOPT_SSRR:
>  		case IPOPT_LSRR:
> +			if (!skb && !ns_capable(net->user_ns, CAP_NET_RAW)) {
> +				pp_ptr = optptr;
> +				goto error;
> +			}

This might be a problem for netfilter which calls __ip_options_compile()
without an skb from ipv4_find_option().

AFAICT, user space can include IP options either using the IP_OPTIONS
socket options or using the IP_RETOPTS cmsg, but the latter is not
applicable to TCP.

If we put the check in do_ip_setsockopt(), we create a weird situation
for non-TCP sockets: They can't set these IP options using IP_OPTIONS,
but can set them via the IP_RETOPTS cmsg.

So maybe we should just put the check in ip_options_get() which is
called from both paths? Something like:

diff --git a/net/ipv4/ip_options.c b/net/ipv4/ip_options.c
index be8815ce3ac2..09d745112c15 100644
--- a/net/ipv4/ip_options.c
+++ b/net/ipv4/ip_options.c
@@ -530,6 +530,10 @@ int ip_options_get(struct net *net, struct ip_options_rcu **optp,
                kfree(opt);
                return -EINVAL;
        }
+       if (opt->opt.srr && !ns_capable(net->user_ns, CAP_NET_RAW)) {
+               kfree(opt);
+               return -EPERM;
+       }
        kfree(*optp);
        *optp = opt;
        return 0;

^ permalink raw reply related	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-06-01 15:34 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-06-01 12:41 [PATCH net] ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options Eric Dumazet
2026-06-01 15:34 ` Ido Schimmel

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox