linux-kernel - Re: [ofa-general] Re: [PATCH 00 of 33] Set of ipath patches for 2.6.22

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 10 Apr 2007 17:48:35 -0700
From:	Robert Walsh <rjwalsh@...hscale.com>
To:	Roland Dreier <rdreier@...co.com>
Cc:	Bryan O'Sullivan <bos@...hscale.com>,
	openib-general@...nfabrics.org, linux-kernel@...r.kernel.org
Subject: Re: [ofa-general] Re: [PATCH 00 of 33] Set of ipath patches for 2.6.22

Roland Dreier wrote:
>  > Is there any chance of getting a fix for the use-after-free that can
>  > be caused by allocating something from userspace, failing to mmap the
>  > buffer and then exiting?  To see what happens, look at how
>  > ipath_create_cq sticks a struct ipath_mmap_info into the pending mmap
>  > "list" (and yes it would be much cleaner to just use struct list_head
>  > here rather than reimplementing a linked list yourself), and then look
>  > at how ipath_destroy_cq() frees the same structure without checking if
>  > it has been removed from the pending mmap list.
> 
> By the way, would it help get this fixed if I opened a bug on openfabrics.org?
> Or is that a waste of time?

We're tracking it here (bug 12010 on our internal bugzilla), and it's on 
my list to get done "soon".  I'm currently in the middle of some other 
bug fixes, but when I get to a good stopping point, I'll get this fixed. 
  Shouldn't be too difficult.

If you'd like to track it yourself, feel free to open an OpenFabrics 
bug.  I'll update the bug when I get a patch done.

Regards,
  Robert.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/