From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] agp: potential info leak in compat_agpioc_info_wrap()
Date: Fri, 23 Sep 2011 09:04:15 +0200 [thread overview]
Message-ID: <1316761455.2560.15.camel@edumazet-laptop> (raw)
In-Reply-To: <20110923061945.GC4387@elgon.mountain>
Le vendredi 23 septembre 2011 à 09:19 +0300, Dan Carpenter a écrit :
> Smatch has a new check for Rosenberg type information leaks where
> structs are copied to the user with uninitialized stack data in them.
>
Hmm, automatic tools should not send patches without human check.
> The agp_info32 struct has a 4 byte hole in it so we need to clear
> that before copying it to userspace.
>
> struct agp_info32 {
> struct agp_version version; /* 0 0 */
>
> /* XXX 4 bytes hole, try to pack */
>
This makes no sense :
Why should we have a 32bit hole before an u32 field ?
Which arch mandates this ?
> u32 bridge_id; /* 4 4 */
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/drivers/char/agp/compat_ioctl.c b/drivers/char/agp/compat_ioctl.c
> index a48e05b..0509497 100644
> --- a/drivers/char/agp/compat_ioctl.c
> +++ b/drivers/char/agp/compat_ioctl.c
> @@ -42,6 +42,8 @@ static int compat_agpioc_info_wrap(struct agp_file_private *priv, void __user *a
>
> agp_copy_info(agp_bridge, &kerninfo);
>
> + memset(&userinfo, 0, sizeof(userinfo));
> +
> userinfo.version.major = kerninfo.version.major;
> userinfo.version.minor = kerninfo.version.minor;
> userinfo.bridge_id = kerninfo.device->vendor |
next prev parent reply other threads:[~2011-09-23 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 6:19 Dan Carpenter
2011-09-23 7:04 ` Eric Dumazet [this message]
2011-09-23 7:30 ` Dan Carpenter
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=1316761455.2560.15.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=airlied@linux.ie \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--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®