CVE-2026-68371

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: 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:

usb: musb: omap2430: Do not put borrowed of_node in probe

omap2430_probe() stores pdev->dev.of_node in a local np variable. This is a borrowed pointer and the probe function does not take a reference to it.

The success and error paths nevertheless call of_node_put(np). This drops a reference that is owned by the platform device, and can leave pdev->dev.of_node with an unbalanced reference count.

Do not put the borrowed platform device node from omap2430_probe(). References taken for the child MUSB device are handled by the device core, and the ctrl-module phandle reference is still released separately.

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

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

usb: musb: omap2430: Do not put borrowed of_node in probe - kernel/git/stable/linux.git - Linux kernel stable tree

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

usb: musb: omap2430: Do not put borrowed of_node in probe - kernel/git/stable/linux.git - Linux kernel stable tree

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

usb: musb: omap2430: Do not put borrowed of_node in probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6c525c851e5912b9753622d796f2bc55c4913b04
generic

usb: musb: omap2430: Do not put borrowed of_node in probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/58d1c81c0b54a0b9aa6d6af077b09aa2f1bd2193
generic

usb: musb: omap2430: Do not put borrowed of_node in probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0950ac52426b0ab32d3b8cf4afe1711668b19cb8

Vendor Advisories for CVE-2026-68371(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 33× in last 7d / 45× 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-08-21 05:38 UTCEG score recompute
  2. 2026-08-21 05:38 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 18:00 UTCGHSA enrichment
  5. 2026-08-20 06:22 UTCGHSA enrichment
  6. 2026-08-19 18:44 UTCEG score recompute
  7. 2026-08-19 18:44 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 06:23 UTCGHSA enrichment
  10. 2026-08-18 18:35 UTCEG score recompute
  11. 2026-08-18 18:35 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 06:57 UTCGHSA enrichment
  15. 2026-08-17 19:19 UTCEG score recompute
  16. 2026-08-17 19:19 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:32 UTCEG score recompute
  19. 2026-08-17 06:32 UTCGHSA enrichment
  20. 2026-08-17 05:36 UTCEG score recompute
  21. 2026-08-17 05:36 UTCGHSA enrichment
  22. 2026-08-16 21:31 UTCEG score recompute
  23. 2026-08-16 21:31 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 09:53 UTCEG score recompute
Show 20 more
  1. 2026-08-16 09:53 UTCGHSA enrichment
  2. 2026-08-15 22:16 UTCGHSA enrichment
  3. 2026-08-15 10:38 UTCEG score recompute
  4. 2026-08-15 10:38 UTCGHSA enrichment
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 23:00 UTCGHSA enrichment
  7. 2026-08-14 11:22 UTCEG score recompute
  8. 2026-08-14 11:22 UTCGHSA enrichment
  9. 2026-08-13 23:45 UTCEG score recompute
  10. 2026-08-13 23:45 UTCGHSA enrichment
  11. 2026-08-13 23:04 UTCEG score recompute▲ 8.40
  12. 2026-08-13 23:04 UTCGHSA enrichment
  13. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 18:27 UTCEG score recompute
  16. 2026-08-13 18:27 UTCGHSA enrichment
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-10 13:24 UTCNVD update
  19. 2026-08-10 12:18 UTCEG score recompute
  20. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68371?
CVE-2026-68371 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: usb: musb: omap2430: Do not put borrowed of_node in probe omap2430probe() stores pdev->dev.ofnode in a local np variable. This is a borrowed pointer and the probe function does not take a reference to it. The success and error…
When was CVE-2026-68371 disclosed?
CVE-2026-68371 was first published in the National Vulnerability Database on August 10, 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-68371 actively exploited?
CVE-2026-68371 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 91.9% of all scored CVEs.
What is the CVSS score of CVE-2026-68371?
CVE-2026-68371 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-68371?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68371, 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-68371

Explore →

Is Your Infrastructure Affected by CVE-2026-68371?

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

Start Free Scan →Browse All CVEs