Full vulnerability report · 2026

CVE-2026-64331High confidence

usbip: vudc: fix NULL deref in vep_dequeue()

Linux · Linux

5.5MediumCVSS 3.1

Recommended action

Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product

Operational reassessment

Published severity in operational context

Open reassessment dashboard →

Published severityMediumOperational priority:Low, lowered one band.downgradedsince 17 Aug 2026

Evidence used

No CISA KEV confirmation is currently recorded.
Exploitation requires an existing local or physical foothold with privileges.
EPSS is 0.12% for the current model date.

Compensating controls

Validate the affected product branch and deploy the verified fixed release.
Restrict local access and enforce least privilege on affected hosts.
Monitor vendor guidance and exploitation sources for a material change.

Verification

Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Canonical Ubuntu Security: 20 affected package states with no published fix

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

25 package states

Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution release	Source package	Vendor state	Fixed version	Evidence
Debian trixietrixie · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.96-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.1.180-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · source	`linux-6.12`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.100-1~deb12u1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`7.1.4-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`7.1.4-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current

CVE-2026-64331 · CSAF 2.0 · revision 14 · interimSUSE Product Security TeamCVE-2026-64331

292 known affected

The vendor explicitly identifies these products as affected by this CVE.

cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5
ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1

Summary: 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
Remediation: To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

Recommended actionPatch only the product branches with a verified fix

Fix availability varies by product

What, why and how

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

What

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → NULL Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-476 ↗
CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

CWE-476

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-48875Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

BSI · German · WID-SEC-2026-2527Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.

Official advisory ↗

Cyber Security Agency of Singapore · English · CSA-SB-20260729Security Bulletin 29 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Jul 2026, published on 29 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64325 https://www.cve.org/CVERecord?id=CVE-2026-64325 Référence CVE CVE-2026-64326 https://www.cve.org/CVERecord?id=CVE-2026-64326 Référence CVE CVE-2026-64327 https://www.cve.org/CVERecord?id=CVE-2026-64327 Référence CVE CVE-2026-64328 https://www.cve.org/CVERecord?id=CVE-2026-64328 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64335 https://www.cve.org/CVERecord?id=CVE-2026-64335 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64337 https://www.cve.org/CVERecord?id=CVE-2026-64337 Référence CVE CVE-2026-64338 https://www.cve.org/CVERecord?id=CVE-2026-64338 Référence CVE CVE-2026-64339 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-64319 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64321 https://www.cve.org/CVERecord?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64326 https://www.cve.org/CVERecord?id=CVE-2026-64326 Référence CVE CVE-2026-64327 https://www.cve.org/CVERecord?id=CVE-2026-64327 Référence CVE CVE-2026-64328 https://www.cve.org/CVERecord?id=CVE-2026-64328 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64335 https://www.cve.org/CVERecord?id=CVE-2026-64335 Référence CVE CVE-2026-64337 https://www.cve.org/CVERecord?id=CVE-2026-64337 Référence CVE CVE-2026-64338 https://www.cve.org/CVERecord?id=CVE-2026-64338 Référence CVE CVE-2026-64340 https://www.cve.org/CVERecord?id=CVE-2026-64340 Référence CVE CVE-2026-64341 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1202Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-64306 Référence CVE CVE-2026-64312 https://www.cve.org/CVERecord?id=CVE-2026-64312 Référence CVE CVE-2026-64313 https://www.cve.org/CVERecord?id=CVE-2026-64313 Référence CVE CVE-2026-64315 https://www.cve.org/CVERecord?id=CVE-2026-64315 Référence CVE CVE-2026-64316 https://www.cve.org/CVERecord?id=CVE-2026-64316 Référence CVE CVE-2026-64317 https://www.cve.org/CVERecord?id=CVE-2026-64317 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64335 https://www.cve.org/CVERecord?id=CVE-2026-64335 Référence CVE CVE-2026-64337 https://www.cve.org/CVERecord?id=CVE-2026-64337 Référence CVE CVE-2026-64338 https://www.cve.org/CVERecord?id=CVE-2026-64338 Référence CVE CVE-2026-64340 https://www.cve.org/CVERecord?id=CVE-2026-64340 Référence CVE CVE-2026-64341 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1164Multiples vulnérabilités dans le noyau Linux de SUSE

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1031Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64326 https://www.cve.org/CVERecord?id=CVE-2026-64326 Référence CVE CVE-2026-64327 https://www.cve.org/CVERecord?id=CVE-2026-64327 Référence CVE CVE-2026-64328 https://www.cve.org/CVERecord?id=CVE-2026-64328 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64335 https://www.cve.org/CVERecord?id=CVE-2026-64335 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64337 https://www.cve.org/CVERecord?id=CVE-2026-64337 Référence CVE CVE-2026-64338 https://www.cve.org/CVERecord?id=CVE-2026-64338 Référence CVE CVE-2026-64340 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0982Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-64315 Référence CVE CVE-2026-64316 https://www.cve.org/CVERecord?id=CVE-2026-64316 Référence CVE CVE-2026-64317 https://www.cve.org/CVERecord?id=CVE-2026-64317 Référence CVE CVE-2026-64318 https://www.cve.org/CVERecord?id=CVE-2026-64318 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64335 https://www.cve.org/CVERecord?id=CVE-2026-64335 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64337 https://www.cve.org/CVERecord?id=CVE-2026-64337 Référence CVE CVE-2026-64338 https://www.cve.org/CVERecord?id=CVE-2026-64338 Référence CVE CVE-2026-64340 https://www.cve.org/CVERecord?id=

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2026-032046LinuxのLinux KernelにおけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。usbipのvudcにおけるvep_dequeue()内のNULL参照の問題です。vep_alloc_request()がvrequest-＞udcを初期化していなかったため、FunctionFSのAIOパスでのキャンセル処理が、有効なUDC参照なしにvep_dequeueに到達していました。vrequest-＞udcは実際にはどこでも正しく使用されていなかったため、これを削除し、他のvep_操作との整合性を取るために、vep_dequeueをep_to_vudc()を使ってudcの参照を取得するよう更新しました。このバグは約10年間存在していたと考えられます。usbipのvudcでFunctionFSのAIOパスを本格的にストレステストした人はほとんどいなかったようです。私はこの修正をQEMUのaarch64ゲスト環境でFunctionFSエンドポイントをAIO経由で操作してテストしました。修正前は、ホストから「usbip attach」を実行すると、ゲストが次のバックトレース付きでカーネルパニック（oops）を起こしていました。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

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Fix availability varies by product
Affected: cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5
ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP2
reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP3
and 262 more
Fixed: Linux: < 4.7, 5.10.261 ≤ 5.10.*, 5.15.212 ≤ 5.15.*, 6.1.178 ≤ 6.1.*, 6.6.145 ≤ 6.6.*, 6.12.96 ≤ 6.12.*, 6.18.39 ≤ 6.18.*, 7.1.4 ≤ 7.1.*, 7.2 ≤ *
Action: Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 25 Jul 2026 · Last source change 17 Aug 2026, 04:53 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2026-48875

