Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 11 Mar 2014 09:50:45 -0700
From: Chris Palmer <>
Subject: Re: CVE-2014-0131 -- kernel: net: use-after-free
 during segmentation with zerocopy

It would be nice to clarify this bug description. It's a kernel memory
disclosure bug (not a memory leak in the sense of failing to collect
garbage). Although UAF is often worse than that, it's not in this case,
because there's 0 chance the after-free-user of the fragment will think the
fragment is bigger than it is and subsequently write too much data into it.

Is that right?
On Mar 10, 2014 9:41 AM, "Petr Matousek" <> wrote:

> A flaw was found in the way segmentation was performed on skbs
> originated from vhost-net when zerocopy feature was enabled.
> This flaw could be potentially used to leak kernel memory.
> Upstream patch submission:
> --
> Petr Matousek / Red Hat Security Response Team
> PGP: 0xC44977CA 8107 AF16 A416 F9AF 18F3  D874 3E78 6F42 C449 77CA

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.