Review reviewHigh

CVE-2023-54095

Linux

In the Linux kernel, the following vulnerability has been resolved: powerpc/iommu: Fix notifiers being shared by PCI and VIO buses fail_iommu_setup() registers the fail_iommu_bus_notifier struct to both PCI and VIO buses. struct notifier_block is a linked list node, so this causes any notifiers later registered to either bus type to also be registered to the other since they share the same node. This causes issues in (at least) the vgaarb code, which registers a notifier for PCI buses. pci_notify() ends up being called on a vio device, converted with to_pci_dev() even though it's not a PCI...

CVSS
7
EPSS
0.14%
3.95% percentile
CISA KEV
Not listed
Published
2025.12.24
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.14%
Technical severityCVSS 7

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: powerpc/iommu: Fix notifiers being shared by PCI and VIO buses fail_iommu_setup() registers the fail_iommu_bus_notifier struct to both PCI and VIO buses. struct notifier_block is a linked list node, so this causes any notifiers later registered to either bus type to also be registered to the other since they share the same node. This causes issues in (at least) the vgaarb code, which registers a notifier for PCI buses. pci_notify() ends up being called on a vio device, converted with to_pci_dev() even though it's not a PCI...

Affected product and versions

Product
Linux
Affected versions
>= d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 < dc0d107e624ca96aef6dd8722eb33ba3a6d157b0, >= d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 < 075a4dcdbc9a5ea793cb8ec8b78a6c0b7636fd52, >= d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 < 65bf8a196ba25cf65a858b5bb8de80f0aad76691, >= d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 < f08944e3c6962b00827de7263a9e20688e79ad84, >= d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 < a9ddbfed53465bc7c411231db32a488066c0c1be, >= d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 < f17d5efaafba3d5f02f0373f7c5f44711d676f3e, >= d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 < c46af58588253e5e4063bb5ddc78cd12fdf9e55d, >= d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 < 6670c65bf863cd0d44ca24d4c10ef6755b8d9529, >= d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 < c37b6908f7b2bd24dcaaf14a180e28c9132b9c58, >= 3.6
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available