I don't know whether we should worry about CVE-2017-2636, filing this bug in case we should. A Dutch tech website is blaming Linux distros for being slow to fix the issue. I don't know whether the issue is as bad as they think, but ticking the "secteam" box in case they are. They claim as good as all distros which have "CONFIG_N_HDLC=m" in their kernel config are affected. $ grep "CONFIG_N_HDLC=m" /boot/config-4.9.16-desktop-2.mga6 CONFIG_N_HDLC=m [marja@localhost ~]$
CC: (none) => makowski.mageiaSee Also: (none) => https://bugzilla.redhat.com/show_bug.cgi?id=1428319
according to RedHat : Upstream patch: https://git.kernel.org/cgit/linux/kernel/git/gregkh/tty.git/commit/?h=tty-linus&id=82f2341c94d270421f383641b7cd670e474db56b and Mitigation: The n_hdlc kernel module will be automatically loaded when an application attempts to use the HDLC line discipline from userspace. This module can be prevented from being loaded by using the system-wide modprobe rules. The following command, run as root, will prevent accidental or intentional loading of the module. Red Hat Product Security believe this method is a robust method to prevent accidental loading of the module, even by privileged users. รข# echo "install n_hdlc /bin/true" >> /etc/modprobe.d/disable-n_hdlc.conf
Yes, Cauldron is fixed as of kernel 4.9.15 Mga5 kernel 4.4 series is fixed upstream as of 4.4.54 I have 4.4.55-1 sets assigned to QA since 2017-03-19 https://bugs.mageia.org/show_bug.cgi?id=20527 https://bugs.mageia.org/show_bug.cgi?id=20528 https://bugs.mageia.org/show_bug.cgi?id=20529
(In reply to Thomas Backlund from comment #2) > Yes, Cauldron is fixed as of kernel 4.9.15 > > Mga5 kernel 4.4 series is fixed upstream as of 4.4.54 > > I have 4.4.55-1 sets assigned to QA since 2017-03-19 > > https://bugs.mageia.org/show_bug.cgi?id=20527 > https://bugs.mageia.org/show_bug.cgi?id=20528 > https://bugs.mageia.org/show_bug.cgi?id=20529 Thanks, Thomas :-)
Version: Cauldron => 5Depends on: (none) => 20527, 20528, 20529
Mga5 kernels now pushed
Status: NEW => RESOLVEDResolution: (none) => FIXED
This got fixed long ago, there's no need to keep this report hidden. So removing the tick that made it only visible to secteam.
Group: secteam => (none)