All of lore.kernel.org
 help / color / mirror / Atom feed
* [Qemu-devel] [Bug 1837094] [NEW] UndefinedBehaviorSanitizer crash around slirp::ip_reass()
@ 2019-07-18 17:47 Philippe Mathieu-Daudé
  2019-07-18 17:58 ` [Qemu-devel] [Bug 1837094] " Philippe Mathieu-Daudé
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: Philippe Mathieu-Daudé @ 2019-07-18 17:47 UTC (permalink / raw)
  To: qemu-devel

Public bug reported:

tag: v4.1.0-rc1

./configure --enable-sanitizers --extra-cflags=-O1

==26130==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000008 (pc 0x00000046d588 bp 0x7fff6ee9f940 sp 0x7fff6ee9f8e8 T26130)
==26130==The signal is caused by a WRITE memory access.
==26130==Hint: address points to the zero page.
    #0 0x0000561ad346d587 in ip_deq() at slirp/src/ip_input.c:411:55
    #1 0x0000561ad346cffb in ip_reass() at slirp/src/ip_input.c:304:9
    #2 0x0000561ad346cb6f in ip_input() at slirp/src/ip_input.c:184:18

I only had access to the last packet which isn't the culprit, I'm now
seeing how to log the network traffic of the guest to provide more
useful information.

** Affects: qemu
     Importance: Undecided
         Status: New


** Tags: slirp

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1837094

Title:
  UndefinedBehaviorSanitizer crash around slirp::ip_reass()

Status in QEMU:
  New

Bug description:
  tag: v4.1.0-rc1

  ./configure --enable-sanitizers --extra-cflags=-O1

  ==26130==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000008 (pc 0x00000046d588 bp 0x7fff6ee9f940 sp 0x7fff6ee9f8e8 T26130)
  ==26130==The signal is caused by a WRITE memory access.
  ==26130==Hint: address points to the zero page.
      #0 0x0000561ad346d587 in ip_deq() at slirp/src/ip_input.c:411:55
      #1 0x0000561ad346cffb in ip_reass() at slirp/src/ip_input.c:304:9
      #2 0x0000561ad346cb6f in ip_input() at slirp/src/ip_input.c:184:18

  I only had access to the last packet which isn't the culprit, I'm now
  seeing how to log the network traffic of the guest to provide more
  useful information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1837094/+subscriptions


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

* [Qemu-devel] [Bug 1837094] Re: UndefinedBehaviorSanitizer crash around slirp::ip_reass()
  2019-07-18 17:47 [Qemu-devel] [Bug 1837094] [NEW] UndefinedBehaviorSanitizer crash around slirp::ip_reass() Philippe Mathieu-Daudé
@ 2019-07-18 17:58 ` Philippe Mathieu-Daudé
  2019-08-29 15:16 ` Philippe Mathieu-Daudé
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: Philippe Mathieu-Daudé @ 2019-07-18 17:58 UTC (permalink / raw)
  To: qemu-devel

** Description changed:

  tag: v4.1.0-rc1
  
  ./configure --enable-sanitizers --extra-cflags=-O1
  
- ==26130==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000008 (pc 0x00000046d588 bp 0x7fff6ee9f940 sp 0x7fff6ee9f8e8 T26130)
+ ==26130==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000008 (pc 0x0000561ad346d588 bp 0x7fff6ee9f940 sp 0x7fff6ee9f8e8 T26130)
  ==26130==The signal is caused by a WRITE memory access.
  ==26130==Hint: address points to the zero page.
-     #0 0x0000561ad346d587 in ip_deq() at slirp/src/ip_input.c:411:55
-     #1 0x0000561ad346cffb in ip_reass() at slirp/src/ip_input.c:304:9
-     #2 0x0000561ad346cb6f in ip_input() at slirp/src/ip_input.c:184:18
+     #0 0x0000561ad346d587 in ip_deq() at slirp/src/ip_input.c:411:55
+     #1 0x0000561ad346cffb in ip_reass() at slirp/src/ip_input.c:304:9
+     #2 0x0000561ad346cb6f in ip_input() at slirp/src/ip_input.c:184:18
  
  I only had access to the last packet which isn't the culprit, I'm now
  seeing how to log the network traffic of the guest to provide more
  useful information.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1837094

Title:
  UndefinedBehaviorSanitizer crash around slirp::ip_reass()

Status in QEMU:
  New

Bug description:
  tag: v4.1.0-rc1

  ./configure --enable-sanitizers --extra-cflags=-O1

  ==26130==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000008 (pc 0x0000561ad346d588 bp 0x7fff6ee9f940 sp 0x7fff6ee9f8e8 T26130)
  ==26130==The signal is caused by a WRITE memory access.
  ==26130==Hint: address points to the zero page.
      #0 0x0000561ad346d587 in ip_deq() at slirp/src/ip_input.c:411:55
      #1 0x0000561ad346cffb in ip_reass() at slirp/src/ip_input.c:304:9
      #2 0x0000561ad346cb6f in ip_input() at slirp/src/ip_input.c:184:18

  I only had access to the last packet which isn't the culprit, I'm now
  seeing how to log the network traffic of the guest to provide more
  useful information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1837094/+subscriptions


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

* [Qemu-devel] [Bug 1837094] Re: UndefinedBehaviorSanitizer crash around slirp::ip_reass()
  2019-07-18 17:47 [Qemu-devel] [Bug 1837094] [NEW] UndefinedBehaviorSanitizer crash around slirp::ip_reass() Philippe Mathieu-Daudé
  2019-07-18 17:58 ` [Qemu-devel] [Bug 1837094] " Philippe Mathieu-Daudé
