Kernel memory corruption via shared bus notifier
Published Dec 24, 2025 · Updated Dec 24, 2025
A type confusion in affected Linux kernel builds allows local users to read or corrupt kernel memory during PowerPC device registration. The shared notifier node sends VIO events through pci_notify(), where to_pci_dev() treats a VIO device as PCI and accesses memory out of bounds. Reachability requires a PowerPC pseries build with non-default CONFIG_FAIL_IOMMU plus PCI and IBMVIO; the corruption can expose kernel data or panic the system.
Summary
What happened
A type confusion in affected Linux kernel builds allows local users to read or corrupt kernel memory during PowerPC device registration. The shared notifier node sends VIO events through pci_notify(), where to_pci_dev() treats a VIO device as PCI and accesses memory out of bounds. Reachability requires a PowerPC pseries build with non-default CONFIG_FAIL_IOMMU plus PCI and IBMVIO; the corruption can expose kernel data or panic the system.
The record
- CVE
- CVE-2023-54095
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.6
- Affected versionversion=d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 <075a4dcdbc9a5ea793cb8ec8b78a6c0b7636fd52
- Affected versionversion=d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 <65bf8a196ba25cf65a858b5bb8de80f0aad76691
- Affected versionversion=d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 <6670c65bf863cd0d44ca24d4c10ef6755b8d9529
- Affected versionversion=d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 <a9ddbfed53465bc7c411231db32a488066c0c1be
- Affected versionversion=d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 <c37b6908f7b2bd24dcaaf14a180e28c9132b9c58
- Affected versionversion=d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 <c46af58588253e5e4063bb5ddc78cd12fdf9e55d
- Affected versionversion=d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 <dc0d107e624ca96aef6dd8722eb33ba3a6d157b0
- Affected versionversion=d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 <f08944e3c6962b00827de7263a9e20688e79ad84
- Affected versionversion=d6b9a81b2a45786384f5bd3516bd6ddfb4b772c6 <f17d5efaafba3d5f02f0373f7c5f44711d676f3e
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo