Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-54095

powerpc/iommu: Fix notifiers being shared by PCI and VIO buses

High7.0EPSS 0.16%
Published
Updated
Reserved
Assigned by
Linux

Description

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]

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 10 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-54095, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.0.

Affected products

  • Linux · Linux

    • affected d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 – < dc0d107e624ca96aef6dd8722eb33ba3a6d157b0
    • affected d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 – < 075a4dcdbc9a5ea793cb8ec8b78a6c0b7636fd52
    • affected d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 – < 65bf8a196ba25cf65a858b5bb8de80f0aad76691
    • affected d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 – < f08944e3c6962b00827de7263a9e20688e79ad84
    • affected d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 – < a9ddbfed53465bc7c411231db32a488066c0c1be
    • affected d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 – < f17d5efaafba3d5f02f0373f7c5f44711d676f3e
    • affected d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 – < c46af58588253e5e4063bb5ddc78cd12fdf9e55d
    • affected d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 – < 6670c65bf863cd0d44ca24d4c10ef6755b8d9529
    • affected d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 – < c37b6908f7b2bd24dcaaf14a180e28c9132b9c58
  • Linux · Linux

    • affected 3.6
    • unaffected < 3.6
    • unaffected 4.14.326 – ≤ 4.14.*
    • unaffected 4.19.295 – ≤ 4.19.*
    • unaffected 5.4.257 – ≤ 5.4.*
    • unaffected 5.10.195 – ≤ 5.10.*
    • unaffected 5.15.132 – ≤ 5.15.*
    • unaffected 6.1.53 – ≤ 6.1.*
    • unaffected 6.4.16 – ≤ 6.4.*
    • unaffected 6.5.3 – ≤ 6.5.*
    • unaffected 6.6 – ≤ *

References (9)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-54095 badge
[![CVE-2023-54095](https://trackcve.app/badge/CVE-2023-54095.svg)](https://trackcve.app/cve/CVE-2023-54095)

Record last updated .