Security and bug fixes, advisory will follow... SRPMS: kernel-5.10.19-1.mga7.src.rpm kmod-virtualbox-6.1.18-7.mga7.src.rpm kmod-xtables-addons-3.13-13.mga7.src.rpm i586: cpupower-5.10.19-1.mga7.i586.rpm cpupower-devel-5.10.19-1.mga7.i586.rpm kernel-desktop-5.10.19-1.mga7-1-1.mga7.i586.rpm kernel-desktop586-5.10.19-1.mga7-1-1.mga7.i586.rpm kernel-desktop586-devel-5.10.19-1.mga7-1-1.mga7.i586.rpm kernel-desktop586-devel-latest-5.10.19-1.mga7.i586.rpm kernel-desktop586-latest-5.10.19-1.mga7.i586.rpm kernel-desktop-devel-5.10.19-1.mga7-1-1.mga7.i586.rpm kernel-desktop-devel-latest-5.10.19-1.mga7.i586.rpm kernel-desktop-latest-5.10.19-1.mga7.i586.rpm kernel-doc-5.10.19-1.mga7.noarch.rpm kernel-server-5.10.19-1.mga7-1-1.mga7.i586.rpm kernel-server-devel-5.10.19-1.mga7-1-1.mga7.i586.rpm kernel-server-devel-latest-5.10.19-1.mga7.i586.rpm kernel-server-latest-5.10.19-1.mga7.i586.rpm kernel-source-5.10.19-1.mga7-1-1.mga7.noarch.rpm kernel-source-latest-5.10.19-1.mga7.noarch.rpm kernel-userspace-headers-5.10.19-1.mga7.i586.rpm libbpf0-5.10.19-1.mga7.i586.rpm libbpf-devel-5.10.19-1.mga7.i586.rpm perf-5.10.19-1.mga7.i586.rpm xtables-addons-kernel-5.10.19-desktop-1.mga7-3.13-13.mga7.i586.rpm xtables-addons-kernel-5.10.19-desktop586-1.mga7-3.13-13.mga7.i586.rpm xtables-addons-kernel-5.10.19-server-1.mga7-3.13-13.mga7.i586.rpm xtables-addons-kernel-desktop586-latest-3.13-13.mga7.i586.rpm xtables-addons-kernel-desktop-latest-3.13-13.mga7.i586.rpm xtables-addons-kernel-server-latest-3.13-13.mga7.i586.rpm x86_64: bpftool-5.10.19-1.mga7.x86_64.rpm cpupower-5.10.19-1.mga7.x86_64.rpm cpupower-devel-5.10.19-1.mga7.x86_64.rpm kernel-desktop-5.10.19-1.mga7-1-1.mga7.x86_64.rpm kernel-desktop-devel-5.10.19-1.mga7-1-1.mga7.x86_64.rpm kernel-desktop-devel-latest-5.10.19-1.mga7.x86_64.rpm kernel-desktop-latest-5.10.19-1.mga7.x86_64.rpm kernel-doc-5.10.19-1.mga7.noarch.rpm kernel-server-5.10.19-1.mga7-1-1.mga7.x86_64.rpm kernel-server-devel-5.10.19-1.mga7-1-1.mga7.x86_64.rpm kernel-server-devel-latest-5.10.19-1.mga7.x86_64.rpm kernel-server-latest-5.10.19-1.mga7.x86_64.rpm kernel-source-5.10.19-1.mga7-1-1.mga7.noarch.rpm kernel-source-latest-5.10.19-1.mga7.noarch.rpm kernel-userspace-headers-5.10.19-1.mga7.x86_64.rpm lib64bpf0-5.10.19-1.mga7.x86_64.rpm lib64bpf-devel-5.10.19-1.mga7.x86_64.rpm perf-5.10.19-1.mga7.x86_64.rpm virtualbox-kernel-5.10.19-desktop-1.mga7-6.1.18-7.mga7.x86_64.rpm virtualbox-kernel-5.10.19-server-1.mga7-6.1.18-7.mga7.x86_64.rpm virtualbox-kernel-desktop-latest-6.1.18-7.mga7.x86_64.rpm virtualbox-kernel-server-latest-6.1.18-7.mga7.x86_64.rpm xtables-addons-kernel-5.10.19-desktop-1.mga7-3.13-13.mga7.x86_64.rpm xtables-addons-kernel-5.10.19-server-1.mga7-3.13-13.mga7.x86_64.rpm xtables-addons-kernel-desktop-latest-3.13-13.mga7.x86_64.rpm xtables-addons-kernel-server-latest-3.13-13.mga7.x86_64.rpm
Kernel: 5.10.19-desktop-1.mga7 x86_64 MATE 1.22.1 Mobo: MSI model: Z97-G43 (MS-7816) Quad Core: Intel Core i7-4790 type: MT MCP NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 460.32.03 Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet : driver: r8169 RAM: 32GB No problems installing the desktop kernel. The graphics card driver was rebuilt before reboot. Rebooted smoothly and fast. Two virtualbox clients launched fine. Ran stress tests and glmark2. A few skips and 6 failures in `perf test`. Opened a password-protected file in LO writer. Used GIMP to manipulate an image. Opened darktable on an image. Played an MP4 film in vlc - sound and video OK. No problems encountered.
CC: (none) => tarazed25
64 bit OK on My workstation "svarten": Mainboard: Sabertooth P67, CPU: i7-3770, RAM 16G, GM107 [GeForce GTX 750] using nvidia-current; GeForce 635 series and later, 4k display. Was already running with 5.10.16 a few days Yesterday updated to: - cpupower-5.10.19-1.mga7.x86_64 - dkms-nvidia-current-460.56-1.mga7.nonfree.x86_64 - kernel-desktop-5.10.19-1.mga7-1-1.mga7.x86_64 - kernel-desktop-devel-5.10.19-1.mga7-1-1.mga7.x86_64 - kernel-desktop-devel-latest-5.10.19-1.mga7.x86_64 - kernel-desktop-latest-5.10.19-1.mga7.x86_64 - kernel-userspace-headers-5.10.19-1.mga7.x86_64 - ldetect-lst-0.6.9.2-1.mga7.x86_64 - nvidia-current-cuda-opencl-460.56-1.mga7.nonfree.x86_64 - nvidia-current-doc-html-460.56-1.mga7.nonfree.x86_64 - nvidia-current-utils-460.56-1.mga7.nonfree.x86_64 - x11-driver-video-nvidia-current-460.56-1.mga7.nonfree.x86_64 Today also kernel-firmware-nonfree-20210223-1.mga7.nonfree.x86_64 rebooted, $ sudo dkms status tells nvidia-current and virtualbox are OK Disk&Filesystem: SSD with /boot/EFI and ext4 /boot, LUKS{LVM {swap, ext4 /home & / } and a spinner at /mnt/somewhere Plasma desktop, using Thunderbird, LibreOffice, Ktorrent, Nextcloud client... Video with sound in Firefox CUDA and OpenCL detected Stress test: While working with other things BOINC use all cores to 100%, videos do not stutter. Also virtualbox 6.1.18 OK running MSW7 64 bit guest incl folder sharing, USB memory, bidirectional clipboard, dynamic guest window resizing. All as usual, need to free 1 or 2 cores from BOINC to avoid video stutter in guest Firefox, playing video with sound from internet svtplay.se.
CC: (none) => fri
Same, lazy tests ;) MGA7 x86_64 on Intel Core i5 3570K, Nvidia Geforce GTX 670. - cpupower-5.10.19-1.mga7.x86_64 - dkms-nvidia-current-460.56-1.mga7.nonfree.x86_64 - kernel-desktop-5.10.19-1.mga7-1-1.mga7.x86_64 - kernel-desktop-devel-5.10.19-1.mga7-1-1.mga7.x86_64 - kernel-desktop-devel-latest-5.10.19-1.mga7.x86_64 - kernel-desktop-latest-5.10.19-1.mga7.x86_64 - kernel-userspace-headers-5.10.19-1.mga7.x86_64 - ldetect-lst-0.6.9.2-1.mga7.x86_64 - nvidia-current-cuda-opencl-460.56-1.mga7.nonfree.x86_64 - nvidia-current-doc-html-460.56-1.mga7.nonfree.x86_64 - nvidia-current-utils-460.56-1.mga7.nonfree.x86_64 - x11-driver-video-nvidia-current-460.56-1.mga7.nonfree.x86_64 Today also kernel-firmware-nonfree-20210223-1.mga7.nonfree.x86_64 Success. DKMS recompile OK. Stable system, All usage, WiFI, Network, USB, Bluetooth, 3D/openGL OK No errors in system journal.
Whiteboard: (none) => MGA8-64-OKCC: (none) => ouaurelien
Oups.
Whiteboard: MGA8-64-OK => MGA7-64-OK
advisory, added to svn: type: security subject: Updated kernel packages fix security vulnerabilities CVE: - CVE-2021-20194 - CVE-2021-26930 - CVE-2021-26931 - CVE-2021-26932 src: 7: core: - kernel-5.10.19-1.mga7 - kmod-virtualbox-6.1.18-7.mga7 - kmod-xtables-addons-3.13-13.mga7 description: | This kernel update is based on upstream 5.10.19 and fixes atleast the following security issues: There is a vulnerability in the linux kernel versions higher than 5.2 (if kernel compiled with config params CONFIG_BPF_SYSCALL=y, CONFIG_BPF=y, CONFIG_CGROUPS=y, CONFIG_CGROUP_BPF=y, CONFIG_HARDENED_USERCOPY not set, and BPF hook to getsockopt is registered). As result of BPF execution, the local user can trigger bug in __cgroup_bpf_run_filter_getsockopt() function that can lead to heap overflow (because of non-hardened usercopy). The impact of attack could be deny of service or possibly privileges escalation. NOTE! Mageia kernel configs have HARDENED_USERCOPY enabled by default, making this an non-issue when using prebuilt kernels (CVE-2021-20194). An issue was discovered in the Linux kernel 3.11 through 5.10.16, as used by Xen. To service requests to the PV backend, the driver maps grant references provided by the frontend. In this process, errors may be encountered. In one case, an error encountered earlier might be discarded by later processing, resulting in the caller assuming successful mapping, and hence subsequent operations trying to access space that wasn't mapped. In another case, internal state would be insufficiently updated, preventing safe recovery from the error (CVE-2021-26930). An issue was discovered in the Linux kernel 2.6.39 through 5.10.16, as used in Xen. Block, net, and SCSI backends consider certain errors a plain bug, deliberately causing a kernel crash. For errors potentially being at least under the influence of guests (such as out of memory conditions), it isn't correct to assume a plain bug. Memory allocations potentially causing such crashes occur only when Linux is running in PV mode, though (CVE-2021-26931). An issue was discovered in the Linux kernel 3.2 through 5.10.16, as used by Xen. Grant mapping operations often occur in batch hypercalls, where a number of operations are done in a single hypercall, the success or failure of each one is reported to the backend driver, and the backend driver then loops over the results, performing follow-up actions based on the success or failure of each operation. Unfortunately, when running in PV mode, the Linux backend drivers mishandle this: Some errors are ignored, effectively implying their success from the success of related batch elements. In other cases, errors resulting from one batch element lead to further batch elements not being inspected, and hence successful ones to not be possible to properly unmap upon error recovery. Only systems with Linux backends running in PV mode are vulnerable. Linux backends run in HVM / PVH modes are not vulnerable (CVE-2021-26932). It also adds the following fixes: - enable ACPI_EC_DEBUGFS (mga#28415) - ALSA: hda: Add another CometLake-H PCI ID - Revert 'drm/amd/display: Update NV1x SR latency values' - drm/nouveau/kms: handle mDP connectors - drm/i915/gt: One more flush for Baytrail clear residuals - drm/i915/gt: Flush before changing register state - drm/i915/gt: Correct surface base address for renderclear - rtw88: 8821c: add RFE type 2 support - update rtw89 patchset to v3 - tracing: Check length before giving out the filter buffer - drop "revert 'Bluetooth: btusb: Add Qualcomm Bluetooth SoC WCN6855 support' (mga#27910)" - Bluetooth: btusb: fix for Qualcomm Bluetooth adapters that stopped working due to not finding (unneeded) ROME firmware (real fix for mga#27910) - media: uvcvideo: Allow entities with no pads - mm/vmscan: restore zone_reclaim_mode ABI - nvme: Add quirks for Lexar 256GB SSD (pterjan, mga#28417) - nvme: add 48-bit DMA address quirk for Amazon NVMe controllers - nvme-pci: add the DISABLE_WRITE_ZEROES quirk for a SPCC device - staging/rtl8723bs: sync with 5.12-rc1 (mga#28429) - x86: fix seq_file iteration for pat/memtype.c For other upstream fixes, see the referenced changelogs. references: - https://bugs.mageia.org/show_bug.cgi?id=28467 - https://bugs.mageia.org/show_bug.cgi?id=28435 - https://bugs.mageia.org/show_bug.cgi?id=28429 - https://bugs.mageia.org/show_bug.cgi?id=28417 - https://bugs.mageia.org/show_bug.cgi?id=28415 - https://bugs.mageia.org/show_bug.cgi?id=27910 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.15 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.16 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.17 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.18 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.19
Keywords: (none) => advisory
MGA7 - Gnome, Nvidia 390 driver, real hardware I installed this and forgot about it. Seems to be working without an issue. Sound, browser, networking, etc.
CC: (none) => brtians1
Validating. Advisory already pushed.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2021-0099.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED