From: Siddharth Chandrasekaran <csiddharth@vmware.com>
To: gregkh@linuxfoundation.org
Cc: srostedt@vmware.com, stable@vger.kernel.org,
srivatsab@vmware.com, csiddharth@vmware.com,
siddharth@embedjournal.com, dchinner@redhat.com,
darrick.wong@oracle.com, srivatsa@csail.mit.edu
Subject: [PATCH v2] Backport xfs security fix to 4.9 and 4.4 stable trees
Date: Fri, 15 May 2020 20:41:07 +0530 [thread overview]
Message-ID: <cover.1589544531.git.csiddharth@vmware.com> (raw)
Hello,
Lack of proper validation that cached inodes are free during allocation can,
cause a crash in fs/xfs/xfs_icache.c (refer: CVE-2018-13093). To address this
issue, I'm backporting upstream commit [1] to 4.4 and 4.9 stable trees
(a backport of [1] to 4.14 already exists).
Also, commit [1] references another commit [2] which added checks only to
xfs_iget_cache_miss(). In this patch, those checks have been moved into a
dedicated checker method and both xfs_iget_cache_miss() and
xfs_iget_cache_hit() are made to call that method. This code reorg in commit
[1], makes commit [2] redundant in the history of the 4.9 and 4.4 stable
trees. So commit [2] is not being backported.
-- Sid
[1]: afca6c5b2595 ("xfs: validate cached inodes are free when allocated")
[2]: ee457001ed6c ("xfs: catch inode allocation state mismatch corruption")
change log:
v2:
- Reword cover letter.
- Fix accidental worong patch that got mailed.
--
2.7.4
next reply other threads:[~2020-05-15 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 15:11 Siddharth Chandrasekaran [this message]
2020-05-15 15:11 ` [PATCH 4.4 v2] xfs: validate cached inodes are free when allocated Siddharth Chandrasekaran
2020-05-15 15:11 ` [PATCH 4.9 " Siddharth Chandrasekaran
2020-05-15 15:22 ` [PATCH v2] Backport xfs security fix to 4.9 and 4.4 stable trees Greg KH
2020-05-15 15:58 ` Siddharth Chandrasekaran
2020-05-20 9:18 ` Siddharth Chandrasekaran
2020-06-03 16:46 ` Darrick J. Wong
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=cover.1589544531.git.csiddharth@vmware.com \
--to=csiddharth@vmware.com \
--cc=darrick.wong@oracle.com \
--cc=dchinner@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=siddharth@embedjournal.com \
--cc=srivatsa@csail.mit.edu \
--cc=srivatsab@vmware.com \
--cc=srostedt@vmware.com \
--cc=stable@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 NNTP newsgroup(s).