Skip to main content

Security Update: kernel, php

It seems that the release of Slackware 14.2 will have to wait again since Pat just bumped the kernel to 4.4.14 to fix 2 security vulnerabilities which he mentioned in detail in the latest batch of updates:
This kernel release fixes two security issues:
  Corrupted offset allows for arbitrary decrements in compat
  IPT_SO_SET_REPLACE setsockopt.  Risk:  High.  Impact:  Kernel memory
  corruption, leading to elevation of privileges or kernel code execution.
  This occurs in a compat_setsockopt() call that is normally restricted to
  root, however, Linux 3/4 kernels that support user and network namespaces
  can allow an unprivileged user to trigger this functionality.  This is
  exploitable from inside a container.
  Out of bounds reads when processing IPT_SO_SET_REPLACE setsockopt.
  Risk:  Medium.  Impact:  Out of bounds heap memory access, leading to a
  Denial of Service (or possibly heap disclosure or further impact).
  This occurs in a setsockopt() call that is normally restricted to root,
  however, Linux 3/4 kernels that support user and network namespaces can
  allow an unprivileged user to trigger this functionality.  This is
  exploitable from inside a container.
  For more information, see:
    http://www.openwall.com/lists/oss-security/2016/06/24/5
    http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4997
    http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4998
  (* Security fix *)
Other than kernel update which was only applied for current, php is also updated to 5.6.23 for Slackware 14.0, 14.1, and current. This update is also considered a security update.

In current, we have more updates coming in:
  • mariadb: Upgraded to 10.0.26
  • libpng: Upgraded to 1.6.23
  • librsvg: Upgraded to 2.40

Popular posts from this blog

Running Rsync Via Proxy

One way to get the latest Slackware updates is by running rsync to syncronize your local repository and the main repository that hold the Slackware packages. Eric Hameleers has provided a great script called rsync_current.sh and how i modified this tool has been discussed on my previous post. In general, it works, except for one problem, when your computer is connecting to the Internet through a proxy.

My workstation at my office is connected to the Internet through a proxy, so i can't use normal rsync to work normally. I browsed the web and i found this site which tells us about how we should modify our squid configuration to allow rsync connection from any computer from our local networks. I asked my sysadmin to try this script. He agreed and he updated the squid configuration on the proxy.

Next, i need to update my environment variable RSYNC_PROXY to the host of the proxy and also the port. Let's say you are running a proxy on 192.168.1.1 and port 8080, then you need to run …

NVidia Legacy Unix Driver Update

NVidia has released an updated legacy drivers to support X.Org 1.19 with ABI 23. It has been mentioned in the UNIX drivers, but you can directly find the drivers from the links below:
NVidia 304.134 (x86x86_64)NVidia 340.101 (x86, x86_64) I have tested the 304.134 driver and it's working great here. I can finally remove x from my /etc/slackpkg/blacklist file since it's a showstopper for me.
Aside from legacy driver, NVidia has also released their latest driver 375.26 (x86, x86_64), which brings support for newer cards and also many new features (including X.Org 1.19 with ABI 23 support). 

Security Update: firefox, irssi, pidgin

Three security updates were released for today:
firefox: Upgraded to 45.4.0esr for 14.1 and 14.2 and 49.0 for currentirssi: Upgraded to 0.8.20pidgin: Upgraded to 2.10.11, 2.10.12, and 2.11.0 for all stable Slackware releases depending on their support Some minor update in current:
mkinitrd: Add dmsetup supportemacs: Upgraded to 25.1qt: Fix multilib issue network-scripts: Fix minor issue