From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <Alexander.Levin@microsoft.com>
Cc: stable <stable@vger.kernel.org>,
Lorenzo Stoakes <lstoakes@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Willy Tarreau <w@1wt.eu>
Subject: Fix for CVE-2018-1120 in 4.4
Date: Thu, 13 Dec 2018 20:24:24 +0000 [thread overview]
Message-ID: <1544732664.19315.59.camel@codethink.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
I've backported changes to fix CVE-2018-1120 (denial of service via
FUSE-backed /proc/PID/cmdline) in 4.4-stable. See
<https://www.qualys.com/2018/05/17/procps-ng-audit-report-advisory.txt>
for an explanation of the issue.
This was already fixed in newer stable branches, but the fix depended
on API changes made in 4.9. The API changes are fairly straightforward
and should be low risk, so the attached patches include those API
changes.
I verified that the proof-of-concept no longer works after these
changes, and that there were no regressions in the user-copy and vm
self-tests. I leave it to you to decide whether it's worthwhile to fix
this in 4.4.
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
[-- Attachment #2: security-4.4-CVE-2018-1120.mbox --]
[-- Type: application/mbox, Size: 68200 bytes --]
next reply other threads:[~2018-12-13 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 20:24 Ben Hutchings [this message]
2018-12-13 20:39 ` Fix for CVE-2018-1120 in 4.4 Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1544732664.19315.59.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=Alexander.Levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=lstoakes@gmail.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.