From: David Miller <davem@davemloft.net>
To: jkosina@suse.cz
Cc: akpm@linux-foundation.org, acme@mandriva.com, jagger@swiecki.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] DCCP: proper optlen checking in do_dccp_getsockopt()
Date: Wed, 28 Mar 2007 11:59:43 -0700 (PDT) [thread overview]
Message-ID: <20070328.115943.03111877.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0703282045010.19566@jikos.suse.cz>
From: Jiri Kosina <jkosina@suse.cz>
Date: Wed, 28 Mar 2007 20:49:32 +0200 (CEST)
> From: Jiri Kosina <jkosina@suse.cz>
>
> DCCP: proper optlen checking in do_dccp_getsockopt()
>
> Robert Swiecki discovered [1] a signedness bug in checking of
> optlen in do_dccp_getsockopt(). This bug can allow user to
> read parts of the kernel memory.
>
> [1] http://www.securityfocus.com/archive/1/463934/30/0/threaded
Arnaldo already sent me a more proper fix for this.
prev parent reply other threads:[~2007-03-28 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 18:49 Jiri Kosina
2007-03-28 18:59 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070328.115943.03111877.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=acme@mandriva.com \
--cc=akpm@linux-foundation.org \
--cc=jagger@swiecki.net \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®