SECUFOCUSNOW
Home›CVE index›CVE-2026-64436
Review reviewHigh

CVE-2026-64436

Linux

In the Linux kernel, the following vulnerability has been resolved: net: af_key: initialize alg_key_len for IPComp states pfkey_msg2xfrm_state() handles the IPComp (SADB_X_SATYPE_IPCOMP) case by allocating x->calg and copying only the algorithm name: x->calg = kmalloc_obj(*x->calg); if (!x->calg) { err = -ENOMEM; goto out; } strcpy(x->calg->alg_name, a->name); x->props.calgo = sa->sadb_sa_encrypt; Unlike the authentication (x->aalg) and encryption (x->ealg) branches of the same function, the compression branch never initializes calg->alg_key_len. IPComp carries no key and the allocation onl...

CVSS
7.1
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.1

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: net: af_key: initialize alg_key_len for IPComp states pfkey_msg2xfrm_state() handles the IPComp (SADB_X_SATYPE_IPCOMP) case by allocating x->calg and copying only the algorithm name: x->calg = kmalloc_obj(*x->calg); if (!x->calg) { err = -ENOMEM; goto out; } strcpy(x->calg->alg_name, a->name); x->props.calgo = sa->sadb_sa_encrypt; Unlike the authentication (x->aalg) and encryption (x->ealg) branches of the same function, the compression branch never initializes calg->alg_key_len. IPComp carries no key and the allocation onl...

Affected product and versions

Product
Linux
Affected versions
>= 80c9abaabf4283f7cf4a0b3597cd302506635b7f < 58e82fc3dedb57b1432292504415b224fd2d6acb, >= 80c9abaabf4283f7cf4a0b3597cd302506635b7f < 01b9115b55018123ef2449ac4951f89147a8428e, >= 80c9abaabf4283f7cf4a0b3597cd302506635b7f < 3f63d1752d90c0e28be931a48ab5d89bc97d637d, >= 80c9abaabf4283f7cf4a0b3597cd302506635b7f < 273c06b81d2e902b21acc801ae18c8276c8a9b69, >= 80c9abaabf4283f7cf4a0b3597cd302506635b7f < 6de2a650917bedaaefd65b17cede83c5e2c1dedd, >= 80c9abaabf4283f7cf4a0b3597cd302506635b7f < e8417353cbd078d10531ba3928e609c84ab09e6b, >= 80c9abaabf4283f7cf4a0b3597cd302506635b7f < cea34abc94b0a81e3a8b5cfb41cf45af37c2c67e, >= 80c9abaabf4283f7cf4a0b3597cd302506635b7f < d129c3177d7b1138fd5066fcc63a698b3ba415b0, >= 2.6.21
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
CWE
Not available