This bug was fixed in the package linux-ti-omap4 - 2.6.38-1209.26
--------------- linux-ti-omap4 (2.6.38-1209.26) natty-proposed; urgency=low
* Release Tracking Bug - LP: #1047347
[ Upstream Kernel Changes ]
* rds: set correct msg_namelen - LP: #1031112 - CVE-2012-3340 * KVM: unmap pages from the iommu when slots are removed - LP: #987569 - CVE-2012-2121 * net: Allow driver to limit number of GSO segments per skb - LP: #1037456 - CVE-2012-3412 * tcp: do not scale TSO segment size with reordering degree - LP: #1037456 - CVE-2012-3412 * tcp: Apply device TSO segment limit earlier - LP: #1037456 - CVE-2012-3412 * sfc: Replace some literal constants with EFX_PAGE_SIZE/EFX_BUF_SIZE - LP: #1037456 - CVE-2012-3412 * sfc: Fix maximum number of TSO segments and minimum TX queue size - LP: #1037456 - CVE-2012-3412 * mm: Hold a file reference in madvise_remove - LP: #1042447 - CVE-2012-3511 -- Paolo Pisati <email address hidden> Wed, 12 Sep 2012 16:34:28 +0200
This bug was fixed in the package linux-ti-omap4 - 2.6.38-1209.26
---------------
linux-ti-omap4 (2.6.38-1209.26) natty-proposed; urgency=low
* Release Tracking Bug
- LP: #1047347
[ Upstream Kernel Changes ]
* rds: set correct msg_namelen SIZE/EFX_ BUF_SIZE
- LP: #1031112
- CVE-2012-3340
* KVM: unmap pages from the iommu when slots are removed
- LP: #987569
- CVE-2012-2121
* net: Allow driver to limit number of GSO segments per skb
- LP: #1037456
- CVE-2012-3412
* tcp: do not scale TSO segment size with reordering degree
- LP: #1037456
- CVE-2012-3412
* tcp: Apply device TSO segment limit earlier
- LP: #1037456
- CVE-2012-3412
* sfc: Replace some literal constants with EFX_PAGE_
- LP: #1037456
- CVE-2012-3412
* sfc: Fix maximum number of TSO segments and minimum TX queue size
- LP: #1037456
- CVE-2012-3412
* mm: Hold a file reference in madvise_remove
- LP: #1042447
- CVE-2012-3511
-- Paolo Pisati <email address hidden> Wed, 12 Sep 2012 16:34:28 +0200