Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-35825: usb: gadget: ncm: Fix handling of zero block length packets

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 4.15, 4.19.312, 5.10.215.

Low priority for now. Upgrade to Linux Linux 4.15, 4.19.312, 5.10.215 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: ncm: Fix handling of zero block length packets While connecting to a Linux host with CDC_NCM_NTB_DEF_SIZE_TX set to 65536, it has been observed that we receive short packets, which come at interval of 5-10 seconds sometimes and have block length zero but still contain 1-2 valid datagrams present. According to the NCM spec: "If wBlockLength = 0x0000, the block is terminated by a short packet. In this case, the USB transfer must still be shorter than dwNtbInMaxSize or dwNtbOutMaxSize. If exactly dwNtbInMaxSize or dwNtbOutMaxSize bytes are sent, and the size is a multiple of wMaxPacketSize for the given pipe, then no ZLP shall be sent. wBlockLength= 0x0000 must be used with extreme care, because of the possibility that the host and device may get out of sync, and because of test issues. wBlockLength = 0x0000 allows the sender to reduce latency by starting to send a very large NTB, and then shortening it when the sender discovers that there’s not sufficient data to justify sending a large NTB" However, there is a potential issue with the current implementation, as it checks for the occurrence of multiple NTBs in a single giveback by verifying if the leftover bytes to be processed is zero or not. If the block length reads zero, we would process the same NTB infintely because the leftover bytes is never zero and it leads to a crash. Fix this by bailing out if block length reads zero.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 17, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-35825

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel4.19.297 and later · before 4.19.312
  • linux linux kernel5.4.259 and later · before 5.4.274
  • linux linux kernel5.10.199 and later · before 5.10.215
  • linux linux kernel5.15.136 and later · before 5.15.154
  • linux linux kernel6.1.59 and later · before 6.1.84
  • linux linux kernel4.14.328 and later · before 4.15
  • linux linux kernel6.6.1 and later · before 6.6.24
  • linux linux kernel6.7 and later · before 6.7.12
  • linux linux kernel6.5.8 and later · before 6.6
  • linux linux kernel6.6
  • linux linux kernel6.8

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5bdf93a2f5459f944b416b188178ca4a92fd206f, 4bf1a9d20c65b9e80ca4b171267103f8d4f2c61f, 6.6affected
    • ff3ba016263ee93a1c6209bf5ab1599de7ab1512 and later · before e2dbfea520e60d58e0c498ba41bde10452257779affected · git
    • e7ca00f35d8a17af1ae19d529193ebc21bfda164 and later · before a766761d206e7c36d7526e0ae749949d17ca582caffected · git
    • 17c653d4913bbc50d284aa96cf12bfc63e41ee5c and later · before ef846cdbd100f7f9dc045e8bcd7fe4b3a3713c03affected · git
    • 7014807fb7efa169a47a7a0a0a41d2c513925de0 and later · before 92b051b87658df7649ffcdef522593f21a2b296baffected · git
    • 49fbc18378ae72a47feabee97fdb86f3cea09765 and later · before 7664ee8bd80309b90d53488b619764f0a057f2b7affected · git
    • 427694cfaafa565a3db5c5ea71df6bc095dca92f and later · before a0f77b5d6067285b8eca0ee3bd1e448a6258026faffected · git
    • 427694cfaafa565a3db5c5ea71df6bc095dca92f and later · before 6b2c73111a252263807b7598682663dc33aa4b4caffected · git
    • 427694cfaafa565a3db5c5ea71df6bc095dca92f and later · before f90ce1e04cbcc76639d6cba0fdbd820cd80b3c70affected · git
    • 4.19.297 and later · before 4.19.312affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.85-16.1.85-1
Debian:13linuxbefore 6.7.12-16.7.12-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-35822May 17, 2024 · usb: udc: remove warning when queue disabled ep
    22Monitor
  • ← EarlierCVE-2024-35824May 17, 2024 · misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume
    22Monitor
  • Later →CVE-2024-35826May 17, 2024 · block: Fix page refcounts for unaligned buffers in __bio_release_pages()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux4.15Vendor (CNA)
Linux Linux4.19.312Vendor (CNA)
Linux Linux5.10.215Vendor (CNA)
Linux Linux5.15.154Vendor (CNA)
Linux Linux5.4.274Vendor (CNA)
Linux Linux6.1.84Vendor (CNA)
Linux Linux6.6Vendor (CNA)
Linux Linux6b2c73111a252263807b7598682663dc33aa4b4cVendor (CNA)
Linux Linux7664ee8bd80309b90d53488b619764f0a057f2b7Vendor (CNA)
Linux Linux92b051b87658df7649ffcdef522593f21a2b296bVendor (CNA)
Linux Linuxa0f77b5d6067285b8eca0ee3bd1e448a6258026fVendor (CNA)
Linux Linuxa766761d206e7c36d7526e0ae749949d17ca582cVendor (CNA)
Linux Linuxe2dbfea520e60d58e0c498ba41bde10452257779Vendor (CNA)
Linux Linuxef846cdbd100f7f9dc045e8bcd7fe4b3a3713c03Vendor (CNA)
Linux Linuxf90ce1e04cbcc76639d6cba0fdbd820cd80b3c70Vendor (CNA)
debian:linux6.1.85-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records