CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-45894 remediation guide

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Clear Present bit before tearing down PASID entry The Intel VT-d Scalable Mode PASID table entry consists of 512 bits (64 bytes). When tearing down an entry, the current implementation zeros the entire 64-byte structure immediately using multiple 64-bit writes. Since the IOMMU hardware may fetch these 64 bytes using multiple internal transactions (e.g., four 128-bit bursts), updating or zeroing the entire entry while it is active (P=1) risks a "torn" read. If a hardware fetch occurs simultaneously with the CPU z...

Open CVE record
ProductLinux Linux, linux kernel
Affected versions0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15, 5.0, >= 5.0 < 6.12.75, >= 6.13 < 6.18.14, >= 6.19 < 6.19.4
Fixed versions6.12.75, 6.18.14, 6.19.4
Priority basisReview · CVSS 7.8 · EPSS 0.15%
01

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.
02

Validate the affected-version match

Compare the deployed version with the affected range: 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15, 5.0, >= 5.0 < 6.12.75, >= 6.13 < 6.18.14, >= 6.19 < 6.19.4. Treat incomplete inventory results as unresolved.

03

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.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 6.12.75, 6.18.14, 6.19.4. Preserve configuration and rollback material before change.

05

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.