[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+rthh9K+P2JHSqoNi6WJHKR8S7q9CDztip5F6aSUcLd-uRV_w@mail.gmail.com>
Date: Mon, 22 Apr 2013 14:29:48 +0200
From: Mathias Krause <minipli@...glemail.com>
To: oss-security@...ts.openwall.com
Cc: cve-assign@...re.org, Petr Matousek <pmatouse@...hat.com>
Subject: Re: Re: Linux kernel: more net info leak fixes for v3.9
On Mon, Apr 22, 2013 at 2:13 PM, P J P <ppandit@...hat.com> wrote:
> Hello,
> +-- On Mon, 22 Apr 2013, cve-assign@...re.org wrote --+
> | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 CVE-2013-3222
>
> Is the following call sequence correct..?
>
> recvmsg
> -> __sys_recvmsg
> -> sock_recvmsg_nosec/sock_recvmsg
> -> __sock_recvmsg_nosec
> -> sock->ops->recvmsg
> -> vcc_recvmsg
looks reasonable
> If yes, *msg seems to hold the user space msghdr values. (Just to confirm)
partly... Have a look at verify_iovec()/verify_compat_iovec(). They're
updating the msg_name and msg_iov pointers.
Mathias
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.
