Close speculative mem read possibility
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest1 patch 1 replyIn review
Changelog from the cover letter
v1: initial version
v2: Rephrased patch header text, added Finn's Reviewed-by, no code changes.
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | s390/zcrypt: Close speculative mem read possibilitydrivers/ | +2 | 1 reply |
Reviews trailers per patch
The patch has a Reviewed-by or Acked-by.
| Patch | Finn Callies |
|---|---|
| 1/1 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v2 0/1] Close speculative mem read possibility
The domain value is extracted from a given CCA or EP11 ioctl struct when a CPRB is about to be sent. Thus this is a user controlled value. Under some special conditions (custom device node used, administrative load) this value is used as an array index after bounds checking, but without speculation barrier.
Add the missing array_index_nospec() call to prevent speculative execution where this domain value is used.
Changelog:
v1: initial version
v2: Rephrased patch header text, added Finn's Reviewed-by, no code changes.
Harald Freudenberger (1):
s390/zcrypt: Close speculative mem read possibility
drivers/s390/crypto/zcrypt_api.c | 2 ++ 1 file changed, 2 insertions(+)
Signature · 1 line
2.43.0