From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15 v2 05/14] Documentation: x86/bugs/its: Add ITS documentation
Date: Wed, 14 May 2025 16:14:29 -0400 [thread overview]
Message-ID: <20250514110833-0cc48f41e2f17b28@stable.kernel.org> (raw)
In-Reply-To: <20250513-its-5-15-v2-5-90690efdc7e0@linux.intel.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 1ac116ce6468670eeda39345a5585df308243dca
Status in newer kernel trees:
6.14.y | Present (different SHA1: d94999d36def)
6.12.y | Present (different SHA1: 13a7b7b4c7a7)
6.6.y | Present (different SHA1: aef0566edca8)
6.1.y | Present (different SHA1: 145182f52b93)
Note: The patch differs from the upstream commit:
---
1: 1ac116ce64686 ! 1: 5fef22b8da7cf Documentation: x86/bugs/its: Add ITS documentation
@@ Metadata
## Commit message ##
Documentation: x86/bugs/its: Add ITS documentation
+ commit 1ac116ce6468670eeda39345a5585df308243dca upstream.
+
Add the admin-guide for Indirect Target Selection (ITS).
Signed-off-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
@@ Commit message
## Documentation/admin-guide/hw-vuln/index.rst ##
@@ Documentation/admin-guide/hw-vuln/index.rst: are configurable at compile, boot or run time.
- gather_data_sampling
+ gather_data_sampling.rst
+ srso
reg-file-data-sampling
- rsb
+ indirect-target-selection
## Documentation/admin-guide/hw-vuln/indirect-target-selection.rst (new) ##
@@ Documentation/admin-guide/hw-vuln/indirect-target-selection.rst (new)
+reason, when retpoline is enabled, ITS mitigation only relocates the RETs to
+safe thunks. Unless user requested the RSB-stuffing mitigation.
+
-+RSB Stuffing
-+~~~~~~~~~~~~
-+RSB-stuffing via Call Depth Tracking is a mitigation for Retbleed RSB-underflow
-+attacks. And it also mitigates RETs that are vulnerable to ITS.
-+
+Mitigation in guests
+^^^^^^^^^^^^^^^^^^^^
+All guests deploy ITS mitigation by default, irrespective of eIBRS enumeration
@@ Documentation/admin-guide/hw-vuln/indirect-target-selection.rst (new)
+ useful when host userspace is not in the threat model, and only
+ attacks from guest to host are considered.
+
-+ stuff Deploy RSB-fill mitigation when retpoline is also deployed.
-+ Otherwise, deploy the default mitigation. When retpoline mitigation
-+ is enabled, RSB-stuffing via Call-Depth-Tracking also mitigates
-+ ITS.
-+
+ force Force the ITS bug and deploy the default mitigation.
+ ======== ===================================================================
+
@@ Documentation/admin-guide/hw-vuln/indirect-target-selection.rst (new)
+ * - Mitigation: Aligned branch/return thunks
+ - The mitigation is enabled, affected indirect branches and RETs are
+ relocated to safe thunks.
-+ * - Mitigation: Retpolines, Stuffing RSB
-+ - The mitigation is enabled using retpoline and RSB stuffing.
+
+References
+----------
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2025-05-14 20:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 6:06 [PATCH 5.15 v2 00/14] ITS mitigation Pawan Gupta
2025-05-14 6:06 ` [PATCH 5.15 v2 01/14] x86,nospec: Simplify {JMP,CALL}_NOSPEC Pawan Gupta
2025-05-14 20:13 ` Sasha Levin
2025-05-14 6:07 ` [PATCH 5.15 v2 02/14] x86/speculation: Simplify and make CALL_NOSPEC consistent Pawan Gupta
2025-05-14 20:14 ` Sasha Levin
2025-05-14 6:07 ` [PATCH 5.15 v2 03/14] x86/speculation: Add a conditional CS prefix to CALL_NOSPEC Pawan Gupta
2025-05-14 20:14 ` Sasha Levin
2025-05-14 6:07 ` [PATCH 5.15 v2 04/14] x86/speculation: Remove the extra #ifdef around CALL_NOSPEC Pawan Gupta
2025-05-14 20:13 ` Sasha Levin
2025-05-14 6:07 ` [PATCH 5.15 v2 05/14] Documentation: x86/bugs/its: Add ITS documentation Pawan Gupta
2025-05-14 20:14 ` Sasha Levin [this message]
2025-05-14 6:08 ` [PATCH 5.15 v2 06/14] x86/its: Enumerate Indirect Target Selection (ITS) bug Pawan Gupta
2025-05-14 20:13 ` Sasha Levin
2025-05-14 6:08 ` [PATCH 5.15 v2 07/14] x86/its: Add support for ITS-safe indirect thunk Pawan Gupta
2025-05-14 20:14 ` Sasha Levin
2025-05-14 6:08 ` [PATCH 5.15 v2 08/14] x86/alternative: Optimize returns patching Pawan Gupta
2025-05-14 20:14 ` Sasha Levin
2025-05-14 6:08 ` [PATCH 5.15 v2 09/14] x86/alternatives: Remove faulty optimization Pawan Gupta
2025-05-14 20:13 ` Sasha Levin
2025-05-14 6:09 ` [PATCH 5.15 v2 10/14] x86/its: Add support for ITS-safe return thunk Pawan Gupta
2025-05-14 20:13 ` Sasha Levin
2025-05-14 6:09 ` [PATCH 5.15 v2 11/14] x86/its: Enable Indirect Target Selection mitigation Pawan Gupta
2025-05-14 20:14 ` Sasha Levin
2025-05-14 6:09 ` [PATCH 5.15 v2 12/14] x86/its: Add "vmexit" option to skip mitigation on some CPUs Pawan Gupta
2025-05-14 20:14 ` Sasha Levin
2025-05-14 6:10 ` [PATCH 5.15 v2 13/14] x86/its: Align RETs in BHB clear sequence to avoid thunking Pawan Gupta
2025-05-14 20:13 ` Sasha Levin
2025-05-14 6:10 ` [PATCH 5.15 v2 14/14] x86/its: Use dynamic thunks for indirect branches Pawan Gupta
2025-05-14 20:14 ` Sasha Levin
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=20250514110833-0cc48f41e2f17b28@stable.kernel.org \
--to=sashal@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.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