CVE-2026-53400

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH 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 — 3 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 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(high)
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 19, 2026

Last Modified

July 24, 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.

Data Freshness Timeline

(refreshed 15× in last 7d / 21× 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.

  1. 2026-07-27 05:41 UTCGHSA enrichment
  2. 2026-07-26 16:57 UTCEG score recompute
  3. 2026-07-26 16:56 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 04:32 UTCEG score recompute
  6. 2026-07-26 04:32 UTCGHSA enrichment
  7. 2026-07-25 14:18 UTCEPSS rescore
  8. 2026-07-24 14:18 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:19 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:25 UTCEPSS rescore
  13. 2026-07-20 17:47 UTCEG score recompute
  14. 2026-07-20 17:47 UTCGHSA enrichment
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-20 14:47 UTCEG score recompute▲ 7.80
  17. 2026-07-20 14:46 UTCGHSA enrichment
  18. 2026-07-20 14:32 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  19. 2026-07-19 12:26 UTCNVD update
  20. 2026-07-19 12:15 UTCEG score recompute
  21. 2026-07-19 12:10 UTCMITRE cvelistV5first tracked

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 July 24, 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 97.1% 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

Explore the affected products and dependency analysis for 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