CVE-2026-53360 remediation guide
Linux Linux, linux kernel
In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use As per the GHCB spec, when using GHCB v2+ require the software scratch area to reside in the GHCB's shared buffer. Note, things like Page State Change (PSC) requests _rely_ on this behavior, as the guest can't provide a length when making the request, i.e. the size of the guest payload is bounded by the size of the shared buffer. Failure to force usage of the GHCB, and a slew of other flaws, lets a malicious SNP guest corrupt host kernel heap memory, and leak host...
Identify the affected asset
Confirm whether Linux Linux, linux kernel is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: >= 4af663c2f64a8d252e690c60cf8b8abf22dc2951 < bf9ba093fbb83c0c9a3dedd50efec29424eca2fc, >= 4af663c2f64a8d252e690c60cf8b8abf22dc2951 < c9b4198fbc6ed99a9da4bee9f74bb730f926c9ae, >= 4af663c2f64a8d252e690c60cf8b8abf22dc2951 < b328ede59ac34e7998e1eee5e5f0cc26c2a91846, >= 4af663c2f64a8d252e690c60cf8b8abf22dc2951 < db3f2195d29344a3cf1e9dd9ab7f21ced7308cf7, >= 6.10, >= 6.10 < 6.12.93, >= 6.13 < 6.18.35, >= 6.19 < 7.0.12, 7.1. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Follow the vendor advisory or supported update path. Current fixed-version status: 6.12.93, 6.18.35, 7.0.12. Preserve configuration and rollback material before change.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.