Slackware: 2019-202-01: Slackware 14.2 kernel Security Update

    Date21 Jul 2019
    Posted ByLinuxSecurity Advisories
    New kernel packages are available for Slackware 14.2 to fix security issues.
    Hash: SHA1
    [slackware-security]  Slackware 14.2 kernel (SSA:2019-202-01)
    New kernel packages are available for Slackware 14.2 to fix security issues.
    Here are the details from the Slackware 14.2 ChangeLog:
    patches/packages/linux-4.4.182/*:  Upgraded.
      These updates fix various bugs and many minor security issues.
      Be sure to upgrade your initrd after upgrading the kernel packages.
      If you use lilo to boot your machine, be sure lilo.conf points to the correct
      kernel and initrd and run lilo as root to update the bootloader.
      If you use elilo to boot your machine, you should run eliloconfig to copy the
      kernel and initrd to the EFI System Partition.
      For more information, see:
        Fixed in 4.4.183:
        Fixed in 4.4.185:
        Fixed in 4.4.186:
      (* Security fix *)
    Where to find the new packages:
    Thanks to the friendly folks at the OSU Open Source Lab
    ( for donating FTP and rsync hosting
    to the Slackware project!  :-)
    Also see the "Get Slack" section on for
    additional mirror sites near you.
    Updated packages for Slackware 14.2:
    Updated packages for Slackware x86_64 14.2:
    MD5 signatures:
    Slackware 14.2 packages:
    01138ebc336b6e6d692697570bb32920  kernel-firmware-20190717_bf13a71-noarch-1.txz
    d7e0b9ffdc4265b45d4de39d49d52616  kernel-generic-4.4.186-i586-1.txz
    c1131f8dd16f7113cc8b1e14c402a9b7  kernel-generic-smp-4.4.186_smp-i686-1.txz
    ca4630c4ee7056c51f3262152bfb9213  kernel-headers-4.4.186_smp-x86-1.txz
    61b95e68756fe9741ddbdc52f397fe49  kernel-huge-4.4.186-i586-1.txz
    ff981138513726a502d57f9e2aecad36  kernel-huge-smp-4.4.186_smp-i686-1.txz
    ca8f6fb5fc378d16e5afcee31dd032dc  kernel-modules-4.4.186-i586-1.txz
    25fc2f1280f1a706705ef4535f4efd1c  kernel-modules-smp-4.4.186_smp-i686-1.txz
    2d299723d6f910df1e8c21d18070b9ef  kernel-source-4.4.186_smp-noarch-1.txz
    Slackware x86_64 14.2 packages:
    01138ebc336b6e6d692697570bb32920  kernel-firmware-20190717_bf13a71-noarch-1.txz
    80caffb238022225afe93b957fecbff2  kernel-generic-4.4.186-x86_64-1.txz
    f72e4543e3489d18604f33a901e04551  kernel-headers-4.4.186-x86-1.txz
    0765db332a94cfedcacd987871903e56  kernel-huge-4.4.186-x86_64-1.txz
    8d565a7b223b9444731796e6147116eb  kernel-modules-4.4.186-x86_64-1.txz
    0254fdbb4430362ea373b47584d8eb30  kernel-source-4.4.186-noarch-1.txz
    Installation instructions:
    Upgrade the packages as root:
    # upgradepkg kernel-*.txz
    If you are using an initrd, you'll need to rebuild it.
    For a 32-bit SMP machine, use this command (substitute the appropriate
    kernel version if you are not running Slackware 14.2):
    # /usr/share/mkinitrd/ -k 4.4.186-smp | bash
    For a 64-bit machine, or a 32-bit uniprocessor machine, use this command
    (substitute the appropriate kernel version if you are not running
    Slackware 14.2):
    # /usr/share/mkinitrd/ -k 4.4.186 | bash
    Please note that "uniprocessor" has to do with the kernel you are running,
    not with the CPU. Most systems should run the SMP kernel (if they can)
    regardless of the number of cores the CPU has. If you aren't sure which
    kernel you are running, run "uname -a". If you see SMP there, you are
    running the SMP kernel and should use the 4.4.186-smp version when running
    mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit
    systems should always use 4.4.186 as the version.
    If you are using lilo or elilo to boot the machine, you'll need to ensure
    that the machine is properly prepared before rebooting.
    If using LILO:
    By default, lilo.conf contains an image= line that references a symlink
    that always points to the correct kernel. No editing should be required
    unless your machine uses a custom lilo.conf. If that is the case, be sure
    that the image= line references the correct kernel file.  Either way,
    you'll need to run "lilo" as root to reinstall the boot loader.
    If using elilo:
    Ensure that the /boot/vmlinuz symlink is pointing to the kernel you wish
    to use, and then run eliloconfig to update the EFI System Partition.
    You are not authorised to post comments.

    Comments powered by CComment

    LinuxSecurity Poll

    What do you think of the articles on LinuxSecurity?

    No answer selected. Please try again.
    Please select either existing option or enter your own, however not both.
    Please select minimum 0 answer(s) and maximum 3 answer(s).
    [{"id":"87","title":"Excellent, don't change a thing!","votes":"65","type":"x","order":"1","pct":57.52,"resources":[]},{"id":"88","title":"Should be more technical","votes":"15","type":"x","order":"2","pct":13.27,"resources":[]},{"id":"89","title":"Should include more HOWTOs","votes":"33","type":"x","order":"3","pct":29.2,"resources":[]}]["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"]["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"]350

    We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.