[DONE] wml://security/2018/dsa-4187.wml
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
- --- ../../english/security/2018/dsa-4187.wml 2018-05-01 23:12:56.000000000 +0500
+++ 2018/dsa-4187.wml 2018-05-02 00:38:15.000284498 +0500
@@ -1,267 +1,268 @@
- -<define-tag description>security update</define-tag>
+#use wml::debian::translation-check translation="1.1" mindelta="1"
+<define-tag description>обновление безопаÑ?ноÑ?Ñ?и</define-tag>
<define-tag moreinfo>
- -<p>Several vulnerabilities have been discovered in the Linux kernel that
- -may lead to a privilege escalation, denial of service or information
- -leaks.</p>
+<p>Ð? Ñ?дÑ?е Linux бÑ?ло обнаÑ?Ñ?жено неÑ?колÑ?ко Ñ?Ñ?звимоÑ?Ñ?ей, коÑ?оÑ?Ñ?е
+могÑ?Ñ? пÑ?иводиÑ?Ñ? к повÑ?Ñ?ениÑ? пÑ?ивилегий, оÑ?казÑ? в обÑ?лÑ?живании или
+Ñ?Ñ?еÑ?кам инÑ?оÑ?маÑ?ии.</p>
<ul>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2015-9016">CVE-2015-9016</a>
- - <p>Ming Lei reported a race condition in the multiqueue block layer
- - (blk-mq). On a system with a driver using blk-mq (mtip32xx,
- - null_blk, or virtio_blk), a local user might be able to use this
- - for denial of service or possibly for privilege escalation.</p></li>
+ <p>Ð?ин Ð?Ñ?й Ñ?ообÑ?ил о Ñ?оÑ?Ñ?оÑ?нии гонки в планиÑ?овÑ?ике Ñ? неÑ?колÑ?кими оÑ?еÑ?едÑ?ми длÑ? блоÑ?ного
+ Ñ?Ñ?овнÑ? (blk-mq). Ð? Ñ?иÑ?Ñ?еме Ñ? дÑ?айвеÑ?ом, иÑ?полÑ?зÑ?Ñ?Ñ?ем blk-mq (mtip32xx,
+ null_blk или virtio_blk) локалÑ?нÑ?й полÑ?зоваÑ?елÑ? можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ?
+ длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании или возможного повÑ?Ñ?ениÑ? пÑ?ивилегий.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-0861">CVE-2017-0861</a>
- - <p>Robb Glasser reported a potential use-after-free in the ALSA (sound)
- - PCM core. We believe this was not possible in practice.</p></li>
+ <p>Роб Ð?лаÑ?Ñ?еÑ? Ñ?ообÑ?ил о поÑ?енÑ?иалÑ?ном иÑ?полÑ?зовании Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ?
+ памÑ?Ñ?и в Ñ?дÑ?е PCM ALSA (sound). СÑ?иÑ?аеÑ?Ñ?Ñ?, Ñ?Ñ?о на пÑ?акÑ?ике Ñ?акое невозможно.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-5715">CVE-2017-5715</a>
- - <p>Multiple researchers have discovered a vulnerability in various
- - processors supporting speculative execution, enabling an attacker
- - controlling an unprivileged process to read memory from arbitrary
- - addresses, including from the kernel and all other processes
- - running on the system.</p>
- -
- - <p>This specific attack has been named Spectre variant 2 (branch
- - target injection) and is mitigated for the x86 architecture (amd64
- - and i386) by using the <q>retpoline</q> compiler feature which allows
- - indirect branches to be isolated from speculative execution.</p></li>
+ <p>Ð?еÑ?колÑ?ко иÑ?Ñ?ледоваÑ?елей обнаÑ?Ñ?жили Ñ?Ñ?звимоÑ?Ñ?Ñ? в Ñ?азлиÑ?нÑ?Ñ? пÑ?оÑ?еÑ?Ñ?оÑ?аÑ?,
+ поддеÑ?живаÑ?Ñ?иÑ? Ñ?пекÑ?лÑ?Ñ?ивное вÑ?полнение кода, коÑ?оÑ?аÑ? позволÑ?еÑ? злоÑ?мÑ?Ñ?ленникÑ?,
+ Ñ?пÑ?авлÑ?Ñ?Ñ?емÑ? непÑ?ивелигиÑ?ованнÑ?м пÑ?оÑ?еÑ?Ñ?ом, Ñ?Ñ?иÑ?Ñ?ваÑ?Ñ? Ñ?одеÑ?жимое памÑ?Ñ?и по пÑ?оизволÑ?номÑ?
+ адÑ?еÑ?Ñ?, вклÑ?Ñ?аÑ? памÑ?Ñ?Ñ? Ñ?дÑ?а и вÑ?еÑ? оÑ?Ñ?алÑ?нÑ?Ñ? пÑ?оÑ?еÑ?Ñ?ов, запÑ?Ñ?еннÑ?Ñ?
+ в Ñ?иÑ?Ñ?еме.</p>
+
+ <p>Ð?аннаÑ? аÑ?ака полÑ?Ñ?ила название Spectre ваÑ?ианÑ? 2 (введение веÑ?влений),
+ а еÑ? оÑ?Ñ?иÑ?аÑ?елÑ?нÑ?е поÑ?ледÑ?Ñ?виÑ? бÑ?ли минимизиÑ?ованÑ? длÑ? аÑ?Ñ?иÑ?екÑ?Ñ?Ñ?Ñ? x86 (amd64 и i386)
+ пÑ?Ñ?Ñ?м иÑ?полÑ?зованиÑ? возможноÑ?Ñ?и компилÑ?Ñ?оÑ?а <q>retpoline</q>, позволÑ?Ñ?Ñ?ей изолиÑ?оваÑ?Ñ?
+ непÑ?Ñ?мое веÑ?вление оÑ? Ñ?пекÑ?лÑ?Ñ?ивного вÑ?полнениÑ? команд.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-5753">CVE-2017-5753</a>
- - <p>Multiple researchers have discovered a vulnerability in various
- - processors supporting speculative execution, enabling an attacker
- - controlling an unprivileged process to read memory from arbitrary
- - addresses, including from the kernel and all other processes
- - running on the system.</p>
- -
- - <p>This specific attack has been named Spectre variant 1
- - (bounds-check bypass) and is mitigated by identifying vulnerable
- - code sections (array bounds checking followed by array access) and
- - replacing the array access with the speculation-safe
- - array_index_nospec() function.</p>
+ <p>Ð?еÑ?колÑ?ко иÑ?Ñ?ледоваÑ?елей обнаÑ?Ñ?жили Ñ?Ñ?звимоÑ?Ñ?Ñ? в Ñ?азлиÑ?нÑ?Ñ? пÑ?оÑ?еÑ?Ñ?оÑ?аÑ?,
+ поддеÑ?живаÑ?Ñ?иÑ? Ñ?пекÑ?лÑ?Ñ?ивное вÑ?полнение кода, коÑ?оÑ?аÑ? позволÑ?еÑ? злоÑ?мÑ?Ñ?ленникÑ?,
+ Ñ?пÑ?авлÑ?Ñ?Ñ?емÑ? непÑ?ивелигиÑ?ованнÑ?м пÑ?оÑ?еÑ?Ñ?ом, Ñ?Ñ?иÑ?Ñ?ваÑ?Ñ? Ñ?одеÑ?жимое памÑ?Ñ?и по пÑ?оизволÑ?номÑ?
+ адÑ?еÑ?Ñ?, вклÑ?Ñ?аÑ? памÑ?Ñ?Ñ? Ñ?дÑ?а и вÑ?еÑ? оÑ?Ñ?алÑ?нÑ?Ñ? пÑ?оÑ?еÑ?Ñ?ов, запÑ?Ñ?еннÑ?Ñ?
+ в Ñ?иÑ?Ñ?еме.</p>
+
+ <p>Ð?аннаÑ? аÑ?ака полÑ?Ñ?ила название Spectre ваÑ?ианÑ? 1 (обÑ?од пÑ?овеÑ?ки гÑ?аниÑ? бÑ?Ñ?еÑ?а),
+ а еÑ? оÑ?Ñ?иÑ?аÑ?елÑ?нÑ?е поÑ?ледÑ?Ñ?виÑ? бÑ?ли минимизиÑ?ованÑ? пÑ?Ñ?Ñ?м опÑ?еделениÑ? Ñ?Ñ?звимÑ?Ñ? Ñ?азделов
+ кода (пÑ?овеÑ?ка гÑ?аниÑ? маÑ?Ñ?ива поÑ?ле обÑ?аÑ?ениÑ? к маÑ?Ñ?ивÑ?) и заменÑ? обÑ?аÑ?ениÑ? к маÑ?Ñ?ивÑ?
+ на безопаÑ?нÑ?Ñ? пÑ?и иÑ?полÑ?зовании Ñ?пекÑ?лÑ?Ñ?ивного вÑ?полнениÑ?
+ Ñ?Ñ?нкÑ?иÑ? array_index_nospec().
- - <p>More use sites will be added over time.</p></li>
+ <p>Со вÑ?еменем бÑ?дÑ?Ñ? добавленÑ? дополниÑ?елÑ?нÑ?е меÑ?Ñ?а в коде.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-13166">CVE-2017-13166</a>
- - <p>A bug in the 32-bit compatibility layer of the v4l2 ioctl handling
- - code has been found. Memory protections ensuring user-provided
- - buffers always point to userland memory were disabled, allowing
- - destination addresses to be in kernel space. On a 64-bit kernel a
- - local user with access to a suitable video device can exploit this
- - to overwrite kernel memory, leading to privilege escalation.</p></li>
+ <p>Ð?Ñ?ла обнаÑ?Ñ?жен оÑ?ибка в пÑ?оÑ?лойке 32-биÑ?ной Ñ?овмеÑ?Ñ?имоÑ?Ñ?и длÑ? обÑ?абаÑ?Ñ?ваÑ?Ñ?его кода
+ v4l2 ioctl. Ð?еÑ?анизмÑ? заÑ?иÑ?Ñ? Ñ?одеÑ?жимого памÑ?Ñ?и, гаÑ?анÑ?иÑ?Ñ?Ñ?Ñ?ее, Ñ?Ñ?о полÑ?зоваÑ?елÑ?Ñ?кие
+ бÑ?Ñ?еÑ?Ñ? памÑ?Ñ?и вÑ?егда Ñ?казÑ?ваÑ?Ñ? на памÑ?Ñ?Ñ? пÑ?оÑ?Ñ?Ñ?анÑ?Ñ?ва полÑ?зоваÑ?елÑ?, бÑ?ли оÑ?клÑ?Ñ?енÑ?, Ñ?Ñ?о
+ позволÑ?еÑ? Ñ?елевÑ?м адÑ?еÑ?ам Ñ?аÑ?полагаÑ?Ñ?Ñ?Ñ? в пÑ?оÑ?Ñ?Ñ?анÑ?Ñ?ве Ñ?дÑ?а. Ð?а 64-биÑ?нÑ?Ñ? Ñ?дÑ?аÑ?
+ локалÑ?нÑ?й полÑ?зоваÑ?елÑ?, имеÑ?Ñ?ий доÑ?Ñ?Ñ?п к подÑ?одÑ?Ñ?емÑ? видеоÑ?Ñ?Ñ?Ñ?ойÑ?Ñ?вÑ?, можеÑ? иÑ?полÑ?зоваÑ?Ñ?
+ даннÑ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? пеÑ?езапиÑ?и памÑ?Ñ?и Ñ?дÑ?а, Ñ?Ñ?о пÑ?иводиÑ? к повÑ?Ñ?ениÑ? пÑ?ивилегий.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-13220">CVE-2017-13220</a>
- - <p>Al Viro reported that the Bluetooth HIDP implementation could
- - dereference a pointer before performing the necessary type check.
- - A local user could use this to cause a denial of service.</p></li>
+ <p>Ðл Ð?иÑ?о Ñ?ообÑ?ил, Ñ?Ñ?о Ñ?еализаÑ?иÑ? Bluetooth HIDP можеÑ? вÑ?полнÑ?Ñ?Ñ? Ñ?азÑ?менование
+ Ñ?казаÑ?елÑ? до вÑ?полнениÑ? необÑ?одимой пÑ?овеÑ?ки Ñ?ипа. Ð?окалÑ?нÑ?й полÑ?зоваÑ?елÑ?
+ можеÑ? иÑ?полÑ?зоваÑ?Ñ? даннÑ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-16526">CVE-2017-16526</a>
- - <p>Andrey Konovalov reported that the UWB subsystem may dereference
- - an invalid pointer in an error case. A local user might be able
- - to use this for denial of service.</p></li>
+ <p>Ð?ндÑ?ей Ð?оновалов Ñ?ообÑ?ил, Ñ?Ñ?о подÑ?иÑ?Ñ?ема UWB в Ñ?лÑ?Ñ?ае оÑ?ибки можеÑ? вÑ?полнÑ?Ñ?Ñ?
+ Ñ?азÑ?менование некоÑ?Ñ?екÑ?ного Ñ?казаÑ?елÑ?. Ð?окалÑ?нÑ?й полÑ?зоваÑ?елÑ? можеÑ? иÑ?полÑ?зоваÑ?Ñ?
+ Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-16911">CVE-2017-16911</a>
- - <p>Secunia Research reported that the USB/IP vhci_hcd driver exposed
- - kernel heap addresses to local users. This information could aid the
- - exploitation of other vulnerabilities.</p></li>
+ <p>СоÑ?Ñ?Ñ?дники Secunia Research Ñ?ообÑ?или, Ñ?Ñ?о дÑ?айвеÑ? USB/IP vhci_hcd Ñ?аÑ?кÑ?Ñ?ваеÑ?
+ адÑ?еÑ?а динамиÑ?еÑ?кой памÑ?Ñ?и Ñ?дÑ?а локалÑ?нÑ?м полÑ?зоваÑ?елÑ?м. ÐÑ?а инÑ?оÑ?маÑ?иÑ? можеÑ? помоÑ?Ñ?
+ в иÑ?полÑ?зование дÑ?Ñ?гиÑ? Ñ?Ñ?звимоÑ?Ñ?ей.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-16912">CVE-2017-16912</a>
- - <p>Secunia Research reported that the USB/IP stub driver failed to
- - perform a range check on a received packet header field, leading
- - to an out-of-bounds read. A remote user able to connect to the
- - USB/IP server could use this for denial of service.</p></li>
+ <p>СоÑ?Ñ?Ñ?дники Secunia Research Ñ?ообÑ?или, Ñ?Ñ?о дÑ?айвеÑ? USB/IP stub не вÑ?полнÑ?еÑ? пÑ?овеÑ?кÑ?
+ гÑ?аниÑ? маÑ?Ñ?ива пÑ?и полÑ?Ñ?ении полÑ? Ñ? заголовком пакеÑ?а, Ñ?Ñ?о пÑ?иводиÑ? к Ñ?Ñ?ениÑ? за
+ пÑ?еделами вÑ?деленного бÑ?Ñ?еÑ?а памÑ?Ñ?и. УдалÑ?ннÑ?й полÑ?зоваÑ?елÑ?, Ñ?поÑ?обнÑ?й подклÑ?Ñ?иÑ?Ñ?Ñ?Ñ? к
+ Ñ?еÑ?веÑ?Ñ? USB/IP, можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-16913">CVE-2017-16913</a>
- - <p>Secunia Research reported that the USB/IP stub driver failed to
- - perform a range check on a received packet header field, leading
- - to excessive memory allocation. A remote user able to connect to
- - the USB/IP server could use this for denial of service.</p></li>
+ <p>СоÑ?Ñ?Ñ?дники Secunia Research Ñ?ообÑ?или, Ñ?Ñ?о дÑ?айвеÑ? USB/IP stub не вÑ?полнÑ?еÑ? пÑ?овеÑ?кÑ?
+ гÑ?аниÑ? маÑ?Ñ?ива пÑ?и полÑ?Ñ?ении полÑ? Ñ? заголовком пакеÑ?а, Ñ?Ñ?о пÑ?иводиÑ? к вÑ?делениÑ?
+ Ñ?Ñ?езмеÑ?ного обÑ?Ñ?ма памÑ?Ñ?и. УдалÑ?ннÑ?й полÑ?зоваÑ?елÑ?, Ñ?поÑ?обнÑ?й подклÑ?Ñ?иÑ?Ñ?Ñ?Ñ? к
+ Ñ?еÑ?веÑ?Ñ? USB/IP, можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-16914">CVE-2017-16914</a>
- - <p>Secunia Research reported that the USB/IP stub driver failed to
- - check for an invalid combination of fields in a received packet,
- - leading to a null pointer dereference. A remote user able to
- - connect to the USB/IP server could use this for denial of service.</p></li>
+ <p>СоÑ?Ñ?Ñ?дники Secunia Research Ñ?ообÑ?или, Ñ?Ñ?о дÑ?айвеÑ? USB/IP stub не вÑ?полнÑ?еÑ? пÑ?овеÑ?кÑ?
+ некоÑ?Ñ?екÑ?нÑ?Ñ? комбинаÑ?ий полей в полÑ?Ñ?енном пакеÑ?е, Ñ?Ñ?о пÑ?иводиÑ? к Ñ?азÑ?менованиÑ?
+ null-Ñ?казаÑ?елÑ?. УдалÑ?ннÑ?й полÑ?зоваÑ?елÑ?, Ñ?поÑ?обнÑ?й подклÑ?Ñ?иÑ?Ñ?Ñ?Ñ? к
+ Ñ?еÑ?веÑ?Ñ? USB/IP, можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-18017">CVE-2017-18017</a>
- - <p>Denys Fedoryshchenko reported that the netfilter xt_TCPMSS module
- - failed to validate TCP header lengths, potentially leading to a
- - use-after-free. If this module is loaded, it could be used by a
- - remote attacker for denial of service or possibly for code
- - execution.</p></li>
+ <p>Ð?ениÑ? ФедоÑ?иÑ?енко Ñ?ообÑ?ил, Ñ?Ñ?о модÑ?лÑ? netfilter xt_TCPMSS не вÑ?полнÑ?еÑ?
+ пÑ?овеÑ?кÑ? длинÑ? заголовка TCP, Ñ?Ñ?о поÑ?енÑ?иалÑ?но пÑ?иводиÑ? к иÑ?полÑ?зованиÑ?
+ Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и. Ð?Ñ?ли Ñ?казаннÑ?й модÑ?лÑ? загÑ?Ñ?жен, Ñ?о Ñ?Ñ?а Ñ?Ñ?звимоÑ?Ñ?Ñ?
+ можеÑ? иÑ?полÑ?зоваÑ?Ñ?Ñ?Ñ? Ñ?далÑ?ннÑ?м злоÑ?мÑ?Ñ?ленником длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании
+ или возможного вÑ?полнениÑ? кода.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-18203">CVE-2017-18203</a>
- - <p>Hou Tao reported that there was a race condition in creation and
- - deletion of device-mapper (DM) devices. A local user could
- - potentially use this for denial of service.</p></li>
+ <p>Хой Тао Ñ?ообÑ?ил, Ñ?Ñ?о пÑ?и Ñ?оздании и Ñ?далении Ñ?Ñ?Ñ?Ñ?ойÑ?Ñ?в device-mapper (DM)
+ возникаеÑ? Ñ?оÑ?Ñ?оÑ?ние гонки. Ð?окалÑ?нÑ?й полÑ?зоваÑ?елÑ? поÑ?енÑ?иалÑ?но можеÑ?
+ иÑ?полÑ?зоваÑ?Ñ? даннÑ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-18216">CVE-2017-18216</a>
- - <p>Alex Chen reported that the OCFS2 filesystem failed to hold a
- - necessary lock during nodemanager sysfs file operations,
- - potentially leading to a null pointer dereference. A local user
- - could use this for denial of service.</p></li>
+ <p>Ð?лекÑ? Чен Ñ?ообÑ?ил, Ñ?Ñ?о Ñ?айловаÑ? Ñ?иÑ?Ñ?ема OCFS2 не вÑ?полнÑ?еÑ? необÑ?одимÑ?Ñ? блокиÑ?овкÑ?
+ во вÑ?емÑ? Ñ?айловÑ?Ñ? опеÑ?аÑ?ий nodemanager sysfs,
+ Ñ?Ñ?о поÑ?енÑ?иалÑ?но пÑ?иводиÑ? к Ñ?азÑ?менованиÑ? null-Ñ?казаÑ?елÑ?. Ð?окалÑ?нÑ?й полÑ?зоваÑ?елÑ?
+ можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? пÑ?облемÑ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-18232">CVE-2017-18232</a>
- - <p>Jason Yan reported a race condition in the SAS (Serial-Attached
- - SCSI) subsystem, between probing and destroying a port. This
- - could lead to a deadlock. A physically present attacker could
- - use this to cause a denial of service.</p></li>
+ <p>Ð?жейÑ?он Ян Ñ?ообÑ?ил о Ñ?оÑ?Ñ?оÑ?нии гонки в подÑ?иÑ?Ñ?еме SAS (Serial-Attached
+ SCSI) междÑ? обнаÑ?Ñ?жением и Ñ?далением поÑ?Ñ?а. ÐÑ?а пÑ?облема можеÑ? пÑ?иводиÑ?Ñ?
+ к завиÑ?аниÑ?. Ð?лоÑ?мÑ?Ñ?ленник, имеÑ?Ñ?ий Ñ?изиÑ?еÑ?кий доÑ?Ñ?Ñ?п к маÑ?ине, можеÑ?
+ иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2017-18241">CVE-2017-18241</a>
- - <p>Yunlei He reported that the f2fs implementation does not properly
- - initialise its state if the <q>noflush_merge</q> mount option is used.
- - A local user with access to a filesystem mounted with this option
- - could use this to cause a denial of service.</p></li>
+ <p>ЮнÑ?лÑ?й Ð¥Ñ? Ñ?ообÑ?ил, Ñ?Ñ?о Ñ?еализаÑ?иÑ? f2fs непÑ?авилÑ?но иниÑ?иализиÑ?Ñ?еÑ?
+ Ñ?воÑ? Ñ?оÑ?Ñ?оÑ?ние пÑ?и иÑ?полÑ?зовании опÑ?ии монÑ?иÑ?ованиÑ? <q>noflush_merge</q>.
+ Ð?окалÑ?нÑ?й полÑ?зоваÑ?елÑ?, имеÑ?Ñ?ий доÑ?Ñ?Ñ?п к Ñ?айловой Ñ?иÑ?Ñ?еме, Ñ?монÑ?иÑ?ованной Ñ? Ñ?казанной
+ опÑ?ией, можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-1066">CVE-2018-1066</a>
- - <p>Dan Aloni reported to Red Hat that the CIFS client implementation
- - would dereference a null pointer if the server sent an invalid
- - response during NTLMSSP setup negotiation. This could be used
- - by a malicious server for denial of service.</p></li>
+ <p>Ð?Ñ?н Ð?лони Ñ?ообÑ?ил Red Hat, Ñ?Ñ?о Ñ?еализаÑ?иÑ? клиенÑ?а CIFS вÑ?полнÑ?еÑ?
+ Ñ?азÑ?менование null-Ñ?казаÑ?елÑ? в Ñ?лÑ?Ñ?ае, еÑ?ли Ñ?еÑ?веÑ? оÑ?пÑ?авлÑ?еÑ? некоÑ?Ñ?екÑ?нÑ?й
+ оÑ?веÑ? в Ñ?оде Ñ?оглаÑ?ованиÑ? NTLMSSP. ÐÑ?а Ñ?Ñ?звимоÑ?Ñ?Ñ? можеÑ? иÑ?полÑ?зоваÑ?Ñ?Ñ?Ñ?
+ вÑ?едоноÑ?нÑ?м Ñ?еÑ?веÑ?ом длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-1068">CVE-2018-1068</a>
- - <p>The syzkaller tool found that the 32-bit compatibility layer of
- - ebtables did not sufficiently validate offset values. On a 64-bit
- - kernel, a local user with the CAP_NET_ADMIN capability (in any user
- - namespace) could use this to overwrite kernel memory, possibly
- - leading to privilege escalation. Debian disables unprivileged user
- - namespaces by default.</p></li>
+ <p>С помоÑ?Ñ?Ñ? инÑ?Ñ?Ñ?Ñ?менÑ?а syzkaller бÑ?ло обнаÑ?Ñ?жено, Ñ?Ñ?о пÑ?оÑ?лойка 32-биÑ?ной Ñ?овмеÑ?Ñ?имоÑ?Ñ?и
+ ebtables недоÑ?Ñ?аÑ?оÑ?но пÑ?овеÑ?Ñ?еÑ? знаÑ?ениÑ? оÑ?Ñ?Ñ?Ñ?пов. Ð?а 64-биÑ?нÑ?Ñ? Ñ?дÑ?аÑ?
+ локалÑ?нÑ?й полÑ?зоваÑ?елÑ?, имеÑ?Ñ?ий пÑ?ава CAP_NET_ADMIN (в лÑ?бом пÑ?оÑ?Ñ?Ñ?анÑ?Ñ?ве имÑ?н
+ полÑ?зоваÑ?елÑ?), можеÑ? иÑ?полÑ?зоваÑ?Ñ? даннÑ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? пеÑ?езапиÑ?и памÑ?Ñ?и Ñ?дÑ?а, Ñ?Ñ?о
+ поÑ?енÑ?иалÑ?но пÑ?иводиÑ? к повÑ?Ñ?ениÑ? пÑ?ивилегий. Ð? Debian непÑ?ивилегиÑ?ованнÑ?е полÑ?зоваÑ?елÑ?Ñ?кие
+ пÑ?оÑ?Ñ?Ñ?анÑ?Ñ?ва имÑ?н по Ñ?молÑ?аниÑ? оÑ?клÑ?Ñ?енÑ?.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-1092">CVE-2018-1092</a>
- - <p>Wen Xu reported that a crafted ext4 filesystem image would
- - trigger a null dereference when mounted. A local user able
- - to mount arbitrary filesystems could use this for denial of
- - service.</p></li>
+ <p>Ð?Ñ?нÑ? СÑ?й Ñ?ообÑ?ил, Ñ?Ñ?о Ñ?пеÑ?иалÑ?но Ñ?Ñ?оÑ?миÑ?ованнÑ?й обÑ?аз Ñ?айловой Ñ?иÑ?Ñ?емÑ? ext4
+ пÑ?и его монÑ?иÑ?овании вÑ?зÑ?ваеÑ? Ñ?азÑ?менование null-Ñ?казаÑ?елÑ?. Ð?окалÑ?нÑ?й полÑ?зоваÑ?елÑ?,
+ Ñ?поÑ?обнÑ?й монÑ?иÑ?оваÑ?Ñ? пÑ?оизволÑ?нÑ?е Ñ?айловÑ?е Ñ?иÑ?Ñ?емÑ?, можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ?
+ длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-5332">CVE-2018-5332</a>
- - <p>Mohamed Ghannam reported that the RDS protocol did not
- - sufficiently validate RDMA requests, leading to an out-of-bounds
- - write. A local attacker on a system with the rds module loaded
- - could use this for denial of service or possibly for privilege
- - escalation.</p></li>
+ <p>Ð?оÑ?амед Ð?аннам Ñ?ообÑ?ил, Ñ?Ñ?о в пÑ?оÑ?околе RDS недоÑ?Ñ?аÑ?оÑ?но пÑ?овеÑ?Ñ?Ñ?Ñ?Ñ?Ñ?
+ RDMA-запÑ?оÑ?Ñ?, Ñ?Ñ?о пÑ?иводиÑ? к запиÑ?и за пÑ?еделами вÑ?деленного бÑ?Ñ?еÑ?а
+ памÑ?Ñ?и. Ð?окалÑ?нÑ?й злоÑ?мÑ?Ñ?ленник в Ñ?иÑ?Ñ?еме Ñ? загÑ?Ñ?женнÑ?м модÑ?лем rds
+ можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?казаннÑ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании или поÑ?енÑ?иалÑ?ного
+ повÑ?Ñ?ениÑ? пÑ?ивилегий.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-5333">CVE-2018-5333</a>
- - <p>Mohamed Ghannam reported that the RDS protocol did not properly
- - handle an error case, leading to a null pointer dereference. A
- - local attacker on a system with the rds module loaded could
- - possibly use this for denial of service.</p></li>
+ <p>Ð?оÑ?амед Ð?аннам Ñ?ообÑ?ил, Ñ?Ñ?о в пÑ?оÑ?околе RDS непÑ?авилÑ?но обÑ?абаÑ?Ñ?ваÑ?Ñ?Ñ?Ñ?
+ оÑ?ибки, Ñ?Ñ?о пÑ?иводиÑ? к Ñ?азÑ?менованиÑ? null-Ñ?казаÑ?елÑ?. Ð?окалÑ?нÑ?й
+ злоÑ?мÑ?Ñ?ленник в Ñ?иÑ?Ñ?еме Ñ? загÑ?Ñ?женнÑ?м модÑ?лем rds можеÑ? поÑ?енÑ?иалÑ?но
+ иÑ?полÑ?зоваÑ?Ñ? Ñ?казаннÑ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-5750">CVE-2018-5750</a>
- - <p>Wang Qize reported that the ACPI sbshc driver logged a kernel heap
- - address. This information could aid the exploitation of other
- - vulnerabilities.</p></li>
+ <p>Ð?ан Ð?из Ñ?ообÑ?ил, Ñ?Ñ?о дÑ?айвеÑ? ACPI sbshc Ñ?оÑ?Ñ?анÑ?еÑ? в жÑ?Ñ?нал адÑ?еÑ? динамиÑ?еÑ?кой
+ памÑ?Ñ?и Ñ?дÑ?а. ÐÑ?а инÑ?оÑ?маÑ?иÑ? можеÑ? помоÑ?Ñ? в иÑ?полÑ?зовании дÑ?Ñ?гиÑ?
+ Ñ?Ñ?звимоÑ?Ñ?ей.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-5803">CVE-2018-5803</a>
- - <p>Alexey Kodanev reported that the SCTP protocol did not range-check
- - the length of chunks to be created. A local or remote user could
- - use this to cause a denial of service.</p></li>
+ <p>Ð?леÑ?ей Ð?оданев Ñ?ообÑ?ил, Ñ?Ñ?о в пÑ?оÑ?околе SCTP не вÑ?полнÑ?еÑ?Ñ?Ñ? пÑ?овеÑ?ка гÑ?аниÑ? маÑ?Ñ?ива
+ длÑ? длин Ñ?оздаваемÑ?Ñ? поÑ?Ñ?ий даннÑ?Ñ?. Ð?окалÑ?нÑ?й или Ñ?далÑ?ннÑ?й полÑ?зоваÑ?елÑ? могÑ?Ñ?
+ иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6927">CVE-2018-6927</a>
- - <p>Li Jinyue reported that the FUTEX_REQUEUE operation on futexes did
- - not check for negative parameter values, which might lead to a
- - denial of service or other security impact.</p></li>
+ <p>Ð?и ЦзинÑ?Ñ?Ñ? Ñ?ообÑ?ил, Ñ?Ñ?о опеÑ?аÑ?иÑ? FUTEX_REQUEUE на futex не вÑ?полнÑ?еÑ?
+ пÑ?овеÑ?кÑ? оÑ?Ñ?иÑ?аÑ?елÑ?нÑ?Ñ? знаÑ?ений паÑ?амеÑ?Ñ?а, Ñ?Ñ?о можеÑ? пÑ?иводиÑ?Ñ? к
+ оÑ?казÑ? в обÑ?лÑ?живании или оказÑ?ваÑ?Ñ? дÑ?Ñ?гое влиÑ?ние на безопаÑ?ноÑ?Ñ?Ñ? Ñ?иÑ?Ñ?емÑ?.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-7492">CVE-2018-7492</a>
- - <p>The syzkaller tool found that the RDS protocol was lacking a null
- - pointer check. A local attacker on a system with the rds module
- - loaded could use this for denial of service.</p></li>
+ <p>С помоÑ?Ñ?Ñ? инÑ?Ñ?Ñ?Ñ?менÑ?а syzkaller бÑ?ло обнаÑ?Ñ?жено, Ñ?Ñ?о в пÑ?оÑ?околе RDS оÑ?Ñ?Ñ?Ñ?Ñ?Ñ?вÑ?Ñ?Ñ? пÑ?овеÑ?ки
+ null-Ñ?казаÑ?елей. Ð?окалÑ?нÑ?й злоÑ?мÑ?Ñ?ленник в Ñ?иÑ?Ñ?еме Ñ? загÑ?Ñ?женнÑ?м модÑ?лем rds
+ можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-7566">CVE-2018-7566</a>
- - <p>Fan LongFei reported a race condition in the ALSA (sound)
- - sequencer core, between write and ioctl operations. This could
- - lead to an out-of-bounds access or use-after-free. A local user
- - with access to a sequencer device could use this for denial of
- - service or possibly for privilege escalation.</p></li>
+ <p>ФанÑ? Ð?Ñ?нФÑ?й Ñ?ообÑ?ил о Ñ?оÑ?Ñ?оÑ?нии гонки в Ñ?дÑ?е планиÑ?овÑ?ика ALSA (sound)
+ междÑ? опеÑ?аÑ?иÑ?ми запиÑ?и и ioctl. ÐÑ?а Ñ?Ñ?звимоÑ?Ñ?Ñ? можеÑ? пÑ?иводиÑ?Ñ? к
+ обÑ?аÑ?ениÑ? в памÑ?Ñ?и за пÑ?еделами вÑ?деленного бÑ?Ñ?еÑ?а или иÑ?полÑ?зованиÑ? Ñ?казаÑ?елей
+ поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и. Ð?окалÑ?нÑ?й полÑ?зоваÑ?елÑ?, имеÑ?Ñ?ий доÑ?Ñ?Ñ?п к
+ Ñ?Ñ?Ñ?Ñ?ойÑ?Ñ?вÑ? планиÑ?овÑ?ика можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в
+ обÑ?лÑ?живании или возможного повÑ?Ñ?ениÑ? пÑ?ивилегий.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-7740">CVE-2018-7740</a>
- - <p>Nic Losby reported that the hugetlbfs filesystem's mmap operation
- - did not properly range-check the file offset. A local user with
- - access to files on a hugetlbfs filesystem could use this to cause
- - a denial of service.</p></li>
+ <p>Ð?ик Ð?оÑ?Ñ?би Ñ?ообÑ?ил, Ñ?Ñ?о опеÑ?аÑ?иÑ? mmap Ñ?айловой Ñ?иÑ?Ñ?емÑ? hugetlbfs
+ непÑ?авилÑ?но вÑ?полнÑ?еÑ? пÑ?овеÑ?кÑ? гÑ?аниÑ? маÑ?Ñ?ива длÑ? Ñ?айлового оÑ?Ñ?Ñ?Ñ?па. Ð?окалÑ?нÑ?й полÑ?зоваÑ?елÑ?,
+ имеÑ?Ñ?ий доÑ?Ñ?Ñ?п к Ñ?айлам в Ñ?айловой Ñ?иÑ?Ñ?еме hugetlbfs, можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ?
+ длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-7757">CVE-2018-7757</a>
- - <p>Jason Yan reported a memory leak in the SAS (Serial-Attached
- - SCSI) subsystem. A local user on a system with SAS devices
- - could use this to cause a denial of service.</p></li>
+ <p>Ð?жейÑ?он Ян Ñ?ообÑ?ил об Ñ?Ñ?еÑ?ке памÑ?Ñ?и в подÑ?иÑ?Ñ?еме SAS (Serial-Attached
+ SCSI). Ð?окалÑ?нÑ?й полÑ?зоваÑ?елÑ? в Ñ?иÑ?Ñ?еме Ñ? SAS-Ñ?Ñ?Ñ?Ñ?ойÑ?Ñ?вами
+ можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-7995">CVE-2018-7995</a>
- - <p>Seunghun Han reported a race condition in the x86 MCE
- - (Machine Check Exception) driver. This is unlikely to have
- - any security impact.</p></li>
+ <p>СÑ?нÑ?Ñ?нÑ? ХанÑ? Ñ?ообÑ?ил о Ñ?оÑ?Ñ?оÑ?нии гонки в дÑ?айвеÑ?е x86 MCE
+ (Machine Check Exception). ÐÑ?а пÑ?облема Ñ?коÑ?ее вÑ?его не имееÑ?
+ влиÑ?ниÑ? на безопаÑ?ноÑ?Ñ?Ñ? Ñ?иÑ?Ñ?емÑ?.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-8781">CVE-2018-8781</a>
- - <p>Eyal Itkin reported that the udl (DisplayLink) driver's mmap
- - operation did not properly range-check the file offset. A local
- - user with access to a udl framebuffer device could exploit this to
- - overwrite kernel memory, leading to privilege escalation.</p></li>
+ <p>ÐÑ?лÑ? Ð?Ñ?кин Ñ?ообÑ?ил, Ñ?Ñ?о опеÑ?аÑ?иÑ? mmap дÑ?айвеÑ?а udl (DisplayLink)
+ непÑ?авилÑ?но вÑ?полнÑ?еÑ? пÑ?овеÑ?кÑ? гÑ?аниÑ? маÑ?Ñ?ива длÑ? Ñ?айлового оÑ?Ñ?Ñ?Ñ?па. Ð?окалÑ?нÑ?й
+ полÑ?зоваÑ?елÑ?, имеÑ?Ñ?ий доÑ?Ñ?Ñ?п к Ñ?Ñ?Ñ?Ñ?ойÑ?Ñ?вÑ? udl можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ?
+ длÑ? пеÑ?езапиÑ?и памÑ?Ñ?и Ñ?дÑ?а, Ñ?Ñ?о пÑ?иводиÑ? к повÑ?Ñ?ениÑ? пÑ?ивилегий.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-8822">CVE-2018-8822</a>
- - <p>Dr Silvio Cesare of InfoSect reported that the ncpfs client
- - implementation did not validate reply lengths from the server. An
- - ncpfs server could use this to cause a denial of service or
- - remote code execution in the client.</p></li>
+ <p>Ð?-Ñ? СилÑ?вио ЦезаÑ?е из InfoSect Ñ?ообÑ?ил, Ñ?Ñ?о Ñ?еализаÑ?иÑ? клиенÑ?а ncpfs
+ не вÑ?полнÑ?еÑ? пÑ?овеÑ?кÑ? длинÑ? оÑ?веÑ?ов Ñ?еÑ?веÑ?а. СеÑ?веÑ? ncpfs
+ можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании или
+ Ñ?далÑ?нного вÑ?полнениÑ? кода на Ñ?Ñ?оÑ?оне клиенÑ?а.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-1000004">CVE-2018-1000004</a>
- - <p>Luo Quan reported a race condition in the ALSA (sound) sequencer
- - core, between multiple ioctl operations. This could lead to a
- - deadlock or use-after-free. A local user with access to a
- - sequencer device could use this for denial of service or possibly
- - for privilege escalation.</p></li>
+ <p>Ð?о ЦÑ?анÑ? Ñ?ообÑ?ил о Ñ?оÑ?Ñ?оÑ?нии гонки в Ñ?дÑ?е планиÑ?овÑ?ика ALSA (sound)
+ междÑ? неÑ?колÑ?кими опеÑ?аÑ?иÑ?ми ioctl. ÐÑ?а пÑ?облема можеÑ? пÑ?иводиÑ?Ñ? к
+ завиÑ?аниÑ? или иÑ?полÑ?зованиÑ? Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и. Ð?окалÑ?нÑ?й полÑ?зоваÑ?елÑ?, имеÑ?Ñ?ий
+ доÑ?Ñ?Ñ?п к планиÑ?овÑ?икÑ?, можеÑ? иÑ?полÑ?зоваÑ?Ñ? Ñ?казаннÑ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова
+ оÑ?каза в обÑ?лÑ?живании или длÑ? возможного повÑ?Ñ?ениÑ? пÑ?ивилегий.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2018-1000199">CVE-2018-1000199</a>
- - <p>Andy Lutomirski discovered that the ptrace subsystem did not
- - sufficiently validate hardware breakpoint settings. Local users
- - can use this to cause a denial of service, or possibly for
- - privilege escalation, on x86 (amd64 and i386) and possibly other
- - architectures.</p></li>
+ <p>Ðнди Ð?Ñ?Ñ?омиÑ?Ñ?кий обнаÑ?Ñ?жил, Ñ?Ñ?о подÑ?иÑ?Ñ?ема ptrace недоÑ?Ñ?аÑ?оÑ?но
+ пÑ?овеÑ?Ñ?еÑ? наÑ?Ñ?Ñ?ойки аппаÑ?аÑ?нÑ?Ñ? Ñ?оÑ?ке оÑ?Ñ?анова. Ð?окалÑ?нÑ?е полÑ?зоваÑ?ели могÑ?Ñ?
+ иÑ?полÑ?зоваÑ?Ñ? Ñ?Ñ?Ñ? Ñ?Ñ?звимоÑ?Ñ?Ñ? длÑ? вÑ?зова оÑ?каза в обÑ?лÑ?живании или возможного
+ повÑ?Ñ?ениÑ? пÑ?ивилегий на аÑ?Ñ?иÑ?екÑ?Ñ?Ñ?е x86 (amd64 и i386), а Ñ?акже поÑ?енÑ?иалÑ?но и на
+ дÑ?Ñ?гиÑ? аÑ?Ñ?иÑ?екÑ?Ñ?Ñ?аÑ?.</p></li>
</ul>
- -<p>For the oldstable distribution (jessie), these problems have been fixed
- -in version 3.16.56-1.</p>
+<p>Ð? пÑ?едÑ?дÑ?Ñ?ем Ñ?Ñ?абилÑ?ном вÑ?пÑ?Ñ?ке (jessie) Ñ?Ñ?и пÑ?облемÑ? бÑ?ли иÑ?пÑ?авленÑ?
+в веÑ?Ñ?ии 3.16.56-1.</p>
- -<p>We recommend that you upgrade your linux packages.</p>
+<p>РекомендÑ?еÑ?Ñ?Ñ? обновиÑ?Ñ? пакеÑ?Ñ? linux.</p>
- -<p>For the detailed security status of linux please refer to its security
- -tracker page at:
+<p>С подÑ?обнÑ?м Ñ?Ñ?аÑ?Ñ?Ñ?ом поддеÑ?жки безопаÑ?ноÑ?Ñ?и linux можно ознакомиÑ?Ñ?Ñ?Ñ? на
+Ñ?ооÑ?веÑ?Ñ?Ñ?вÑ?Ñ?Ñ?ей Ñ?Ñ?Ñ?аниÑ?е оÑ?Ñ?леживаниÑ? безопаÑ?ноÑ?Ñ?и по адÑ?еÑ?Ñ?
<a href="https://security-tracker.debian.org/tracker/linux">\
https://security-tracker.debian.org/tracker/linux</a></p>
</define-tag>
# do not modify the following line
#include "$(ENGLISHDIR)/security/2018/dsa-4187.data"
- -# $Id: dsa-4187.wml,v 1.1 2018/05/01 18:12:56 dogsleg Exp $
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE3mumcdV9mwCc9oZQXudu4gIW0qUFAlrowlAACgkQXudu4gIW
0qWfVg//XDe1fY3PJKY+xSomqm7LVnXTFPPpMNq4ZMInQfCcgJxQEQFH/SY/M9f7
9vBflTPl80VCYAYxuZShP4qQI12gix1MYsyaOtShrCDmphDfLvG+PNhXCIIXU6vX
J5Ax2L9inuFuHQc3xTvd1pFjjmM0Gh61wBh06SP8/jkt8pXc9+2aNhZ91VAU1XQq
Slv9dsn58UA3KT83DDLFEz/N2kNASYYFhF9ecDWTqS1U6hszbqt5vezMg3JU3gm4
pgewnzIuLROJhm3hfQJhA9qTnmqQjjunWKWatvgaE9sv8nAHbbSefpCWwrn+5Eta
HJddLILIR0shwqQSqQ0Bep3BULLanggZKLmMgPXMFHHZ2xMdmaIZP13W0R0YRKbv
jWOOda24ENGNttKA2yy3WBB96aTLkwY1AzGuCx6Qf6jsFtOUT7+uwMhju9wl58FS
T9fildaG0q1iVvhjkQ+OgE/C9Oej6fXzX1tPP/WXgI75SYmgEG8Q81XGSembSp/m
C8V1yEA2IkJ9B7d5AEg+xtHHku2GxpiyaVmiuhuZWgpnYDHxMjNJfQ8xDmdB5fYn
y9/j0WakgJZfc7ojjoh0hqDoNBZN+YFB/v87yT+4WPnf7jM5j7RTtq3+/u0NZqj3
RlP/c4xqUnmck9Rww/3XpuAd3p4PUMbS44wdIQUDTYDbZfdctJg=
=uEv9
-----END PGP SIGNATURE-----
Reply to: