USN-3314-1: Linux kernel vulnerabilities
Publication date
7 June 2017
Overview
Several security issues were fixed in the Linux kernel.
Releases
Packages
- linux - Linux kernel
- linux-raspi2 - Linux kernel for Raspberry Pi 2
Details
It was discovered that the keyring implementation in the Linux kernel in
some situations did not prevent special internal keyrings from being joined
by userspace keyrings. A privileged local attacker could use this to bypass
module verification. (CVE-2016-9604)
It was discovered that a buffer overflow existed in the trace subsystem in
the Linux kernel. A privileged local attacker could use this to execute
arbitrary code. (CVE-2017-0605)
Daniel Jiang discovered that a race condition existed in the ipv4 ping
socket implementation in the Linux kernel. A local privileged attacker
could use this to cause a denial of service (system crash). (CVE-2017-2671)
JongHwan Kim discovered an out-of-bounds read in the TCP stack of the Linux
kernel. A local attacker could use this to cause a denial of service
(system crash) or...
It was discovered that the keyring implementation in the Linux kernel in
some situations did not prevent special internal keyrings from being joined
by userspace keyrings. A privileged local attacker could use this to bypass
module verification. (CVE-2016-9604)
It was discovered that a buffer overflow existed in the trace subsystem in
the Linux kernel. A privileged local attacker could use this to execute
arbitrary code. (CVE-2017-0605)
Daniel Jiang discovered that a race condition existed in the ipv4 ping
socket implementation in the Linux kernel. A local privileged attacker
could use this to cause a denial of service (system crash). (CVE-2017-2671)
JongHwan Kim discovered an out-of-bounds read in the TCP stack of the Linux
kernel. A local attacker could use this to cause a denial of service
(system crash) or leak sensitive information. (CVE-2017-7277)
Eric Biggers discovered a memory leak in the keyring implementation in the
Linux kernel. A local attacker could use this to cause a denial of service
(memory consumption). (CVE-2017-7472)
Sabrina Dubroca discovered that the asynchronous cryptographic hash (ahash)
implementation in the Linux kernel did not properly handle a full request
queue. A local attacker could use this to cause a denial of service
(infinite recursion). (CVE-2017-7618)
Tuomas Haanpää and Ari Kauppi discovered that the NFSv2 and NFSv3 server
implementations in the Linux kernel did not properly handle certain long
RPC replies. A remote attacker could use this to cause a denial of service
(system crash). (CVE-2017-7645)
Tommi Rantala and Brad Spengler discovered that the memory manager in the
Linux kernel did not properly enforce the CONFIG_STRICT_DEVMEM protection
mechanism. A local attacker with access to /dev/mem could use this to
expose sensitive information or possibly execute arbitrary code.
(CVE-2017-7889)
Tuomas Haanpää and Ari Kauppi discovered that the NFSv2 and NFSv3 server
implementations in the Linux kernel did not properly check for the end of
buffer. A remote attacker could use this to craft requests that cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2017-7895)
Fabian Grünbichler discovered that the Packet action API implementation in
the Linux kernel improperly handled uninitialized data. A local attacker
could use this to cause a denial of service (system crash) or possibly
execute arbitrary code. (CVE-2017-7979)
It was discovered that the Conexant USB driver in the Linux kernel
improperly handled memory in some configurations. A local attacker could
use this to cause a denial of service (system crash). (CVE-2017-8063)
It was discovered that the DVD USB framework in the Linux kernel improperly
handled memory in some configurations. A local attacker could use this to
cause a denial of service (system crash). (CVE-2017-8064)
It was discovered that the virtio console driver in the Linux kernel
improperly handled memory. A local attacker could use this to cause a
denial of service (system crash). (CVE-2017-8067)
Update instructions
After a standard system update you need to reboot your computer to make all the necessary changes.
Learn more about how to get the fixes.The problem can be corrected by updating your system to the following package versions:
Ubuntu Release | Package Version | ||
---|---|---|---|
17.04 zesty | linux-image-generic-lpae – 4.10.0.22.24 | ||
linux-image-4.10.0-22-generic-lpae – 4.10.0-22.24 | |||
linux-image-4.10.0-1006-raspi2 – 4.10.0-1006.8 | |||
linux-image-4.10.0-22-lowlatency – 4.10.0-22.24 | |||
linux-image-generic – 4.10.0.22.24 | |||
linux-image-4.10.0-22-generic – 4.10.0-22.24 | |||
linux-image-lowlatency – 4.10.0.22.24 | |||
linux-image-raspi2 – 4.10.0.1006.8 |
Reduce your security exposure
Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.
References
- CVE-2017-8067
- CVE-2017-8064
- CVE-2017-8063
- CVE-2017-7979
- CVE-2017-7895
- CVE-2017-7889
- CVE-2017-7645
- CVE-2017-7618
- CVE-2017-7472
- CVE-2017-7277
- CVE-2017-8067
- CVE-2017-8064
- CVE-2017-8063
- CVE-2017-7979
- CVE-2017-7895
- CVE-2017-7889
- CVE-2017-7645
- CVE-2017-7618
- CVE-2017-7472
- CVE-2017-7277
- CVE-2017-2671
- CVE-2017-0605
- CVE-2016-9604
Have additional questions?