CVE-2026-19442 is a high severity (CVSS 8.2) pointer validation flaw in the AIX Virtual SCSI (vSCSI) initiator driver on IBM AIX 7.2 and 7.3 and PowerVM VIOS 4.1. It may cause denial of service, privilege escalation or compromise of the client LPAR kernel. IBM details fixes in bulletin 7283858.
What's affected
IBM AIX 7.2 and 7.3 and IBM PowerVM VIOS 4.1 are affected. IBM's bulletin 7283858 is shared by several AIX and VIOS CVEs and says fixes are delivered as service packs and fix packs inside cumulative maintenance packages. The text we could read did not state the exact fix level for this CVE, and the bulletin has special steps for applying updates through NIM and extra steps after VIOS 4.1.0 and 4.1.1 updates. Read the Remediation and Fixes section of the bulletin for the level that applies to your system rather than relying on a number from this post.
IBM lists no workaround for this issue.
IBM's score is 8.2 with the vector AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. The record names the AIX Virtual SCSI initiator driver, which runs on client LPARs that use storage served by a VIOS.
How to check if you're exposed
Find the technology level and service pack of each LPAR. On AIX, run:
oslevel -s
On a VIOS, sign in as padmin and run:
ioslevel
Compare the result with the fixed levels in the Remediation section of IBM's bulletin. If you use NIM, list the clients and their levels from the NIM master so you can plan the update in one pass.
Then identify which LPARs use virtual SCSI storage from a VIOS. Those clients load the initiator driver the record names. Your HMC shows the virtual adapter mappings for each partition.
What to do now
- List the LPARs that use virtual SCSI storage.
- Collect the AIX and VIOS levels for them.
- Find the fix level in the Remediation section of bulletin 7283858 and apply it.
- Review who holds administrative access on client LPARs and on the VIOS.
- Verify levels after the update.
Why it matters
The weakness class is CWE-822, untrusted pointer dereference. A driver uses a pointer value that comes from outside its trust boundary without checking where it points. A kernel driver that follows a bad pointer can crash the system, or if the value is chosen with care, corrupt or read kernel memory.
The record says successful exploitation may lead to denial of service, privilege escalation or full compromise of the client LPAR kernel. The need for high privileges and local access narrows the attack, but virtualization layers concentrate trust, so kernel level flaws in storage drivers deserve prompt maintenance. KEV is false.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Which systems run the vSCSI initiator driver?
Client LPARs that use virtual SCSI storage provided by a VIOS.
Is there a workaround?
IBM lists none. Apply the fix level in the bulletin.
Sources
Last reviewed: 18 October 2026.
