Description: aio: prevent double free in ioctx_alloc
References:
Notes:
 bwh> So far as I can see, this was introduced by commit e34ecee2ae79
 bwh> "aio: Fix a trinity splat" and fixed by commit d558023207e0, both
 bwh> of which went into 3.13-rc3 and 3.12.4.  So no releases appear to
 bwh> be affected and this CVE is entirely bogus.
 bwh> There was another regression caused by "aio: Fix a trinity splat",
 bwh> fixed by commit 200067a3f3e7 "aio: fix kioctx leak ..."
Bugs:
upstream: N/A "vulnerable code not present"
2.6.32-upstream-stable: N/A "vulnerable code not present"
sid: N/A "vulnerable code not present"
3.2-wheezy-security: N/A "vulnerable code not present"
2.6.32-squeeze-security: N/A "vulnerable code not present"
3.2-upstream-stable: N/A "vulnerable code not present"