diff options
author | Lalithambika Krishnakumar <lalithambika.krishnakumar@intel.com> | 2020-12-23 14:09:00 -0800 |
---|---|---|
committer | Christoph Hellwig <hch@lst.de> | 2021-01-06 10:30:37 +0100 |
commit | 62df80165d7f197c9c0652e7416164f294a96661 (patch) | |
tree | 9d613daac28ccc1da9bcfc7e581293b7a9c3c3c5 /mm | |
parent | 5c11f7d9f843bdd24cd29b95401938bc3f168070 (diff) |
nvme: avoid possible double fetch in handling CQE
While handling the completion queue, keep a local copy of the command id
from the DMA-accessible completion entry. This silences a time-of-check
to time-of-use (TOCTOU) warning from KF/x[1], with respect to a
Thunderclap[2] vulnerability analysis. The double-read impact appears
benign.
There may be a theoretical window for @command_id to be used as an
adversary-controlled array-index-value for mounting a speculative
execution attack, but that mitigation is saved for a potential follow-on.
A man-in-the-middle attack on the data payload is out of scope for this
analysis and is hopefully mitigated by filesystem integrity mechanisms.
[1] https://github.com/intel/kernel-fuzzer-for-xen-project
[2] http://thunderclap.io/thunderclap-paper-ndss2019.pdf
Signed-off-by: Lalithambika Krishna Kumar <lalithambika.krishnakumar@intel.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions