CVE-2026-68368

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: 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: gadget: f_ncm: validate datagram bounds in ncm_unwrap_ntb()

When unpacking host-supplied NTBs, ncm_unwrap_ntb() checks datagram length against frame_max but does not verify that the datagram fits within the declared block length. Additionally, when decoding multiple NTBs from a single socket buffer, subsequent block lengths are not checked against the actual remaining buffer data.

With these checks missing, a malicious USB host can specify datagram offsets and lengths that point beyond the block, or supply secondary NTB headers declaring lengths larger than the buffer. skb_put_data() then copies adjacent kernel memory from skb_shared_info into the network skb.

Fix this by verifying that sufficient buffer space remains for the NTB header before parsing, handling zero-length block declarations, ensuring that block lengths never exceed the remaining buffer space, and verifying that each datagram payload stays strictly within the block boundary.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Vendor Advisories for CVE-2026-68368(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 16× in last 7d / 23× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-19 17:50 UTCGHSA enrichment
  3. 2026-08-19 17:31 UTCNVD update
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 16:54 UTCGHSA enrichment
  6. 2026-08-19 16:43 UTCMITRE cvelistV5
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 06:32 UTCGHSA enrichment
  11. 2026-08-17 06:18 UTCNVD update
  12. 2026-08-17 05:36 UTCGHSA enrichment
  13. 2026-08-17 05:24 UTCMITRE cvelistV5
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 13:58 UTCGHSA enrichment
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 13:41 UTCEG score recompute
  19. 2026-08-13 13:41 UTCGHSA enrichment
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-10 13:24 UTCNVD update
  22. 2026-08-10 12:18 UTCEG score recompute
  23. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-68368?
CVE-2026-68368 is a publicly disclosed vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: usb: gadget: fncm: validate datagram bounds in ncmunwrap_ntb() When unpacking host-supplied NTBs, ncmunwrapntb() checks datagram length against frame_max but does not verify that the datagram fits within the declared block length.…
When was CVE-2026-68368 disclosed?
CVE-2026-68368 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68368 actively exploited?
CVE-2026-68368 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 88.4% of all scored CVEs.
How do I remediate CVE-2026-68368?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68368, 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-68368

Explore →

Is Your Infrastructure Affected by CVE-2026-68368?

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