Software-update: Linux Kernel 2.6.19.2

Het is alweer een tijdje geleden dat de Linux Kernel in onze meuktracker voorbij kwam, maar gelukkig hebben de ontwikkelaars onlangs versie 2.6.19.2 uitgebracht die we bij deze dus kunnen vermelden. Voor de liefhebbers van lange lijsten met veranderingen verwijzen we jullie door naar de lijsten met de veranderingen in 2.6.19, 2.6.19.1 en 2.6.19.2. En de aankondigingen van de laatste drie uitgaves zien er als volgt uit:

Version 2.6.19.2:

We (the -stable team) are announcing the release of the 2.6.19.2 kernel. There's a long list of fixes, not the least of which is the data corruption fix from Linus and some security fixes:

• d4ea7f9f: Bluetooth: Add packet size checks for CAPI messages (CVE-2006-6106)
• eaca4fd8: handle ext3 directory corruption better (CVE-2006-6053)
• fe89cf78: corrupted cramfs filesystems cause kernel oops (CVE-2006-5823)
• 8d312ae1: ext2: skip pages past number of blocks in ext2_find_entry (CVE-2006-6054)
• 54e25b04: VM: Fix nasty and subtle race in shared mmap'ed page writeback
• e26353af: Fix incorrect user space access locking in mincore() (CVE-2006-4814)

thanks,
-chris

Version 2.6.19.1:

We (the -stable team) are announcing the release of the 2.6.19.1 kernel. It's an assortment of fixes with a couple security related:

• a526d58e: do_coredump() and not stopping rewrite attacks? (CVE-2006-6304)
• ad8ca99c: TOKENRING: Remote memory corruptor in ibmtr.c

thanks,
-chris

Version 2.6.19:

There it finally is (or rather - I'm currently uploading the tar-file and patches, and the mirrors are hopefully busily pushing out the git tree that is already updated).

There's not a lot to be said about the changes since -rc6: the shortlog (appended) tells the whole story, and it's really mostly a lot of one-liners or other really small changes. Bugs fixed, but nothing that stands out in my mind.

So go get it. It's one of those rare "perfect" kernels. So if it doesn't happen to compile with your config (or it does compile, but then does unspeakable acts of perversion with your pet dachshund), you can rest easy knowing that it's all your own d*mn fault, and you should just fix your evil ways.

You could send me and the kernel mailing list a note about it anyway, of course. (And perhaps pictures, if your dachshund is involved. Not that we'd be interested, of course. No. Just so that we'd know to avoid it next time).

Linus