Database/Firmware, BMC & network fabric

IBM Power Systems firmware: boot image validation flaw accepts a crafted code update image and runs it on the host
Impact
The host firmware boot process does not properly validate code update images, so an attacker with service access to the service processor can supply a malicious update image and execute arbitrary code on the host system. This is a signed-boot bypass in practice: the code the operator believes is verified firmware is attacker-supplied, it survives reinstalling the OS, and it sits beneath the hypervisor and every partition on the node. For a fleet, the worst case is a node that stays compromised through reimaging and cannot be trusted again without a known-good reflash. This id spans the widest firmware range of the batch - FW1120.00 through FW1120.01, FW1110.00 through FW1110.31, and FW1060.00 through FW1060.81.
Who can reach it
Local to the service processor with high privilege: an attacker needs service access to the FSP to stage the crafted code update image. No host OS or partition access needed.
What to do
Apply the fixed firmware level from IBM support document 7290129, which covers the FW1120, FW1110 and FW1060 streams. A firmware update is the fix and the update path itself is what is broken, so flash from a trusted source with the managed system out of service, and verify the resulting level afterwards. Keep FSP access restricted to the management VLAN and to accounts you can account for.
References
Related entries
- IBM Power Systems firmware: second FSP mailbox overflow in runtime attribute storage yields firmware code executionCVE-2026-96264 · IBM Power Systems host firmware (FSP mailbox, runtime attribute storage)High
- IBM Power Systems firmware: FSP mailbox message reads or modifies arbitrary Hostboot memoryCVE-2026-96265 · IBM Power Systems host firmware (FSP mailbox, Hostboot memory access)High
- IBM Power Systems firmware: crafted configuration data corrupts host firmware memory during IPLCVE-2026-96266 · IBM Power Systems host firmware (configuration parsing during IPL)High
- Supermicro IPMI BMC firmware: Every affected BMC shares one TLS private key and one SSH host key, baked into theCVE-2013-3619 · Supermicro IPMI BMC firmwareHigh
- Dell iDRAC6/iDRAC7 IPMI 1.5 session handling: IPMI 1.5 session IDs are handed out incrementally from a small pool, soCVE-2014-8272 · Dell iDRAC6/iDRAC7 IPMI 1.5 session handlingHigh
- Dell iDRAC9: Stack overflow overwriting iDRAC configuration via oversized payloadsCVE-2021-21540 · Dell iDRAC9High
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.