CVE-2026-16819: Vulnerabilities in IBM AIX and PowerVM VIOS

Q: Who can exploit this issue?

A local attacker could exploit the race condition. The provided information does not indicate that remote access alone is sufficient.

Q: What impacts are described if exploitation succeeds?

Successful exploitation could cause a denial of service and compromise data integrity.

Q: Which products are identified as affected?

The issue is identified for IBM AIX and IBM PowerVM VIOS.

Published Aug 15, 2026

Updated

AIX could allow a local attacker to cause a denial of service and compromise data integrity due to a time-of-check time-of-use race condition.

Other sources

IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to cause a denial of service and compromise data integrity due to a time-of-check time-of-use race condition.

— MITRE

Affected Software

3 affected components

IBM AIX<=7.2

IBM AIX<=7.3

IBM PowerVM VIOS<=4.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade IBM AIX 7.2 to a version that resolves this vulnerability.
Fixed in SP13Patch IJ5956608
Upgrade
Upgrade IBM AIX 7.3 TL04 to a version that resolves this vulnerability.
Fixed in SP2Patch IJ5956608
Upgrade
Upgrade IBM AIX 7.3 TL03 to a version that resolves this vulnerability.
Fixed in SP3Patch IJ5956508
Upgrade
Upgrade IBM AIX 7.3 TL02 to a version that resolves this vulnerability.
Fixed in SP5Patch IJ5956408
Upgrade
Upgrade IBM AIX 7.2 TL05 to a version that resolves this vulnerability.
Fixed in SP13Patch IJ59563
Upgrade
Upgrade IBM PowerVM VIOS 4.1.0 to a version that resolves this vulnerability.
Fixed in 4.1.0.50Patch IJ5956508
Upgrade
Upgrade IBM PowerVM VIOS 4.1.1 to a version that resolves this vulnerability.
Fixed in 4.1.1.30Patch IJ5956408
Upgrade
Upgrade IBM PowerVM VIOS 4.1.2 to a version that resolves this vulnerability.
Fixed in 4.1.2.20Patch IJ5956308
Operational
An LPAR reboot is required to complete the SP/FP update.
Operational
For VIOS 4.1.0 and VIOS 4.1.1, perform the additional steps required to migrate to the latest Postgres15 after applying the 4.1.0.50 or 4.1.1.30 FPs.

Event History

Aug 15, 2026

CVE Published

via IBM·12:00 AM

Data Sourced

via IBM·12:00 AM

DescriptionAffected Software

Aug 19, 2026

CVE Published

via MITRE·03:07 PM

Data Sourced

via MITRE·03:07 PM

RemedyDescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

IBM-7283858

Frequently Asked Questions

Who can exploit this issue?