Security and bugfixes, advisory will follow... SRPMS: kernel-linus-5.10.27-1.mga8.src.rpm i586: kernel-linus-5.10.27-1.mga8-1-1.mga8.i586.rpm kernel-linus-devel-5.10.27-1.mga8-1-1.mga8.i586.rpm kernel-linus-devel-latest-5.10.27-1.mga8.i586.rpm kernel-linus-doc-5.10.27-1.mga8.noarch.rpm kernel-linus-latest-5.10.27-1.mga8.i586.rpm kernel-linus-source-5.10.27-1.mga8-1-1.mga8.noarch.rpm kernel-linus-source-latest-5.10.27-1.mga8.noarch.rpm x86_64: kernel-linus-5.10.27-1.mga8-1-1.mga8.x86_64.rpm kernel-linus-devel-5.10.27-1.mga8-1-1.mga8.x86_64.rpm kernel-linus-devel-latest-5.10.27-1.mga8.x86_64.rpm kernel-linus-doc-5.10.27-1.mga8.noarch.rpm kernel-linus-latest-5.10.27-1.mga8.x86_64.rpm kernel-linus-source-5.10.27-1.mga8-1-1.mga8.noarch.rpm kernel-linus-source-latest-5.10.27-1.mga8.noarch.rpm
Mga7 rpms: SRPMS: kernel-linus-5.10.27-1.mga7.src.rpm i586: kernel-linus-5.10.27-1.mga7-1-1.mga7.i586.rpm kernel-linus-devel-5.10.27-1.mga7-1-1.mga7.i586.rpm kernel-linus-devel-latest-5.10.27-1.mga7.i586.rpm kernel-linus-doc-5.10.27-1.mga7.noarch.rpm kernel-linus-latest-5.10.27-1.mga7.i586.rpm kernel-linus-source-5.10.27-1.mga7-1-1.mga7.noarch.rpm kernel-linus-source-latest-5.10.27-1.mga7.noarch.rpm x86_64: kernel-linus-5.10.27-1.mga7-1-1.mga7.x86_64.rpm kernel-linus-devel-5.10.27-1.mga7-1-1.mga7.x86_64.rpm kernel-linus-devel-latest-5.10.27-1.mga7.x86_64.rpm kernel-linus-doc-5.10.27-1.mga7.noarch.rpm kernel-linus-latest-5.10.27-1.mga7.x86_64.rpm kernel-linus-source-5.10.27-1.mga7-1-1.mga7.noarch.rpm kernel-linus-source-latest-5.10.27-1.mga7.noarch.rpm
Summary: Update reqest: kernel-linus-5.10.27-1.mga8 => Update reqest: kernel-linus-5.10.27-1.mga8/7Whiteboard: (none) => MGA7TOO
Advisory, added to svn: type: security subject: Updated kernel-linus packages fix security vulnerabilities CVE: - CVE-2021-28688 - CVE-2021-28951 - CVE-2021-28964 - CVE-2021-28971 - CVE-2021-28972 - CVE-2021-29266 src: 8: core: - kernel-linus-5.10.27-1.mga8 7: core: - kernel-linus-5.10.27-1.mga7 description: | This kernel-linus update is based on upstream 5.10.27 and fixes atleast the following security issues: The fix for XSA-365 includes initialization of pointers such that subsequent cleanup code wouldn't use uninitialized or stale values. This initialization went too far and may under certain conditions also overwrite pointers which are in need of cleaning up. The lack of cleanup would result in leaking persistent grants. The leak in turn would prevent fully cleaning up after a respective guest has died, leaving around zombie domains. A malicious or buggy frontend driver may be able to cause resource leaks from the corresponding backend driver. This can result in a host-wide Denial of Sevice (DoS). (CVE-2021-28688 / XSA-371). An issue was discovered in fs/io_uring.c in the Linux kernel through 5.11.8. It allows attackers to cause a denial of service (deadlock) because exit may be waiting to park a SQPOLL thread, but concurrently that SQPOLL thread is waiting for a signal to start (CVE-2021-28951). A race condition was discovered in get_old_root in fs/btrfs/ctree.c in the Linux kernel through 5.11.8. It allows attackers to cause a denial of service (BUG) because of a lack of locking on an extent buffer before a cloning operation (CVE-2021-28964). In intel_pmu_drain_pebs_nhm in arch/x86/events/intel/ds.c in the Linux kernel through 5.11.8 on some Haswell CPUs, userspace applications (such as perf-fuzzer) can cause a system crash because the PEBS status in a PEBS record is mishandled(CVE-2021-28971). In drivers/pci/hotplug/rpadlpar_sysfs.c in the Linux kernel through 5.11.8, the RPA PCI Hotplug driver has a user-tolerable buffer overflow when writing a new device name to the driver from userspace, allowing userspace to write data to the kernel stack frame directly. This occurs because add_slot_store and remove_slot_store mishandle drc_name '\0' termination (CVE-2021-28972). An issue was discovered in the Linux kernel before 5.11.9. drivers/vhost/ vdpa.c has a use-after-free because v->config_ctx has an invalid value upon re-opening a character device (CVE-2021-29266). It also adds the following fixes: - arm: enable OF_OVERLAY (mga#28596) For other upstream fixes, see the referenced changelogs. references: - https://bugs.mageia.org/show_bug.cgi?id=28691 - https://bugs.mageia.org/show_bug.cgi?id=28596 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.26 - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.27 - https://xenbits.xen.org/xsa/advisory-371.html
Keywords: (none) => advisory
Kernel: 5.10.27-1.mga7 x86_64 Quad Core: Intel Core i7-4790 NVIDIA GM204 [GeForce GTX 970] driver: nouveau OpenGL: renderer: NV124 v: 4.3 Mesa 20.2.3 Rebooted with the Linus kernel. Desktop as before. Virtualbox running. ssh login across the lan working with authorized keys. NFS shares registered. QA backup folder on NAS mounted OK. Installed celestia and started it. It runs fairly well on a 4K monitor with the nouveau driver. LO writer, vlc sound and video, gwenview, okular, no problems. Set up wifi printer using MCC -> hardware. Printed test page OK and a document from LO but then disaster struck - lpr no longer works. I have been using it from within a label page printing script for over 25 years. I have done nothing except what is required for every installation when adding a printer. Now commands such as this fail - $ lpr -Pokda tmp/abc-0.ps lpr: Error - The printer or class does not exist. CUPS certainly sees the printer in firefox but there are no classes defined - a facility that has never been needed. Under printers -> maintenance it prints a test page OK. Something may be missing this time round.
CC: (none) => tarazed25
Panic over. Had forgotten to connect the printer to the server. Getting too old and senile for this job.
Whiteboard: MGA7TOO => MGA7TOO, MGA8-64-OK, MGA7-64-OKCC: (none) => sysadmin-bugsKeywords: (none) => validated_update
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2021-0175.html
Status: NEW => RESOLVEDResolution: (none) => FIXED