CVE-2026-53400

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. 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

A fix is available — apply it.

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

i2c: core: fix adapter registration race

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

Make sure that the adapter (including its struct device) has been initialised before adding it to the IDR to avoid accessing uninitialised data which could, for example, lead to NULL-pointer dereferences or use-after-free.

Note that the i2c-dev chardev, which is registered from a bus notifier, currently uses i2c_get_adapter() so the adapter needs to be added to the IDR before registration.

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
1%
KEV
Not listed

Published

July 19, 2026

Last Modified

September 8, 2026

Advisory Details (4)

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

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

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

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

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

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

https://git.kernel.org/stable/c/78793c75dc6d0ff2e4d50ad617349b328a99054e
generic

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

https://git.kernel.org/stable/c/6a946038f2a5a8c29048c6af369d4e391448a5c5

Vendor Advisories for CVE-2026-53400(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-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-08ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-08ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-08ubuntu

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.3-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 18× in last 7d / 109× 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 193 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-53400?

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

Start Free Scan →Browse All CVEs