CVE-2026-64436

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. A secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 only reserves sizeof(struct xfrm_algo) (i.e. no room for a key), so the field is left containing uninitialized slab data.

calg->alg_key_len is later used as a length by xfrm_algo_clone() when an IPComp state is cloned during XFRM_MSG_MIGRATE:

xfrm_state_migrate() xfrm_state_clone_and_setup() x->calg = xfrm_algo_clone(orig->calg); kmemdup(orig, xfrm_alg_len(orig));

where xfrm_alg_len() returns sizeof(*alg) + (alg_key_len + 7) / 8. With a non-zero garbage alg_key_len, kmemdup() reads past the end of the 68-byte calg object. Adding an IPComp SA via PF_KEY and then migrating it triggers (net-next, KASAN, init_on_alloc=0):

BUG: KASAN: slab-out-of-bounds in kmemdup_noprof+0x44/0x60 Read of size 4164 at addr ff11000025a74980 by task diag2/9287 CPU: 3 UID: 0 PID: 9287 Comm: diag2 7.1.0-rc6-g903db046d557 #1 Call Trace: dump_stack_lvl+0x10e/0x1f0 print_report+0xf7/0x600 kasan_report+0xe4/0x120 kasan_check_range+0x105/0x1b0 __asan_memcpy+0x23/0x60 kmemdup_noprof+0x44/0x60 xfrm_state_migrate+0x70a/0x1da0 xfrm_migrate+0x753/0x18a0 xfrm_do_migrate+0xb47/0xf10 xfrm_user_rcv_msg+0x411/0xb50 netlink_rcv_skb+0x158/0x420 xfrm_netlink_rcv+0x71/0x90 netlink_unicast+0x584/0x850 netlink_sendmsg+0x8b0/0xdc0 ____sys_sendmsg+0x9f7/0xb90 ___sys_sendmsg+0x134/0x1d0 __sys_sendmsg+0x16d/0x220 do_syscall_64+0x116/0x7d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Allocated by task 9287: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 pfkey_add+0x2652/0x2ea0 pfkey_process+0x6d0/0x830 pfkey_sendmsg+0x42c/0x850 __sys_sendto+0x461/0x4b0 __x64_sys_sendto+0xe0/0x1c0 do_syscall_64+0x116/0x7d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f

The buggy address belongs to the object at ff11000025a74980 which belongs to the cache kmalloc-96 of size 96 The buggy address is located 0 bytes inside of allocated 68-byte region [ff11000025a74980, ff11000025a749c4)

Depending on the uninitialized value the same field can instead request an oversized kmemdup() allocation and make the migration clone fail.

The XFRM netlink path is not affected: verify_one_alg() rejects an XFRMA_ALG_COMP attribute shorter than xfrm_alg_len(), so a calg added via XFRM_MSG_NEWSA is always self-consistent.

Initialize calg->alg_key_len to 0, matching the aalg/ealg branches.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 25, 2026

Last Modified

September 3, 2026

Advisory Details (8)

Auto-updated Jul 27, 2026
Patch available.
Web page

net: af_key: initialize alg_key_len for IPComp states - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e8417353cbd078d10531ba3928e609c84ab09e6b
Web page

net: af_key: initialize alg_key_len for IPComp states - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d129c3177d7b1138fd5066fcc63a698b3ba415b0
Web page

net: af_key: initialize alg_key_len for IPComp states - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cea34abc94b0a81e3a8b5cfb41cf45af37c2c67e
Web page

net: af_key: initialize alg_key_len for IPComp states - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6de2a650917bedaaefd65b17cede83c5e2c1dedd
Web page

net: af_key: initialize alg_key_len for IPComp states - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/58e82fc3dedb57b1432292504415b224fd2d6acb
Web page

net: af_key: initialize alg_key_len for IPComp states - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f63d1752d90c0e28be931a48ab5d89bc97d637d
Web page

net: af_key: initialize alg_key_len for IPComp states - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/273c06b81d2e902b21acc801ae18c8276c8a9b69
Web page

net: af_key: initialize alg_key_len for IPComp states - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01b9115b55018123ef2449ac4951f89147a8428e

Vendor Advisories for CVE-2026-64436(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(17)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-07ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-10-07ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2018.18) @ resolute2026-10-07ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18) @ resolute2026-10-07ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1011.11) @ resolute2026-10-07ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-07ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-07ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-10-07ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1122.131) @ jammy2026-10-07ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-10-07ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-10-07ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1118.115) @ jammy2026-10-07ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-10-07ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1036.39) @ noble2026-10-07ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1019.19) @ resolute2026-10-07ubuntu
ubuntulinux-tools-ibm-7.0 (7.0.0-1013.13) @ resolute2026-10-07ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-10-07ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)
  • every version up to 5.10.262-1: fixed in 5.10.262-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)
  • every version up to 6.1.180-1~deb11u1: fixed in 6.1.180-1~deb11u1
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
linux-6.12—
  • every version up to 6.12.100-1~deb12u1: fixed in 6.12.100-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)
  • every version up to 6.12.96-1: fixed in 6.12.96-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (159 versions)
  • every version up to 7.1.4-1: fixed in 7.1.4-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(17)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 77× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 269 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 169 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-13 11:41 UTCEG score recompute
  3. 2026-10-13 11:41 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-12 15:48 UTCEG score recompute
  6. 2026-10-11 19:32 UTCEG score recompute
  7. 2026-10-11 16:47 UTCEG score recompute
  8. 2026-10-11 14:09 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-07 04:26 UTCEG score recompute
  14. 2026-10-07 04:26 UTCVendor advisory
  15. 2026-10-07 04:26 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-04 07:27 UTCEG score recompute
  20. 2026-10-04 07:27 UTCVendor advisory
  21. 2026-10-04 07:27 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-02 18:33 UTCEG score recompute
  24. 2026-10-02 18:33 UTCVendor advisory
  25. 2026-10-02 18:33 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
