Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-54095: powerpc/iommu: Fix notifiers being shared by PCI and VIO buses

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 075a4dcdbc9a5ea793cb8ec8b78a6c0b7636fd52, 65bf8a196ba25cf65a858b5bb8de80f0aad76691, 6670c65bf863cd0d44ca24d4c10ef6755b8d9529.

Low priority for now. Upgrade to Linux Linux 075a4dcdbc9a5ea793cb8ec8b78a6c0b7636fd52, 65bf8a196ba25cf65a858b5bb8de80f0aad76691, 6670c65bf863cd0d44ca24d4c10ef6755b8d9529 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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 device, and finally makes a bad access in vga_arbiter_add_pci_device() as discovered with KASAN: BUG: KASAN: slab-out-of-bounds in vga_arbiter_add_pci_device+0x60/0xe00 Read of size 4 at addr c000000264c26fdc by task swapper/0/1 Call Trace: dump_stack_lvl+0x1bc/0x2b8 (unreliable) print_report+0x3f4/0xc60 kasan_report+0x244/0x698 __asan_load4+0xe8/0x250 vga_arbiter_add_pci_device+0x60/0xe00 pci_notify+0x88/0x444 notifier_call_chain+0x104/0x320 blocking_notifier_call_chain+0xa0/0x140 device_add+0xac8/0x1d30 device_register+0x58/0x80 vio_register_device_node+0x9ac/0xce0 vio_bus_scan_register_devices+0xc4/0x13c __machine_initcall_pseries_vio_device_init+0x94/0xf0 do_one_initcall+0x12c/0xaa8 kernel_init_freeable+0xa48/0xba8 kernel_init+0x64/0x400 ret_from_kernel_thread+0x5c/0x64 Fix this by creating separate notifier_block structs for each bus type. [mpe: Add #ifdef to fix CONFIG_IBMVIO=n build]

HighCVSS 7.0 · v3.1—No exploit Fix available
Published
Dec 24, 2025
Updated
Oct 15, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.0
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-54095

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.6affected
    • d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 and later · before dc0d107e624ca96aef6dd8722eb33ba3a6d157b0affected · git
    • d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 and later · before 075a4dcdbc9a5ea793cb8ec8b78a6c0b7636fd52affected · git
    • d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 and later · before 65bf8a196ba25cf65a858b5bb8de80f0aad76691affected · git
    • d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 and later · before f08944e3c6962b00827de7263a9e20688e79ad84affected · git
    • d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 and later · before a9ddbfed53465bc7c411231db32a488066c0c1beaffected · git
    • d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 and later · before f17d5efaafba3d5f02f0373f7c5f44711d676f3eaffected · git
    • d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 and later · before c46af58588253e5e4063bb5ddc78cd12fdf9e55daffected · git
    • d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 and later · before 6670c65bf863cd0d44ca24d4c10ef6755b8d9529affected · git
    • d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 and later · before c37b6908f7b2bd24dcaaf14a180e28c9132b9c58affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.55-16.1.55-1
Debian:13linuxbefore 6.5.3-16.5.3-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-54092Dec 24, 2025 · KVM: s390: pv: fix index value of replaced ASCE
    35Monitor
  • ← EarlierCVE-2023-54094Dec 24, 2025 · net: prevent skb corruption on frag list segmentation
    39Monitor
  • Later →CVE-2023-54098Dec 24, 2025 · drm/i915/gvt: fix gvt debugfs destroy
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux075a4dcdbc9a5ea793cb8ec8b78a6c0b7636fd52Vendor (CNA)
Linux Linux65bf8a196ba25cf65a858b5bb8de80f0aad76691Vendor (CNA)
Linux Linux6670c65bf863cd0d44ca24d4c10ef6755b8d9529Vendor (CNA)
Linux Linuxa9ddbfed53465bc7c411231db32a488066c0c1beVendor (CNA)
Linux Linuxc37b6908f7b2bd24dcaaf14a180e28c9132b9c58Vendor (CNA)
Linux Linuxc46af58588253e5e4063bb5ddc78cd12fdf9e55dVendor (CNA)
Linux Linuxdc0d107e624ca96aef6dd8722eb33ba3a6d157b0Vendor (CNA)
Linux Linuxf08944e3c6962b00827de7263a9e20688e79ad84Vendor (CNA)
Linux Linuxf17d5efaafba3d5f02f0373f7c5f44711d676f3eVendor (CNA)
debian:linux6.1.55-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records