@ 2019-08-29 15:16 ` Philippe Mathieu-Daudé
  2019-08-29 15:39 ` Samuel thibault
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: Philippe Mathieu-Daudé @ 2019-08-29 15:16 UTC (permalink / raw)
  To: qemu-devel

Recent libslirp patch 126c04ac (explained in e0be8043) changed
ip_reass(), so this bug might be fixed.

https://gitlab.freedesktop.org/slirp/libslirp/commit/126c04ac
https://gitlab.freedesktop.org/slirp/libslirp/commit/e0be8043

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1837094

Title:
  UndefinedBehaviorSanitizer crash around slirp::ip_reass()

Status in QEMU:
  New

Bug description:
  tag: v4.1.0-rc1

  ./configure --enable-sanitizers --extra-cflags=-O1

  ==26130==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000008 (pc 0x0000561ad346d588 bp 0x7fff6ee9f940 sp 0x7fff6ee9f8e8 T26130)
  ==26130==The signal is caused by a WRITE memory access.
  ==26130==Hint: address points to the zero page.
      #0 0x0000561ad346d587 in ip_deq() at slirp/src/ip_input.c:411:55
      #1 0x0000561ad346cffb in ip_reass() at slirp/src/ip_input.c:304:9
      #2 0x0000561ad346cb6f in ip_input() at slirp/src/ip_input.c:184:18

  I only had access to the last packet which isn't the culprit, I'm now
  seeing how to log the network traffic of the guest to provide more
  useful information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1837094/+subscriptions


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

* [Qemu-devel] [Bug 1837094] Re: UndefinedBehaviorSanitizer crash around slirp::ip_reass()
  2019-07-18 17:47 [Qemu-devel] [Bug 1837094] [NEW] UndefinedBehaviorSanitizer crash around slirp::ip_reass() Philippe Mathieu-Daudé
  2019-07-18 17:58 ` [Qemu-devel] [Bug 1837094] " Philippe Mathieu-Daudé
  2019-08-29 15:16 ` Philippe Mathieu-Daudé
