CVE-2026-64048

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot

On the SMC-D client, slot 0 of ini->ism_dev[]/ini->ism_chid[] is reserved for an SMC-Dv1 device. smc_find_ism_v2_device_clnt() populates V2 entries starting at index 1, so when no V1 device is selected slot 0 is left in its kzalloc()'ed state with ism_dev[0] == NULL and ism_chid[0] == 0.

smc_v2_determine_accepted_chid() then matches the peer's CHID against the array starting from index 0 using the CHID alone. A malicious peer replying to a SMC-Dv2-only proposal with d1.chid == 0 matches the empty slot, ini->ism_selected becomes 0, and the subsequent ism_dev[0]->lgr_lock dereference in smc_conn_create() faults at offsetof(struct smcd_dev, lgr_lock) == 0x68:

BUG: KASAN: null-ptr-deref in _raw_spin_lock_bh+0x79/0xe0 Write of size 4 at addr 0000000000000068 by task exploit/144 Call Trace: _raw_spin_lock_bh smc_conn_create (net/smc/smc_core.c:1997) __smc_connect (net/smc/af_smc.c:1447) smc_connect (net/smc/af_smc.c:1720) __sys_connect __x64_sys_connect do_syscall_64

Require ism_dev[i] to be non-NULL before accepting a CHID match.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

July 19, 2026

Last Modified

September 2, 2026

Advisory Details (6)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d38ba387244e5c5f7db3e11ea98bc2c7beccb0c0
generic

net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/afa9036b8c9963947b487c36e332df6a42c96fcb
generic

net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6927cacf2b10d4fa80c1a2d407512ef9397c59c6
generic

net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65edb3b0822cfe5041be8fbabebd57e2e5ad9f4e
generic

net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/53eb7bd09aace72fa17510d80e0caf5ca058c231
generic

net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/277740023def559a4a2ddc3e8e784ee37a0f16a9

Vendor Advisories for CVE-2026-64048(4)

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

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-139.139) @ noble2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1067.75) @ noble2026-09-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-18ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
redhatkernel-0:4.18.0-553.157.1.el8_102026-08-20redhat
redhatkernel-0:5.14.0-687.41.1.el9_82026-08-20redhat
redhatkernel-rt-0:4.18.0-553.157.1.rt7.498.el8_102026-08-20redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(8)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 112× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 272 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64048?
CVE-2026-64048 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot On the SMC-D client, slot 0 of ini->ismdev[]/ini->ismchid[] is reserved for an SMC-Dv1 device. smcfindismv2device_clnt() populates V2 entries starting at index 1, so…
When was CVE-2026-64048 disclosed?
CVE-2026-64048 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64048 actively exploited?
CVE-2026-64048 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64048?
CVE-2026-64048 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-64048?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64048, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-64048?

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

Start Free Scan →Browse All CVEs