[release-24.11] xen: manual backport of XSAs #467 & #469#407311
Merged
LeSuisse merged 2 commits intoNixOS:release-24.11from May 16, 2025
Merged
[release-24.11] xen: manual backport of XSAs #467 & #469#407311LeSuisse merged 2 commits intoNixOS:release-24.11from
LeSuisse merged 2 commits intoNixOS:release-24.11from
Conversation
When setting up interrupt remapping for legacy PCI(-X) devices,
including PCI(-X) bridges, a lookup of the upstream bridge is required.
This lookup, itself involving acquiring of a lock, is done in a context
where acquiring that lock is unsafe. This can lead to a deadlock.
The passing through of certain kinds of devices to an unprivileged guest
can result in a Denial of Service (DoS) affecting the entire host.
Note: Normal usage of such devices by a privileged domain can also
trigger the issue. In such a scenario, the deadlock is not
considered a security issue, but just a plain bug.
Systems with Intel IOMMU hardware (VT-d) are affected. Systems using
AMD or non-x86 hardware are not affected.
Only systems where certain kinds of devices are passed through to an
unprivileged guest are vulnerable.
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
(cherry picked from commit 5af1d19)
Researchers at VU Amsterdam have released Training Solo, detailing several speculative attacks which bypass current protections. One issue, which Intel has named Indirect Target Selection, is a bug in the hardware support for prediction-domain isolation. The mitigation for this involves both microcode and software changes in Xen. For more details, see: 1. https://vusec.net/projects/training-solo 2. https://www.intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/advisory-guidance/indirect-target-selection.html Another issue discussed in the Training Solo paper pertains to classic-BPF. Xen does not have any capability similar to BPF filters, so is not believed to be affected by this issue. Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net> (cherry picked from commit c29710d)
8 tasks
Contributor
Author
|
hehongbo
approved these changes
May 15, 2025
Member
|
Confirmed nixpkgs-review builds, let's merge. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Manual backport of #385642 and #406506.
Things done
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.