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… (CVE-2026-74679)
A vulnerability in the Linux kernel's USB gadget function f_ncm involves the use of a signed integer variable ndp_index to store an unsigned return value. This mismatch allows a malicious host to supply a large offset that causes ndp_index to overflow and become negative. Because ndp_index is then compared against unsigned bounds, this negative value bypasses sanity checks, leading to an out-of-bounds read when calculating the address of the NDP block. The issue is resolved by changing ndp_index to an unsigned int to ensure consistent unsigned comparisons.
AI Analysis
Technical Summary
The Linux kernel's USB gadget function f_ncm used a signed integer variable ndp_index to store the return value of get_ncm(), which is unsigned. This type mismatch allows a malicious host to provide a large offset that overflows ndp_index, making it negative. Since ndp_index is compared against unsigned bounds, the negative value bypasses sanity checks, resulting in an out-of-bounds read when computing the NDP block address (ntb_ptr + ndp_index). The vulnerability is fixed by changing ndp_index to unsigned int, ensuring consistent unsigned comparisons throughout the function.
Potential Impact
A malicious host can exploit this vulnerability to cause an out-of-bounds read in the Linux kernel's USB gadget f_ncm function. This could potentially lead to information disclosure or kernel memory corruption depending on how the out-of-bounds read is leveraged. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix for this vulnerability has been implemented by changing the ndp_index variable from signed int to unsigned int in the Linux kernel source code. Users should apply the official Linux kernel updates that include this fix once available. Patch status is not yet confirmed; check the vendor advisory for current remediation guidance.
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… (CVE-2026-74679)
Description
A vulnerability in the Linux kernel's USB gadget function f_ncm involves the use of a signed integer variable ndp_index to store an unsigned return value. This mismatch allows a malicious host to supply a large offset that causes ndp_index to overflow and become negative. Because ndp_index is then compared against unsigned bounds, this negative value bypasses sanity checks, leading to an out-of-bounds read when calculating the address of the NDP block. The issue is resolved by changing ndp_index to an unsigned int to ensure consistent unsigned comparisons.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's USB gadget function f_ncm used a signed integer variable ndp_index to store the return value of get_ncm(), which is unsigned. This type mismatch allows a malicious host to provide a large offset that overflows ndp_index, making it negative. Since ndp_index is compared against unsigned bounds, the negative value bypasses sanity checks, resulting in an out-of-bounds read when computing the NDP block address (ntb_ptr + ndp_index). The vulnerability is fixed by changing ndp_index to unsigned int, ensuring consistent unsigned comparisons throughout the function.
Potential Impact
A malicious host can exploit this vulnerability to cause an out-of-bounds read in the Linux kernel's USB gadget f_ncm function. This could potentially lead to information disclosure or kernel memory corruption depending on how the out-of-bounds read is leveraged. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix for this vulnerability has been implemented by changing the ndp_index variable from signed int to unsigned int in the Linux kernel source code. Users should apply the official Linux kernel updates that include this fix once available. Patch status is not yet confirmed; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6qhg-x625-34c5
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74679"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f1acd9273b499bc77a
Added to database: 08/22/2026, 22:51:29 UTC
Last enriched: 08/23/2026, 00:24:02 UTC
Last updated: 08/23/2026, 01:32:13 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.