RE: [SECURITY] [DSA 2926-1] linux security update

2014-05-12 Thread Daniel Genis
Die CVE-2014-0196 is wel interessant

Local kernel DoS || privilege escalation

 Original message 
From: Moritz Muehlenhoff j...@debian.org 
Date: 12/05/2014  17:59  (GMT+01:00) 
To: debian-security-annou...@lists.debian.org 
Subject: [SECURITY] [DSA 2926-1] linux security update 
 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -
Debian Security Advisory DSA-2926-1   secur...@debian.org
http://www.debian.org/security/    Moritz Muehlenhoff
May 12, 2014   http://www.debian.org/security/faq
- -

Package    : linux
CVE ID : CVE-2014-0196 CVE-2014-1737 CVE-2014-1738 CVE-2014-2851 
 CVE-2014-3122

Several vulnerabilities have been discovered in the Linux kernel that 
may lead to a denial of service, information leaks or privilege 
escalation:

CVE-2014-0196

    Jiri Slaby discovered a race condition in the pty layer, which could
    lead to denial of service or privilege escalation.

CVE-2014-1737 / CVE-2014-1738

    Matthew Daley discovered that missing input sanitising in the
    FDRAWCMD ioctl and an information leak could result in privilege
    escalation.

CVE-2014-2851

    Incorrect reference counting in the ping_init_sock() function allows
    denial of service or privilege escalation.

CVE-2014-3122

    Incorrect locking of memory can result in local denial of service.

For the stable distribution (wheezy), these problems have been fixed in
version 3.2.57-3+deb7u1. This update also fixes a regression in the isci
driver and suspend problems with certain AMD CPUs (introduced in the
updated kernel from the Wheezy 7.5 point release).

For the unstable distribution (sid), these problems will be fixed soon.

We recommend that you upgrade your linux packages.

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: http://www.debian.org/security/

Mailing list: debian-security-annou...@lists.debian.org





-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJTcO+9AAoJEBDCk7bDfE421QQP/j08SKXHiHXcdZmtcP1ifE9P
fBvddKDd9thLxec1bn4VhFDsDMMESvMGV4S62FaAuet7OU8GpX899ctGeZiR4YM6
EKpd86hwWiChs+PPhyEpae9/gX0ZDGJLToE5PyggOa/anpZ39yHT6rDccl/H9rIc
OgFE7ru8je/I1jdeOlqdJLZ2YicM/xLy1gF6WwZFvfKUXHbeJ9cnz5VZR/R1aJCb
Ys/rj2QjKDaXvDuW+l+ybQOL6nqevH1upFL4u+kkiOk78q2UoJdyYSeKGLrtIYBW
3SRnY8xHNAtHrldzDjXdFaTqd880/ter5l9OXo9zcR8wUojAqWbSDW+0TC/5CmRL
oWa72DuCoxdulsmZQZydxB0U87pudsI2Ez5wiXVXfPWD7Ykwad+j/AV3EBaUEKwi
hnWt+9IFWgIjnVnDbPbwfUkmzRCa58ewo10alxEq/supTrkAU/5xQbEtejt4MYtq
TGy8b51aWg5VYpEze5HrPBPyl2szdOF+j9OhNF08Rh/RMGbzSi3Qamr/xsG1PhBx
+93FcjfembChbPihpUQp7by/2xtT3Td1TA1Q7o3vgKk/bdcmsI1JMdPs46H+AFpi
xRgd1dxxPpCaTTCgVHkp6uykWhQcW+nI87OEv/Ibxdch+qrlPs4BxxTk9uL0OHGa
mlcOLozLVQLTcPYUAGL6
=AqGQ
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-security-announce-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140512155945.GA2521@pisco.westfalen.local



[Debian 6 Squeeze] ANNOUNCEMENT: Intel processor microcode security update

2014-05-12 Thread Henrique de Moraes Holschuh
THIS ANNOUNCEMENT IS ONLY MEANINGFUL FOR PEOPLE USING DEBIAN 6 (SQUEEZE)
ON COMPUTERS WITH INTEL PROCESSORS.  IT DOES NOT APPLY TO THE MORE RECENT
DEBIAN RELEASES.


A new Intel microcode update is available for Debian 6 (codename Squeeze).

This microcode update is considered a security update.  Users of the newer
versions of Debian (stable/Wheezy, testing/Jessie, unstable) have already
received it.

For technical reasons, Debian 6 (Squeeze) will receive intel-microcode
updates only through squeeze-backports, and only after the same update has
been accepted into Debian stable, and pushed out into a Debian stable point
release.

INSTRUCTIONS ON HOW TO INSTALL THE UPDATE ARE AVAILABLE AT THE LAST PART OF
THIS MESSAGE.

This microcode update release contains fixes for a number of severe issues
on a large number of Intel system processor models produced in the last
five years.  Some of the issues fixed by this update address severe
security risks.

Details about some of the issues fixed by this microcode update, about
microcode updates in general, and about microcode update packages can be
found on previous emails on this thread, at:

https://lists.debian.org/debian-user/2013/09/msg00126.html
https://lists.debian.org/debian-user/2013/09/msg01300.html

Do not expect further announcements about intel-microcode updates, this is
an exception due to the known security nature of this update, and due to
the nonstandard process required to install it for the first time.


Installing the squeeze-backports microcode update:

Manual action by the system administrator is required to enable
squeeze-backports in apt's source.list, and install the backported
intel-microcode and iucode-tool packages for the first time.

After the manual installation of the first update, apt will remember that
it has to get further updates from squeeze-backports.

Please refer to http://backports.debian.org/Instructions/ for general
details on how to use squeeze-backports, and below for step-by-step
simplified instructions.


First install procedure:


1. Enable squeeze-backports in /etc/apt/sources.list, adding:

   deb http://YOURMIRROR.debian.org/debian-backports squeeze-backports main 
contrib non-free

   notice that you need to enable both contrib (for the iucode-tool
   package) and non-free (for the intel-microcode package).

   This is safe.  In Debian's default configuration, squeeze-backports
   packages are only installed by direct request (-t option of apt-get,
   or by explicitly selecting the version from backports in aptitude).

   It will NOT cause your whole system to be updated to squeeze-backports.

2. apt-get update

3. apt-get --purge remove intel-microcode microcode.ctl

4. apt-get -t squeeze-backports install intel-microcode iucode-tool

   (notice that we had to explictly request that packages from
   squeeze-backports were to be used in step 4).


Update procedure:
-

Once installed, packages from squeeze-backports will be handled
automatically when you update the system.  The system remembers which
packages came from squeeze-backports, and looks there for updates.

1. apt-get update
2. apt-get upgrade (or safe-upgrade, or dist-upgrade)

A new microcode update is already available in Debian unstable, and should
make it to squeeze-backports in about four to six months.

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
To UNSUBSCRIBE, email to debian-security-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140512201833.ga21...@khazad-dum.debian.net