From: Kleber Sacilotto de Souza <kleber.souza@canonical.com>
To: dccp@vger.kernel.org
Subject: [PATCH 0/2] net: dccp: fix structure use-after-free
Date: Tue, 13 Oct 2020 17:18:47 +0000 [thread overview]
Message-ID: <20201013171849.236025-1-kleber.souza@canonical.com> (raw)
This patchset addresses the following CVE:
CVE-2020-16119 - DCCP CCID structure use-after-free
Hadar Manor reported that by reusing a socket with an attached
dccps_hc_tx_ccid as a listener, it will be used after being released,
leading to DoS and potentially code execution.
The first patch moves the ccid timers to struct dccp_sock to avoid its
use-after-free, the second patch reverts 2677d2067731 "dccp: don't free
ccid2_hc_tx_sock struct in dccp_disconnect()" that's not needed anymore
and would cause another use-after-free.
Thadeu Lima de Souza Cascardo (2):
dccp: ccid: move timers to struct dccp_sock
Revert "dccp: don't free ccid2_hc_tx_sock struct in dccp_disconnect()"
include/linux/dccp.h | 2 ++
net/dccp/ccids/ccid2.c | 32 +++++++++++++++++++-------------
net/dccp/ccids/ccid3.c | 30 ++++++++++++++++++++----------
net/dccp/proto.c | 2 ++
4 files changed, 43 insertions(+), 23 deletions(-)
--
2.25.1
reply other threads:[~2020-10-13 17:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201013171849.236025-1-kleber.souza@canonical.com \
--to=kleber.souza@canonical.com \
--cc=dccp@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).