USN-3170-1: Linux kernel vulnerabilities<\/p>\n
11th January, 2017<\/em><\/p>\n A security issue affects these releases of Ubuntu and its Several security issues were fixed in the kernel.\n<\/p>\n Dmitry Vyukov discovered that the KVM implementation in the Linux kernel Andrey Konovalov discovered that signed integer overflows existed in the The problem can be corrected by updating your system to the following To update your system, please follow these instructions: After a standard system update you need to reboot your computer to make ATTENTION: Due to an unavoidable ABI change the kernel updates have CVE-2016-9756<\/a>, <\/p>\n CVE-2016-9793<\/a><\/p>\n Source: USN-3170-1: Linux kernel vulnerabilities<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" USN-3170-1: Linux kernel vulnerabilities Ubuntu Security Notice USN-3170-1 11th January, 2017 linux vulnerabilities A security issue affects these releases of Ubuntu and its derivatives: Ubuntu 16.10 Summary Several security issues were fixed in the kernel. Software description linux – Linux kernel Details Dmitry Vyukov discovered that the KVM implementation in the Linux kerneldid not properly initialize the Code Segment (CS) in certain error cases. Alocal attacker could use this to expose sensitive information (kernelmemory). (CVE-2016-9756) Andrey Konovalov discovered that signed integer overflows existed in thesetsockopt() system call when handling the SO_SNDBUFFORCE andSO_RCVBUFFORCE options. A local attacker with the CAP_NET_ADMIN capabilitycould use this to cause a denial of service (system crash or memorycorruption). (CVE-2016-9793) Update instructions The problem can be corrected by updating your system to the following package version: Ubuntu 16.10: linux-image-powerpc-smp 4.8.0.34.43 linux-image-powerpc-e500mc 4.8.0.34.43 linux-image-4.8.0-34-lowlatency 4.8.0-34.36 linux-image-generic 4.8.0.34.43 linux-image-generic-lpae [ more… ]<\/a><\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[586],"tags":[587],"class_list":["post-13214","post","type-post","status-publish","format-standard","hentry","category-ubuntu-usn","tag-ubuntu-usn"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/13214","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/comments?post=13214"}],"version-history":[{"count":1,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/13214\/revisions"}],"predecessor-version":[{"id":13215,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/13214\/revisions\/13215"}],"wp:attachment":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/media?parent=13214"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/categories?post=13214"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/tags?post=13214"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}linux vulnerabilities<\/h3>\n
\n derivatives:<\/p>\n\n
Summary<\/h3>\n
Software description<\/h3>\n
\n
\n – Linux kernel<\/p>\n<\/li>\n<\/ul>\nDetails<\/h3>\n
did not properly initialize the Code Segment (CS) in certain error cases. A
local attacker could use this to expose sensitive information (kernel
memory). (CVE-2016-9756<\/a>)<\/p>\n
setsockopt() system call when handling the SO_SNDBUFFORCE and
SO_RCVBUFFORCE options. A local attacker with the CAP_NET_ADMIN capability
could use this to cause a denial of service (system crash or memory
corruption). (CVE-2016-9793<\/a>)<\/p>\nUpdate instructions<\/h3>\n
\npackage version:<\/p>\n\n
\n
\n 4.8.0.34.43<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 4.8.0.34.43<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 4.8.0-34.36<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 4.8.0.34.43<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 4.8.0.34.43<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 4.8.0-34.36<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 4.8.0.34.43<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 4.8.0-34.36<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 4.8.0-34.36<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 4.8.0-34.36<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 4.8.0.34.43<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 4.8.0-34.36<\/a>
\n <\/span>\n <\/dd>\n<\/dl>\n
\nhttps:\/\/wiki.ubuntu.com\/Security\/Upgrades<\/a>.\n<\/p>\n
all the necessary changes.<\/p>\n
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.<\/p>\nReferences<\/h3>\n