@ 2019-08-29 15:39 ` Samuel thibault
  2020-05-18  8:13 ` Philippe Mathieu-Daudé
  2020-05-18  8:14 ` Philippe Mathieu-Daudé
  4 siblings, 0 replies; 6+ messages in thread
From: Samuel thibault @ 2019-08-29 15:39 UTC (permalink / raw)
  To: qemu-devel

And

https://gitlab.freedesktop.org/slirp/libslirp/commit/d203c81b

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1837094

Title:
  UndefinedBehaviorSanitizer crash around slirp::ip_reass()

Status in QEMU:
  New

Bug description:
  tag: v4.1.0-rc1

  ./configure --enable-sanitizers --extra-cflags=-O1

  ==26130==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000008 (pc 0x0000561ad346d588 bp 0x7fff6ee9f940 sp 0x7fff6ee9f8e8 T26130)
  ==26130==The signal is caused by a WRITE memory access.
  ==26130==Hint: address points to the zero page.
      #0 0x0000561ad346d587 in ip_deq() at slirp/src/ip_input.c:411:55
      #1 0x0000561ad346cffb in ip_reass() at slirp/src/ip_input.c:304:9
      #2 0x0000561ad346cb6f in ip_input() at slirp/src/ip_input.c:184:18

  I only had access to the last packet which isn't the culprit, I'm now
  seeing how to log the network traffic of the guest to provide more
  useful information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1837094/+subscriptions


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

* [Bug 1837094] Re: UndefinedBehaviorSanitizer crash around slirp::ip_reass()
  2019-07-18 17:47 [Qemu-devel] [Bug 1837094] [NEW] UndefinedBehaviorSanitizer crash around slirp::ip_reass() Philippe Mathieu-Daudé
                   ` (2 preceding siblings ...)
  2019-08-29 15:39 ` Samuel thibault
@ 2020-05-18  8:13 ` Philippe Mathieu-Daudé
  2020-05-18  8:14 ` Philippe Mathieu-Daudé
  4 siblings, 0 replies; 6+ messages in thread
From: Philippe Mathieu-Daudé @ 2020-05-18  8:13 UTC (permalink / raw)
  To: qemu-devel

I apologize for not understanding this bug was a security issue, and not
insisting on it.

It has been fixed in SLiRP by "Fix use-afte-free in ip_reass() (CVE-2020-1983)":
https://gitlab.freedesktop.org/slirp/libslirp/commit/9bd6c591

And in QEMU by commit 7769c23774 "slirp: update to fix CVE-2020-1983".

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-1983

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1837094

Title:
  UndefinedBehaviorSanitizer crash around slirp::ip_reass()

Status in QEMU:
  Fix Released

Bug description:
  tag: v4.1.0-rc1

  ./configure --enable-sanitizers --extra-cflags=-O1

  ==26130==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000008 (pc 0x0000561ad346d588 bp 0x7fff6ee9f940 sp 0x7fff6ee9f8e8 T26130)
  ==26130==The signal is caused by a WRITE memory access.
  ==26130==Hint: address points to the zero page.
      #0 0x0000561ad346d587 in ip_deq() at slirp/src/ip_input.c:411:55
      #1 0x0000561ad346cffb in ip_reass() at slirp/src/ip_input.c:304:9
      #2 0x0000561ad346cb6f in ip_input() at slirp/src/ip_input.c:184:18

  I only had access to the last packet which isn't the culprit, I'm now
  seeing how to log the network traffic of the guest to provide more
  useful information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1837094/+subscriptions


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

* [Bug 1837094] Re: UndefinedBehaviorSanitizer crash around slirp::ip_reass()
  2019-07-18 17:47 [Qemu-devel] [Bug 1837094] [NEW] UndefinedBehaviorSanitizer crash around slirp::ip_reass() Philippe Mathieu-Daudé
                   ` (3 preceding siblings ...)
  2020-05-18  8:13 ` Philippe Mathieu-Daudé
@ 2020-05-18  8:14 ` Philippe Mathieu-Daudé
  4 siblings, 0 replies; 6+ messages in thread
From: Philippe Mathieu-Daudé @ 2020-05-18  8:14 UTC (permalink / raw)
  To: qemu-devel

Fixed in QEMU release v5.0.0

** Changed in: qemu
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1837094

Title:
  UndefinedBehaviorSanitizer crash around slirp::ip_reass()

Status in QEMU:
  Fix Released

Bug description:
  tag: v4.1.0-rc1

  ./configure --enable-sanitizers --extra-cflags=-O1

  ==26130==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000008 (pc 0x0000561ad346d588 bp 0x7fff6ee9f940 sp 0x7fff6ee9f8e8 T26130)
  ==26130==The signal is caused by a WRITE memory access.
  ==26130==Hint: address points to the zero page.
      #0 0x0000561ad346d587 in ip_deq() at slirp/src/ip_input.c:411:55
      #1 0x0000561ad346cffb in ip_reass() at slirp/src/ip_input.c:304:9
      #2 0x0000561ad346cb6f in ip_input() at slirp/src/ip_input.c:184:18

  I only had access to the last packet which isn't the culprit, I'm now
  seeing how to log the network traffic of the guest to provide more
  useful information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1837094/+subscriptions


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

end of thread, other threads:[~2020-05-18  8:22 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-18 17:47 [Qemu-devel] [Bug 1837094] [NEW] UndefinedBehaviorSanitizer crash around slirp::ip_reass() Philippe Mathieu-Daudé
2019-07-18 17:58 ` [Qemu-devel] [Bug 1837094] " Philippe Mathieu-Daudé
2019-08-29 15:16 ` Philippe Mathieu-Daudé
2019-08-29 15:39 ` Samuel thibault
2020-05-18  8:13 ` Philippe Mathieu-Daudé
2020-05-18  8:14 ` Philippe Mathieu-Daudé

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.