MGASA-2014-0453
- Source
- https://advisories.mageia.org/MGASA-2014-0453.html
- Import Source
- https://advisories.mageia.org/MGASA-2014-0453.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/MGASA-2014-0453
- Related
- Published
- 2014-11-15T18:31:46Z
- Modified
- 2014-11-15T18:13:30Z
- Summary
- Updated kernel packages fix security vulnerabilities
- Details
-
This kernel update is based on upstream -longterm 3.14.23 and fixes the following security issues:
The kvmiommumap_pages function in virt/kvm/iommu.c in the Linux kernel through 3.16.1 miscalculates the number of pages during the handling of a mapping failure, which allows guest OS users to (1) cause a denial of service (host OS memory corruption) or possibly have unspecified other impact by triggering a large gfn value or (2) cause a denial of service (host OS memory consumption) by triggering a small gfn value that leads to permanently pinned pages (CVE-2014-3601).
The assocarraygc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multiple "keyctl newring" operations followed by a "keyctl timeout" operation (CVE-2014-3631).
The pivotroot implementation in fs/namespace.c in the Linux kernel through 3.17 does not properly interact with certain locations of a chroot directory, which allows local users to cause a denial of service (mount-tree loop) via . (dot) values in both arguments to the pivotroot system call (CVE-2014-7970).
The doumount function in fs/namespace.c in the Linux kernel through 3.17 does not require the CAPSYSADMIN capability for doremountsb calls that change the root filesystem to read-only, which allows local users to cause a denial of service (loss of writability) by making certain unshare system calls, clearing the / MNTLOCKED flag, and making an MNT_FORCE umount system call (CVE-2014-7975).
Other fixes: The X86_SYSFB config option has been disabled as it prevents proper KMS setup on some systems (mga#13098)
The cpupower default governor has been switched from ondemand to performance as the intel_pstate driver (used on newer Intel cpus) does not support ondemand target.
For other fixes included in this update, read the referenced changelogs.
- References
-
- https://advisories.mageia.org/MGASA-2014-0453.html
- https://bugs.mageia.org/show_bug.cgi?id=14301
- https://bugs.mageia.org/show_bug.cgi?id=13098
- https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.19
- https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.20
- https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.21
- https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.22
- https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.23
- Credits
-
-
- Mageia - COORDINATOR
-
Affected packages
Mageia:4 / kmod-broadcom-wl
Package
- Name
- kmod-broadcom-wl
- Purl
- pkg:rpm/mageia/kmod-broadcom-wl?distro=mageia-4
Mageia:4 / kmod-fglrx
Package
- Name
- kmod-fglrx
- Purl
- pkg:rpm/mageia/kmod-fglrx?distro=mageia-4
Mageia:4 / kmod-nvidia173
Package
- Name
- kmod-nvidia173
- Purl
- pkg:rpm/mageia/kmod-nvidia173?distro=mageia-4
Mageia:4 / kmod-nvidia-current
Package
- Name
- kmod-nvidia-current
- Purl
- pkg:rpm/mageia/kmod-nvidia-current?distro=mageia-4
Mageia:4 / kernel
Package
- Name
- kernel
- Purl
- pkg:rpm/mageia/kernel?distro=mageia-4
Mageia:4 / kernel-userspace-headers
Package
- Name
- kernel-userspace-headers
- Purl
- pkg:rpm/mageia/kernel-userspace-headers?distro=mageia-4
Mageia:4 / kmod-xtables-addons
Package
- Name
- kmod-xtables-addons
- Purl
- pkg:rpm/mageia/kmod-xtables-addons?distro=mageia-4
Mageia:4 / rpm-mageia-setup
Package
- Name
- rpm-mageia-setup
- Purl
- pkg:rpm/mageia/rpm-mageia-setup?distro=mageia-4