Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-74679usb: gadget: f_ncm: Use unsigned int for ndp_index

Description

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_ncm: Use unsigned int for ndp_index The variable ndp_index is declared as a signed integer, but it stores the return value of get_ncm(), which is unsigned. A malicious host can supply a large offset that overflows the signed ndp_index, making it negative. Because ndp_index is compared against unsigned bounds, this negative value bypasses sanity checks and leads to an out-of-bounds read when calculating the address of the NDP block (ntb_ptr + ndp_index). Fix this by changing ndp_index to unsigned int to ensure consistent unsigned comparisons throughout the function.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 370af734dfaf8336b496b386e194648e097e248a – < 9c8c6825a750fcd3efbe922847ca70ccd5a66857
    • affected 370af734dfaf8336b496b386e194648e097e248a – < a1c0deeba4a46481543d6b09c665f758c54c3a1a
    • affected 370af734dfaf8336b496b386e194648e097e248a – < d13f650a3485b58c124b3cda45597e8002c9c833
    • affected 370af734dfaf8336b496b386e194648e097e248a – < 11413d7ed42174b8f5d8d0b6a25d10dc88239b21
    • affected 370af734dfaf8336b496b386e194648e097e248a – < 5b2b3a3229a3f4c493ffdee53aee2f173b6f13b3
    • affected 370af734dfaf8336b496b386e194648e097e248a – < d328fdc607fa1bb668ad512e1c918a120f78f337
    • affected 370af734dfaf8336b496b386e194648e097e248a – < fc9e54e22845c4da29588ca0986cb7c795b5a262
    • affected 370af734dfaf8336b496b386e194648e097e248a – < 6b1c8a9403a26cb0fed7a648916c74dc236da591
  • Linux · Linux

    • affected 3.17
    • unaffected < 3.17
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.152 – ≤ 6.6.*
    • unaffected 6.12.104 – ≤ 6.12.*
    • unaffected 6.18.45 – ≤ 6.18.*
    • unaffected 7.1.9 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74679 badge
[![CVE-2026-74679](https://cveledger.app/badge/CVE-2026-74679.svg)](https://cveledger.app/cve/CVE-2026-74679)

Record last updated .