CVE-2026-19448 is a kernel stack corruption vulnerability in AIX and PowerVM VIOS IPsec ESP decapsulation. The root cause is the fundamental tension in kernel fast-path networking: developers must calculate buffer sizes for variable-length encrypted payloads before cryptographic processing completes, and stack allocation in this path is a performance requirement, not a choice. The corruption pattern indicates a bounds miscalculation after crypto operations, likely a padding or authentication tag stripping error that overruns a fixed-size stack buffer. This is not a novel vulnerability class — the same pattern has manifested in Cisco IOS, Linux XFRM, and FreeBSD IPsec implementations. The shared ancestry between AIX and PowerVM VIOS strongly suggests the same legacy code lineage, not independent coincidental flaws. For defenders: verify your AIX kernel build uses stack canaries and bounds-checking compiler optimizations; check whether your IPsec configuration uses extended sequence numbers or fragmented inner packets, which expand the attack surface. The fix will likely add explicit bounds verification after crypto operations or switch to dynamically-sized buffers. Investigate whether your VIOS version carries the same IPsec code path — the blast radius here extends beyond the hypervisor to every LPAR depending on VIOS for storage and network topology. IBM's CVSS 6.5 is conservative; treat this as higher severity given the VIOS blast radius. If you're running legacy AIX IPsec configurations, prioritize isolation until the patch lands.
CVE-2026-19448
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 A stack memory corruption vulnerability exists in the AIX IPsec ESP decapsulation handler. Successful exploitation may corrupt kernel stack state and cause a system crash, resulting in denial of service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisMemory or a resource is used before it has been initialised, so its contents are whatever happened to be there — sometimes leaking earlier data, sometimes values an attacker can influence. Behaviour becomes unpredictable and occasionally exploitable. Remediation is initialising every resource before use and ensuring initialisation happens on all code paths.
General guidance for the use of uninitialized resource class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $4,000. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-19448 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesCVE-2026-19448 is a kernel stack corruption vulnerability in AIX and PowerVM VIOS IPsec ESP decapsulation. The root cause is the fundamental tension in kernel fast-path networking: developers must calculate buffer sizes for variable-length encrypted payloads before cryptographic processing completes, and stack allocation in this path is a performance requirement, not a choice. The corruption pattern indicates a bounds miscalculation after crypto operations, likely a padding or authentication tag stripping error that overruns a fixed-size stack buffer. This is not a novel vulnerability class — the same pattern has manifested in Cisco IOS, Linux XFRM, and FreeBSD IPsec implementations. The shared ancestry between AIX and PowerVM VIOS strongly suggests the same legacy code lineage, not independent coincidental flaws. For defenders: verify your AIX kernel build uses stack canaries and bounds-checking compiler optimizations; check whether your IPsec configuration uses extended sequence numbers or fragmented inner packets, which expand the attack surface. The fix will likely add explicit bounds verification after crypto operations or switch to dynamically-sized buffers. Investigate whether your VIOS version carries the same IPsec code path — the blast radius here extends beyond the hypervisor to every LPAR depending on VIOS for storage and network topology. IBM's CVSS 6.5 is conservative; treat this as higher severity given the VIOS blast radius. If you're running legacy AIX IPsec configurations, prioritize isolation until the patch lands.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-19448 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data