Show 75 more
  1. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-01 15:55 UTCVendor advisory
  4. 2026-10-01 15:54 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  5. 2026-10-01 04:01 UTCEG score recompute
  6. 2026-10-01 04:01 UTCVendor advisory
  7. 2026-10-01 04:01 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  8. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-09-29 08:01 UTCEG score recompute
  10. 2026-09-29 08:01 UTCVendor advisory
  11. 2026-09-29 08:00 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  12. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-09-28 04:09 UTCEG score recompute
  14. 2026-09-28 04:09 UTCVendor advisory
  15. 2026-09-28 04:09 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  16. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-09-25 07:40 UTCEG score recompute
  18. 2026-09-25 07:40 UTCVendor advisory
  19. 2026-09-25 07:40 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  20. 2026-09-24 10:00 UTCVendor advisory
  21. 2026-09-24 10:00 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  22. 2026-09-23 22:07 UTCEG score recompute
  23. 2026-09-23 22:07 UTCVendor advisory
  24. 2026-09-23 22:07 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  25. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-09-23 09:51 UTCVendor advisory
  27. 2026-09-23 09:51 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  28. 2026-09-22 21:58 UTCEG score recompute
  29. 2026-09-22 21:58 UTCVendor advisory
  30. 2026-09-22 21:57 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  31. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-09-20 01:21 UTCEG score recompute
  33. 2026-09-20 01:21 UTCVendor advisory
  34. 2026-09-20 01:21 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  35. 2026-09-18 19:38 UTCEG score recompute
  36. 2026-09-18 19:38 UTCVendor advisory
  37. 2026-09-18 19:38 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  38. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  39. 2026-09-18 02:43 UTCEG score recompute
  40. 2026-09-18 02:43 UTCVendor advisory
  41. 2026-09-18 02:43 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  42. 2026-09-17 01:51 UTCEG score recompute
  43. 2026-09-17 01:51 UTCVendor advisory
  44. 2026-09-17 01:51 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  45. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  46. 2026-09-16 06:25 UTCVendor advisory
  47. 2026-09-16 06:25 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  48. 2026-09-15 09:21 UTCEG score recompute
  49. 2026-09-15 09:21 UTCVendor advisory
  50. 2026-09-15 09:21 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  51. 2026-09-14 16:33 UTCVendor advisory
  52. 2026-09-14 16:33 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  53. 2026-09-14 04:32 UTCEG score recompute
  54. 2026-09-14 04:32 UTCVendor advisory
  55. 2026-09-14 04:32 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  56. 2026-09-13 16:38 UTCVendor advisory
  57. 2026-09-13 16:38 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  58. 2026-09-13 04:45 UTCVendor advisory
  59. 2026-09-13 04:45 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  60. 2026-09-12 16:51 UTCEG score recompute
  61. 2026-09-12 16:51 UTCVendor advisory
  62. 2026-09-12 16:51 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  63. 2026-09-12 04:57 UTCVendor advisory
  64. 2026-09-12 04:57 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  65. 2026-09-11 16:20 UTCEG score recompute
  66. 2026-09-11 16:20 UTCVendor advisory
  67. 2026-09-11 16:20 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  68. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  69. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  70. 2026-09-10 22:23 UTCVendor advisory
  71. 2026-09-10 22:23 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  72. 2026-09-10 10:29 UTCEG score recompute
  73. 2026-09-10 10:29 UTCVendor advisory
  74. 2026-09-10 10:29 UTCGHSA enrichmentGHSA-rcfx-m5g2-2jgr · GitHub severity HIGH · GitHub CVSS 7.1
  75. 2026-09-09 08:32 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64436?
CVE-2026-64436 is a high-severity vulnerability; its CVE record was published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: afkey: initialize algkey_len for IPComp states pfkeymsg2xfrmstate() handles the IPComp (SADBXSATYPE_IPCOMP) case by allocating x->calg and copying only the algorithm name: x->calg = kmalloc_obj(*x->calg); if (!x->calg) { err =…
When was the CVE record for CVE-2026-64436 published?
The CVE record for CVE-2026-64436 was published on July 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 3, 2026; the record at its source may have been updated since.
Is CVE-2026-64436 actively exploited?
CVE-2026-64436 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64436?
CVE-2026-64436 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64436?
A fix for CVE-2026-64436 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64436 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64436

Explore →

Is Your Infrastructure Affected by CVE-2026-64436?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs