CVE-2023-54095

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2025-12-24. the CNA's CVSS baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

A fix is available — apply it.

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]

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
36(Track)
EG Risk 36/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

powerpc/iommu: Fix notifiers being shared by PCI and VIO buses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c37b6908f7b2bd24dcaaf14a180e28c9132b9c58
generic

powerpc/iommu: Fix notifiers being shared by PCI and VIO buses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6670c65bf863cd0d44ca24d4c10ef6755b8d9529
generic

powerpc/iommu: Fix notifiers being shared by PCI and VIO buses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c46af58588253e5e4063bb5ddc78cd12fdf9e55d
generic

powerpc/iommu: Fix notifiers being shared by PCI and VIO buses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f17d5efaafba3d5f02f0373f7c5f44711d676f3e
generic

powerpc/iommu: Fix notifiers being shared by PCI and VIO buses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a9ddbfed53465bc7c411231db32a488066c0c1be
generic

powerpc/iommu: Fix notifiers being shared by PCI and VIO buses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f08944e3c6962b00827de7263a9e20688e79ad84
generic

powerpc/iommu: Fix notifiers being shared by PCI and VIO buses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65bf8a196ba25cf65a858b5bb8de80f0aad76691
generic

powerpc/iommu: Fix notifiers being shared by PCI and VIO buses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/075a4dcdbc9a5ea793cb8ec8b78a6c0b7636fd52
generic

powerpc/iommu: Fix notifiers being shared by PCI and VIO buses - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dc0d107e624ca96aef6dd8722eb33ba3a6d157b0

