CVE-2026-31617

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-04-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: 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 minimum block_len in ncm_unwrap_ntb()

The block_len read from the host-supplied NTB header is checked against ntb_max but has no lower bound. When block_len is smaller than opts->ndp_size, the bounds check of: ndp_index > (block_len - opts->ndp_size) will underflow producing a huge unsigned value that ndp_index can never exceed, defeating the check entirely.

The same underflow occurs in the datagram index checks against block_len

  • opts->dpe_size. With those checks neutered, a malicious USB host can
choose ndp_index and datagram offsets that point past the actual transfer, and the skb_put_data() copies adjacent kernel memory into the network skb.

Fix this by rejecting block lengths that cannot hold at least the NTB header plus one NDP. This will make block_len - opts->ndp_size and block_len - opts->dpe_size both well-defined.

Commit 8d2b1a1ec9f5 ("CDC-NCM: avoid overflow in sanity checking") fixed a related class of issues on the host side of NCM.

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

Published

April 24, 2026

Last Modified

August 6, 2026

Advisory Details (10)

Auto-updated Jul 19, 2026
Patch available. Sources: redhat.
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-31617
generic

usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() - kernel/git/stable/linux.git - Linux kernel stable tree

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

usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8f993d30b95dc9557a8a96ceca11abed674c8acb
generic

usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b3b7bd3c02f98634baaf36c7fc7ac915f6517ca
generic

usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8757a2593631443648218244b9788e193ae0fdc1
generic

usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/74908b0318d1df1188457040b8714ff4d4b68126
generic

usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6762f8a95772265dd0c2ffe7f400493f3115b135
generic

usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1425655c2870054c3ab4712e2b6dbdd331597ada
generic

usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0f156bb5334e588034ca68ac2ee92b23f66e56e7
generic

usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/068a7f2749fff6462a0a908ec415b885fe430f50

Vendor Advisories for CVE-2026-31617(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.258—osv

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 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (127 versions)6.19.14-1—

Weakness Classification(1)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31617?
CVE-2026-31617 is a medium vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: usb: gadget: fncm: validate minimum blocklen in ncmunwrapntb() The block_len read from the host-supplied NTB header is checked against ntbmax but has no lower bound. When blocklen is smaller than opts->ndp_size, the bounds check…
When was CVE-2026-31617 disclosed?
CVE-2026-31617 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31617 actively exploited?
CVE-2026-31617 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-31617?
CVE-2026-31617 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31617?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31617, 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-31617

Explore →

Is Your Infrastructure Affected by CVE-2026-31617?

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

Start Free Scan →Browse All CVEs