moby: Segfaulting (I think?) on Linux 4.7

Output of docker version:

Client:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 22:00:43 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 22:00:43 2016
 OS/Arch:      linux/amd64

Output of docker info:

Containers: 7
 Running: 0
 Paused: 0
 Stopped: 7
Images: 152
Server Version: 1.11.2
Storage Driver: overlay
 Backing Filesystem: extfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins: 
 Volume: local
 Network: bridge null host
Kernel Version: 4.7.0-040700rc2-generic
Operating System: Ubuntu 16.04 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.37 GiB
Name: zfp
ID: WWAV:EBRG:XQKU:LLZ7:JUMU:MDR4:BPJ4:C7T3:XKVQ:WFUT:3DAP:6ZHU
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

Additional environment details (AWS, VirtualBox, physical, etc.):

physical, kernel says Linux zfp 4.7.0-040700rc2-generic #201606051831 SMP Sun Jun 5 22:33:44 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce the issue:

1. Install Linux 4.7 * wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc2-yakkety/linux-headers-4.7.0-040700rc2-generic_4.7.0-040700rc2.201606051831_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc2-yakkety/linux-headers-4.7.0-040700rc2_4.7.0-040700rc2.201606051831_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc2-yakkety/linux-image-4.7.0-040700rc2-generic_4.7.0-040700rc2.201606051831_amd64.deb * sudo dpkg -i linux-headers-4.7.0-040700rc2_4.7.0-040700rc2.201606051831_all.deb linux-headers-4.7.0-040700rc2-generic_4.7.0-040700rc2.201606051831_amd64.deb linux-image-4.7.0-040700rc2-generic_4.7.0-040700rc2.201606051831_amd64.deb
2. reboot into new kernel
3. docker run --rm --name w.pl -v ~/tmp:/tmp -u "$(id -u)" frew/w.pl
4. Cry

Describe the results you received:

The client exited 139 (no core file that I can find anywhere)

Describe the results you expected:

I expected the container to run and write files to ~/tmp

Additional information you deem important (e.g. issue happens only occasionally):

This happens with every single container. I just used the simplest one I know of to show the issue.