netdev - [BUG] docker socket mounting fails in net-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <5fb8d86f-b633-7552-8ba9-41e42f07c02a@gmail.com>
Date:   Thu, 30 Jun 2022 14:20:44 +0300
From:   Leonard Crestez <cdleonard@...il.com>
To:     Kuniyuki Iwashima <kuniyu@...zon.com>,
        "David S. Miller" <davem@...emloft.net>
Cc:     Sachin Sant <sachinp@...ux.ibm.com>,
        netdev <netdev@...r.kernel.org>
Subject: [BUG] docker socket mounting fails in net-next

Hello,

In recent net-next it is no longer possible to mount the docker socket 
inside a container. Test case is very simple:

docker run -v/var/run/docker.sock:/var/run/docker.sock docker docker ps

Giving containers full access to the docker daemon this way is common 
for CI systems where all code is trusted.

I bisected this problem to commit cf2f225e2653 ("af_unix: Put a socket 
into a per-netns hash table."). Another issue was reported in this area:

https://lore.kernel.org/netdev/20220629174729.6744-1-kuniyu@amazon.com/T/

My test scenario is extremely simple, it should easily reproduce on any 
generic distro running docker.

--
Regards,
Leonard