Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.security > #5063
| From | Florian Weimer <fw@deneb.enyo.de> |
|---|---|
| Newsgroups | linux.debian.security |
| Subject | Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? |
| Date | 2016-10-18 22:30 +0200 |
| Message-ID | <stJbj-6WG-5@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <srctb-3jq-13@gated-at.bofh.it> <srpgJ-3eb-11@gated-at.bofh.it> <srtu2-6cx-37@gated-at.bofh.it> <srPux-4ML-9@gated-at.bofh.it> <srT57-7eS-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
* Michael Stone: > On Thu, Oct 13, 2016 at 02:45:29PM -0000, te3d4q@sigaint.org wrote: >>As you asked me for a specific case, may I bring up CVE-2016-5696. >> >>A fix to the medium-risk vulnerability was uploaded on July 10, 2016 by >>Eric Dumazet (cf. >>https://github.com/torvalds/linux/commit/75ff39ccc1bd5d3c455b6822ab09e533c551f758) >> >>Ben Hutchings uploaded his work on the fix on August 12, 2016 (cf. >>https://anonscm.debian.org/cgit/kernel/linux.git/log/?h=jessie-security) >> >>Debian officially pushed out the fix on September 4, 2016 via DSA-3659-1. >> >>Are there reasons for the 23-day delay in providing end-users the patch? > > I don't know the specifics of this one but kernel updates are > generally kind of a mess and in this case we're talking about an issue > that basically boils down to a DoS for internet-facing hosts and for > which there existed a mitigation. I'm personally not too concerned > about the timeline. Right. Debian kernel updates can only be applied with a reboot. If we publish a kernel update, its mere availability may put some of our users out of compliance with their policies, which is why we batch these updates.
Back to linux.debian.security | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? te3d4q@sigaint.org - 2016-10-11 17:10 +0200
Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? Moritz Mühlenhoff <jmm@inutil.org> - 2016-10-11 17:30 +0200
Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? te3d4q@sigaint.org - 2016-10-11 22:10 +0200
Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? Moritz Muehlenhoff <jmm@debian.org> - 2016-10-11 23:10 +0200
Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? te3d4q@sigaint.org - 2016-10-12 12:50 +0200
Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? Michael Stone <mstone@debian.org> - 2016-10-12 17:20 +0200
Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? te3d4q@sigaint.org - 2016-10-13 16:50 +0200
Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? Michael Stone <mstone@debian.org> - 2016-10-13 20:40 +0200
Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? Florian Weimer <fw@deneb.enyo.de> - 2016-10-18 22:30 +0200
Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? Henrique de Moraes Holschuh <hmh@debian.org> - 2016-10-19 17:00 +0200
Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? Alexander Schreiber <als@thangorodrim.ch> - 2016-10-20 01:00 +0200
Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? Henrique de Moraes Holschuh <hmh@debian.org> - 2016-10-20 02:40 +0200
Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? Moritz Muehlenhoff <jmm@inutil.org> - 2016-10-12 22:40 +0200
Re: Vulnerabilities rated medium or low risk may not be fixed by Debian security team, is that correct? te3d4q@sigaint.org - 2016-10-13 16:50 +0200
csiph-web