Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64331: usbip: vudc: fix NULL deref in vep_dequeue()

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.12% (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 0025276175fbbe0dcbf3f84d090b0adee769e9d9, 0443e4416aa1ee97748d1ed904eaf3352c60045e, 1226293ec9bed3d4cc5b05eeeb811d315ca51652.

Low priority for now. Upgrade to Linux Linux 0025276175fbbe0dcbf3f84d090b0adee769e9d9, 0443e4416aa1ee97748d1ed904eaf3352c60045e, 1226293ec9bed3d4cc5b05eeeb811d315ca51652 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: usbip: vudc: fix NULL deref in vep_dequeue() vep_alloc_request() wasn't initializing vrequest->udc, so cancellations on the FunctionFS AIO path were arriving in vep_dequeue without a valid UDC reference. Since vrequest->udc is never actually properly used anywhere, we opt to remove it, and update vep_dequeue to obtain a reference to the udc with ep_to_vudc(), consistent with the other vep_ ops. AFAICT this bug has existed for ~10 years. Seems that nobody has really stressed the FunctionFS AIO path on usbip's vudc. I tested this fix in a QEMU aarch64 guest driving FunctionFS endpoints via AIO. Before the fix, running `usbip attach` from the host would cause the guest to oops with the following backtrace: Call trace: vep_dequeue+0x1c/0xe4 (P) usb_ep_dequeue+0x14/0x20 ffs_aio_cancel+0x24/0x34 __arm64_sys_io_cancel+0xb0/0x124 do_el0_svc+0x68/0x100 el0_svc+0x18/0x5c el0t_64_sync_handler+0x98/0xdc el0t_64_sync+0x154/0x158

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jul 25, 2026
Updated
Nov 6, 2026
EPSS
0.1% · 2th percentile

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.1%

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-2026-64331

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

Affected versions

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

  • linux linux kernel4.7 and later · before 5.10.261
  • linux linux kernel5.11 and later · before 5.15.212
  • linux linux kernel5.16 and later · before 6.1.178
  • linux linux kernel6.2 and later · before 6.6.145
  • linux linux kernel6.7 and later · before 6.12.96
  • linux linux kernel6.13 and later · before 6.18.39
  • linux linux kernel6.19 and later · before 7.1.4
  • linux linux kernel7.2

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

    • 4.7affected
    • b6a0ca11186759ad7045d68a5447b1e89f658384 and later · before 9858c91d9ee6a13c45311569039413729fc9b757affected · git
    • b6a0ca11186759ad7045d68a5447b1e89f658384 and later · before 1226293ec9bed3d4cc5b05eeeb811d315ca51652affected · git
    • b6a0ca11186759ad7045d68a5447b1e89f658384 and later · before 3750f75f29f99c0223601e2ee73ad084adec47bdaffected · git
    • b6a0ca11186759ad7045d68a5447b1e89f658384 and later · before d0ebf9cc7c2ddf95a7cfc654b940bdacb7edde97affected · git
    • b6a0ca11186759ad7045d68a5447b1e89f658384 and later · before 0025276175fbbe0dcbf3f84d090b0adee769e9d9affected · git
    • b6a0ca11186759ad7045d68a5447b1e89f658384 and later · before 347b59e9f96719d89b6ef555d02a18ada1a5846faffected · git
    • b6a0ca11186759ad7045d68a5447b1e89f658384 and later · before 0443e4416aa1ee97748d1ed904eaf3352c60045eaffected · git
    • b6a0ca11186759ad7045d68a5447b1e89f658384 and later · before c5371e0b91b24159a3ebaa61e70b0980bcf03c0aaffected · git
    • before 4.7not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.96-16.12.96-1
Debian:14linuxbefore 7.1.4-17.1.4-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-2026-64329Jul 25, 2026 · usb: typec: ucsi: ccg: Fix use-after-free of ucsi on remove
    31Monitor
  • ← EarlierCVE-2026-64330Jul 25, 2026 · usb: typec: tcpm: Validate SVID index in svdm_consume_modes()
    31Monitor
  • Later →CVE-2026-64332Jul 25, 2026 · USB: ulpi: fix memory leak on registration failure
    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 Linux0025276175fbbe0dcbf3f84d090b0adee769e9d9Vendor (CNA)
Linux Linux0443e4416aa1ee97748d1ed904eaf3352c60045eVendor (CNA)
Linux Linux1226293ec9bed3d4cc5b05eeeb811d315ca51652Vendor (CNA)
Linux Linux347b59e9f96719d89b6ef555d02a18ada1a5846fVendor (CNA)
Linux Linux3750f75f29f99c0223601e2ee73ad084adec47bdVendor (CNA)
Linux Linux9858c91d9ee6a13c45311569039413729fc9b757Vendor (CNA)
Linux Linuxc5371e0b91b24159a3ebaa61e70b0980bcf03c0aVendor (CNA)
Linux Linuxd0ebf9cc7c2ddf95a7cfc654b940bdacb7edde97Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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

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. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

All records