Linux Security
    Linux Security
    Linux Security

    Slackware: 2020-163-01: Slackware 14.2 kernel Security Update

    Posted By
    New kernel packages are available for Slackware 14.2 to fix security issues.
    Hash: SHA1
    [slackware-security]  Slackware 14.2 kernel (SSA:2020-163-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.227/*:  Upgraded.
      These updates fix various bugs and security issues, including a mitigation
      for SRBDS (Special Register Buffer Data Sampling). SRBDS is an MDS-like
      speculative side channel that can leak bits from the random number generator
      (RNG) across cores and threads.
      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.218:
        Fixed in 4.4.219:
        Fixed in 4.4.220:
        Fixed in 4.4.221:
        Fixed in 4.4.222:
        Fixed in 4.4.224:
        Fixed in 4.4.225:
        Fixed in 4.4.226:
        Fixed in 4.4.227:
      (* 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:
    9a40d88eccfd6fd52ff545cefe86f87b  kernel-generic-4.4.227-i586-1.txz
    c13f5fa4ef1e1b205b55b8200a82164d  kernel-generic-smp-4.4.227_smp-i686-1.txz
    98070c7ae594d9cd3c5a7d2a81aefb79  kernel-headers-4.4.227_smp-x86-1.txz
    1411df7a758aa56ab7352ab251c33187  kernel-huge-4.4.227-i586-1.txz
    edae1a14db491ed3704e97cb5f78e846  kernel-huge-smp-4.4.227_smp-i686-1.txz
    4f0b746f0eda80865a5507485f220c8c  kernel-modules-4.4.227-i586-1.txz
    bc4c4a2c3cfb5c51457965dc95d44331  kernel-modules-smp-4.4.227_smp-i686-1.txz
    3dfd157f38293392f5ca8ce935e70b8c  kernel-source-4.4.227_smp-noarch-1.txz
    Slackware x86_64 14.2 packages:
    6c8ff864c67d0f5d47b1ed13a81fc912  kernel-generic-4.4.227-x86_64-1.txz
    2a768057dd773822621dfcf069e6edea  kernel-headers-4.4.227-x86-1.txz
    25480853bc1c014faed7285517aaa1b1  kernel-huge-4.4.227-x86_64-1.txz
    832fe6fa4b00c166f9467208c1e47d9d  kernel-modules-4.4.227-x86_64-1.txz
    3b83ef123fbc7fe8b5d7957f1a08c3e4  kernel-source-4.4.227-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.227-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.227 | 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.227-smp version when running
    mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit
    systems should always use 4.4.227 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.

    LinuxSecurity Poll

    I agree with Linus Torvalds - Apple's new M1-powered laptops should run on Linux.

    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 2 answer(s).
    [{"id":"158","title":"True","votes":"8","type":"x","order":"1","pct":100,"resources":[]},{"id":"159","title":"False","votes":"0","type":"x","order":"2","pct":0,"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

    Please vote first in order to view vote results.


    bottom 200

    Please enable / Bitte aktiviere JavaScript!
    Veuillez activer / Por favor activa el Javascript![ ? ]

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