Vendor Advisories for CVE-2023-54095(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
linuxKernel @ 4.14.326—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (34 versions)5.10.197-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-1 ... 6.1.55-1~bpo11+1 (10 versions)6.1.55-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.5.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.5.3-1—

Data Freshness Timeline

(refreshed 8× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 193 total refreshes for this CVE.

  1. 2026-09-18 19:26 UTCEPSS rescore
  2. 2026-09-16 14:06 UTCEPSS rescore
  3. 2026-09-16 05:11 UTCEPSS rescore
  4. 2026-09-16 05:11 UTCEPSS rescore
  5. 2026-09-15 03:08 UTCEPSS rescore
  6. 2026-09-14 05:49 UTCOSV refresh
  7. 2026-09-13 16:45 UTCEPSS rescore
  8. 2026-09-12 14:58 UTCEPSS rescore
  9. 2026-09-11 14:51 UTCEPSS rescore
  10. 2026-09-11 09:34 UTCEPSS rescore
  11. 2026-09-08 21:58 UTCEPSS rescore
  12. 2026-09-07 15:59 UTCEPSS rescore
  13. 2026-09-06 13:46 UTCEPSS rescore
  14. 2026-09-05 15:26 UTCEPSS rescore
  15. 2026-09-04 13:58 UTCEPSS rescore
  16. 2026-09-04 05:04 UTCEPSS rescore
  17. 2026-09-02 14:10 UTCEPSS rescore
  18. 2026-09-01 13:52 UTCEPSS rescore
  19. 2026-09-01 04:36 UTCEPSS rescore
  20. 2026-08-30 19:15 UTCEPSS rescore
  21. 2026-08-30 01:20 UTCEPSS rescore
  22. 2026-08-28 21:39 UTCEPSS rescore
  23. 2026-08-27 14:23 UTCEPSS rescore
  24. 2026-08-26 14:44 UTCEPSS rescore
  25. 2026-08-26 06:43 UTCOSV refresh
Show 75 more
  1. 2026-08-25 13:47 UTCEPSS rescore
  2. 2026-08-23 00:17 UTCEPSS rescore
  3. 2026-08-23 00:17 UTCEPSS rescore
  4. 2026-08-21 23:47 UTCEPSS rescore
  5. 2026-08-20 22:53 UTCEPSS rescore
  6. 2026-08-19 17:02 UTCEPSS rescore
  7. 2026-08-18 13:46 UTCEPSS rescore
  8. 2026-08-16 14:54 UTCEPSS rescore
  9. 2026-08-16 02:12 UTCEPSS rescore
  10. 2026-08-15 01:28 UTCEPSS rescore
  11. 2026-08-13 21:58 UTCEPSS rescore
  12. 2026-08-12 13:49 UTCEPSS rescore
  13. 2026-08-11 13:40 UTCEPSS rescore
  14. 2026-08-10 23:58 UTCEPSS rescore
  15. 2026-08-09 22:47 UTCEG score recompute
  16. 2026-08-09 22:47 UTCVendor advisory
  17. 2026-08-09 22:47 UTCGHSA enrichment
  18. 2026-08-09 13:44 UTCEPSS rescore
  19. 2026-08-08 16:35 UTCEPSS rescore
  20. 2026-08-08 05:27 UTCEG score recompute
  21. 2026-08-08 05:27 UTCVendor advisory
  22. 2026-08-08 05:27 UTCGHSA enrichment
  23. 2026-08-07 16:25 UTCEPSS rescore
  24. 2026-08-06 13:45 UTCEPSS rescore
  25. 2026-08-06 07:11 UTCEG score recompute
  26. 2026-08-06 07:11 UTCVendor advisory
  27. 2026-08-06 07:10 UTCGHSA enrichment
  28. 2026-08-05 19:15 UTCEPSS rescore
  29. 2026-08-05 19:15 UTCEPSS rescore
  30. 2026-08-05 10:15 UTCEG score recompute
  31. 2026-08-05 10:15 UTCVendor advisory
  32. 2026-08-05 10:15 UTCGHSA enrichment
  33. 2026-08-04 10:49 UTCEG score recompute
  34. 2026-08-04 10:49 UTCVendor advisory
  35. 2026-08-04 10:48 UTCGHSA enrichment
  36. 2026-08-04 10:36 UTCEPSS rescore
  37. 2026-08-04 09:24 UTCEG score recompute▲ 7.00
  38. 2026-08-04 09:24 UTCVendor advisory
  39. 2026-08-04 09:23 UTCGHSA enrichment
  40. 2026-08-04 09:20 UTCMITRE cvelistV5CVSS v3 → 7 · severity → HIGH
  41. 2026-08-03 10:34 UTCEPSS rescore
  42. 2026-08-02 02:25 UTCEPSS rescore
  43. 2026-08-02 02:25 UTCEPSS rescore
  44. 2026-08-01 04:14 UTCEPSS rescore
  45. 2026-07-30 16:26 UTCEPSS rescore
  46. 2026-07-30 01:29 UTCEPSS rescore
  47. 2026-07-28 15:34 UTCEPSS rescore
  48. 2026-07-28 15:34 UTCEPSS rescore
  49. 2026-07-27 03:39 UTCOSV refresh
  50. 2026-07-26 14:53 UTCEPSS rescore
  51. 2026-07-25 14:16 UTCEPSS rescore
  52. 2026-07-24 14:16 UTCEPSS rescore
  53. 2026-07-23 14:16 UTCEPSS rescore
  54. 2026-07-23 02:30 UTCEG score recompute
  55. 2026-07-22 23:16 UTCEG score recompute
  56. 2026-07-22 14:07 UTCEPSS rescore
  57. 2026-07-22 14:07 UTCEPSS rescore
  58. 2026-07-21 15:23 UTCEPSS rescore
  59. 2026-07-20 17:06 UTCEPSS rescore
  60. 2026-07-19 14:30 UTCEPSS rescore
  61. 2026-07-19 14:29 UTCEPSS rescore
  62. 2026-07-18 10:03 UTCEPSS rescore
  63. 2026-07-18 10:03 UTCEPSS rescore
  64. 2026-07-16 17:01 UTCEPSS rescore
  65. 2026-07-15 01:59 UTCEPSS rescore
  66. 2026-07-15 01:59 UTCEPSS rescore
  67. 2026-07-13 22:28 UTCEPSS rescore
  68. 2026-07-13 22:28 UTCEPSS rescore
  69. 2026-07-13 06:11 UTCEPSS rescore
  70. 2026-07-12 05:45 UTCEPSS rescore
  71. 2026-07-12 05:45 UTCEPSS rescore
  72. 2026-07-11 08:26 UTCEPSS rescore
  73. 2026-07-09 22:17 UTCOSV refresh
  74. 2026-07-09 19:08 UTCEPSS rescore
  75. 2026-07-08 15:13 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2023-54095?
CVE-2023-54095 is a high vulnerability published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: powerpc/iommu: Fix notifiers being shared by PCI and VIO buses failiommusetup() registers the failiommubus_notifier struct to both PCI and VIO buses. struct notifier_block is a linked list node, so this causes any notifiers later…
When was CVE-2023-54095 disclosed?
CVE-2023-54095 was first published in the National Vulnerability Database on December 24, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-54095 actively exploited?
CVE-2023-54095 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.6% of all scored CVEs.
What is the CVSS score of CVE-2023-54095?
CVE-2023-54095 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-54095?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54095, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-54095

Explore →

Is Your Infrastructure Affected by CVE-2023-54095?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs