netdev - Fw: [Bug 207403] New: Object freed twice in cleanup_net in net/core/net

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>] [day] [month] [year] [list]

Date:   Wed, 22 Apr 2020 08:42:00 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     netdev@...r.kernel.org
Subject: Fw: [Bug 207403] New: Object freed twice in cleanup_net in
 net/core/net_namespace.c

Begin forwarded message:

Date: Wed, 22 Apr 2020 12:47:34 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: stephen@...workplumber.org
Subject: [Bug 207403] New: Object freed twice in cleanup_net in net/core/net_namespace.c

https://bugzilla.kernel.org/show_bug.cgi?id=207403

            Bug ID: 207403
           Summary: Object freed twice in cleanup_net in
                    net/core/net_namespace.c
           Product: Networking
           Version: 2.5
    Kernel Version: At least between 4.14 and 5.4
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Other
          Assignee: stephen@...workplumber.org
          Reporter: jmarcet@...il.com
        Regression: No

Created attachment 288659
  --> https://bugzilla.kernel.org/attachment.cgi?id=288659&action=edit  
dmesg from qemu instance running openwrt

There is an issue regarding network namespaces on OpenWRT.

There is some locking wrong in kernel's netns subsystem. Starting docker with a
bunch of containers is a game of luck, they can start cleanly, but there are
good chances the bug is hit, often crashing the entire system. I attach a dmesg
grabbed from a qemu instance which shows it clearly.

I have built OpenWRT with a vanilla kernel, and the issue still happens. It
might have to do with the special user space tools not used in any other
environment. It has been happening for at least between 4.14 and 5.4, and the
issue is in the kernel.

I hit it with docker. Using docker-compose, with some image building, after
some time I get the oops in the attached dmesg.

I have verified it happens on x86-64 both bare metal and under qemu, with and
without preemption, with 1 or several CPUs.

Since I have not seen it in any other environment and you might want to play
first hands with it, I am sharing a OpenWRT image ready to use, a little more
packed than the official ones, with docker-compose, kgdb, ftrace,... It is for
x86-64 efi systems and runs fine under qemu.
https://openwrt.marcet.info/latest/targets/x86/64/

If there is any more info I can provide, please ask.

-- 
You are receiving this mail because:
You are the assignee for the bug.