Power Systems Firmware: Integer Overflow or Wraparound
CVE-2026-16933 is a high-severity integer overflow or wraparound vulnerability in Power Systems Firmware from IBM, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited with local access to the system by an attacker with administrator privileges, without any action from a user. Affected Power Systems Firmware versions: FW1120.00; FW1110.00 through FW1110.30; FW1060.00 through FW1060.80, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.17% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Power System S1122 (9824-22a) Firmware to fw1110.31 or a later version.
- Update Power System S1124 (9824-42a) Firmware to fw1110.31 or a later version.
- Update Power System S1122s (9824-22b) Firmware to fw1110.31 or a later version.
- Read the advisory on ibm.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| IBM | Power Systems Firmware | FW1120.00; FW1110.00 through FW1110.30; FW1060.00 through FW1060.80; FW950.00 through FW950.H2; OP940.00 through OP940.a1; OP940.00 through OP940.81 | Not stated |
| IBM | Power System S1122 (9824-22a) Firmware | fw1110.00 up to, but not including, fw1110.31; fw1120.00 | fw1110.31 |
| IBM | Power System S1124 (9824-42a) Firmware | fw1110.00 up to, but not including, fw1110.31; fw1120.00 | fw1110.31 |
| IBM | Power System S1122s (9824-22b) Firmware | fw1110.00 up to, but not including, fw1110.31; fw1120.00 | fw1110.31 |
| IBM | Power System S1114 (9824-41b) Firmware | fw1110.00 up to, but not including, fw1110.31; fw1120.00 | fw1110.31 |
| IBM | Power System L1122 (9856-22h) Firmware | fw1110.00 up to, but not including, fw1110.31; fw1120.00 | fw1110.31 |
| IBM | Power System L1124 (9856-42h) Firmware | fw1110.00 up to, but not including, fw1110.31; fw1120.00 | fw1110.31 |
| IBM | Power System E1150 (9043-mru) Firmware | fw1110.00 up to, but not including, fw1110.31; fw1120.00 | fw1110.31 |
| IBM | Power System S1112 (9242-21b) Firmware | fw1120.00 | Not stated |
| IBM | Power System S1112 (9242-21t) Firmware | fw1120.00 | Not stated |
| IBM | Power System E1080 (9080-hex) Firmware | fw1060.00 up to, but not including, fw1060.81 | fw1060.81 |
| IBM | Power System S1022 (9105-22a) Firmware | fw1060.00 up to, but not including, fw1060.81 | fw1060.81 |
| IBM | Power System S1024 (9105-42a) Firmware | fw1060.00 up to, but not including, fw1060.81 | fw1060.81 |
| IBM | Power System S1022s (9105-22b) Firmware | fw1060.00 up to, but not including, fw1060.81 | fw1060.81 |
| IBM | Power System S1014 (9105-41b) Firmware | fw1060.00 up to, but not including, fw1060.81 | fw1060.81 |
| IBM | Power System L1022 (9786-22h) Firmware | fw1060.00 up to, but not including, fw1060.81 | fw1060.81 |
| IBM | Power System L1024 (9786-42h) Firmware | fw1060.00 up to, but not including, fw1060.81 | fw1060.81 |
| IBM | Power System E1050 (9043-mrx) Firmware | fw1060.00 up to, but not including, fw1060.81 | fw1060.81 |
| IBM | Power System S1012 (9028-21b) Firmware | fw1060.00 up to, but not including, fw1060.81 | fw1060.81 |
| IBM | Power System E1180 (9080-heu) Firmware | fw1110.00 up to, but not including, fw1110.31; fw1120.00 | fw1110.31 |
| IBM | Power System S922 (9009-22g) Firmware | fw950.00 up to, but not including, fw950.h3 | fw950.h3 |
| IBM | Power System H922 (9223-22s) Firmware | fw950.00 up to, but not including, fw950.h3 | fw950.h3 |
| IBM | Power System S914 (9009-41g) Firmware | fw950.00 up to, but not including, fw950.h3 | fw950.h3 |
| IBM | Power System S924 (9009-42g) Firmware | fw950.00 up to, but not including, fw950.h3 | fw950.h3 |
| IBM | Power System H924 (9223-42s) Firmware | fw950.00 up to, but not including, fw950.h3 | fw950.h3 |
Version data comes from the organisation that assigned the CVE; 5 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (us.ibm.com).
Official description
IBM Power Systems Firmware FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, FW950.00 through FW950.H2, OP940.00 through OP940.a1 (Power9), and OP940.00 through OP940.81 (Power HMC) is affected by a vulnerability in the interface between the BMC/FSP and the host system. An attacker with service account or root access to the BMC/FSP can read and write arbitrary regions of host system memory, giving full control over the host system and all hosted partitions, resulting in a confidentiality, integrity, and availability impact.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Integer Overflow or Wraparound
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
How developers prevent this class of flaw
- Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).
More Integer Overflow or Wraparound vulnerabilities (CWE-190)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Power Systems Firmware
- 7.9 High severity
- 7.3 High severity
- 8.3 High severity
- 8.2 High severity
- 8.1 High severity
- 8.2 High severity
Recent Integer Overflow or Wraparound vulnerabilities
- 8.4 High severity
- 8.2 High severity
- 7.5 High severity
- 7.5 High severity
- 9.3 Critical severity
- 8.8 High severity
Spotted an error? Tell us.