CVE-2026-64048

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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: 0%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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 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(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-20ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-20ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-20ubuntu

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 (138 versions)7.0.12-1—

All Vendor Advisories

(3)

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 38× in last 7d / 154× 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 165 total refreshes for this CVE.

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

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 60.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64048?
CVE-2026-64048 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
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