CVE-2026-64279

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
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.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

i2c: core: fix adapter deregistration race

Adapters can be looked up by their id using i2c_get_adapter() which takes a reference to the embedded struct device.

Remove the adapter from the IDR before tearing it down during deregistration (and on registration failure) to make sure its resources are not accessed after having been freed (e.g. the device name).

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (7)

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

i2c: core: fix adapter deregistration race - kernel/git/stable/linux.git - Linux kernel stable tree

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

i2c: core: fix adapter deregistration race - kernel/git/stable/linux.git - Linux kernel stable tree

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

i2c: core: fix adapter deregistration race - kernel/git/stable/linux.git - Linux kernel stable tree

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

i2c: core: fix adapter deregistration race - kernel/git/stable/linux.git - Linux kernel stable tree

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

i2c: core: fix adapter deregistration race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9882a9bd74db08e7bae5821a7050627ae92d3380
generic

i2c: core: fix adapter deregistration race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35dbd1f1f603401155cbd3a180bb18e3a3b675b8
generic

i2c: core: fix adapter deregistration race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/11dfa37bf544cc806f21742ca2fd2d841bd7032e

Vendor Advisories for CVE-2026-64279(2)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (500 versions)
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 137× 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 166 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64279?
CVE-2026-64279 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: i2c: core: fix adapter deregistration race Adapters can be looked up by their id using i2cgetadapter() which takes a reference to the embedded struct device. Remove the adapter from the IDR before tearing it down during…
When was CVE-2026-64279 disclosed?
CVE-2026-64279 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64279 actively exploited?
CVE-2026-64279 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 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64279?
CVE-2026-64279 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64279?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64279, 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-64279

Explore →

Is Your Infrastructure Affected by CVE-2026-64279?

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