Product sourceVendor CSAF · SUSE Product Security Team

Remediation sourceVendor CSAF · SUSE Product Security Team

CWE sourceNIST NVD

NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

17 Aug 2026, 04:53 UTC
Vendor guidanceAuthoritative vendor guidance changed: added patch: git.kernel.org/0025276175fbbe0dcbf3f84d090b0adee769e9d9; added patch: git.kernel.org/0443e4416aa1ee97748d1ed904eaf3352c60045e; 6 further additions.
Before
remediation: git.kernel.org/9858c91d9ee6a13c45311569039413729fc9b757
After
patch: git.kernel.org/0025276175fbbe0dcbf3f84d090b0adee769e9d9 · patch: git.kernel.org/0443e4416aa1ee97748d1ed904eaf3352c60045e · patch: git.kernel.org/1226293ec9bed3d4cc5b05eeeb811d315ca51652 · 6 more references
git.kernel.org ↗
17 Aug 2026, 04:53 UTC
SeveritySeverity changed from Unknown to Medium.
Before
Unknown
After
Medium
NIST NVD ↗
17 Aug 2026, 04:53 UTC
CVSS scoreCVSS score changed from not recorded to 5.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
Before
not recorded
After
5.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
NIST NVD ↗

2026-07-25CVE published

2026-08-17Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-48875↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

usbip: vudc: fix NULL deref in vep_dequeue()

Published severity in operational context

Evidence used

Compensating controls

Verification

Remediation availability differs by product scope

Release-specific package status

Authoritative vendor CSAF and VEX advisories

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2026-48875

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication