CVE-2026-74639: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-74639 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.
CVE-2026-74639 at a Glance
How to Fix CVE-2026-74639
To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-74639, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree
Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
References
Frequently Asked Questions
What is CVE-2026-74639?
Which Software versions are affected?
What version fixes CVE-2026-74639?
What CWE is associated with CVE-2026-74639?
How can I check Maven dependencies for CVE-2026-74639?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-hx28-f548-xhmf",
"modified" : "2026-08-22T18:30:27Z",
"published" : "2026-08-22T18:30:27Z",
"aliases" : [ "CVE-2026-74639" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: us144mkii: re-anchor capture URBs on resubmission\n\ncapture_urb_complete() resubmits each capture URB without anchoring it:\n\n\tusb_get_urb(urb);\n\tret = usb_submit_urb(urb, GFP_ATOMIC);\n\nAnchoring is a property of a submission, not of the URB. The giveback\npath calls usb_unanchor_urb() before urb->complete(), so an URB\nresubmitted from its own completion handler is off the anchor. The\ncapture URBs are anchored once, at stream start, so from the first\ncompletion onward tascam->capture_anchor is empty.\n\ntascam_free_urbs(), tascam_disconnect(), tascam_suspend() and the\nstop-work path all call usb_kill_anchored_urbs(&tascam->capture_anchor)\nto reap the capture URBs before anything is freed. With the anchor empty\nthose calls return immediately and the URBs stay queued on the host\ncontroller.\n\ntascam_free_urbs() then returns the capture transfer buffers with\nusb_free_coherent(), and snd_card_free() releases the snd_card\nallocation that embeds tascam (card->private_data). The controller\ncompletes the queued URBs afterwards, writing device-supplied data into\nthe freed transfer buffer, and capture_urb_complete() dereferences the\nfreed driver object.\n\nKASAN on 7.2.0-rc5 (arm64):\n\n BUG: KASAN: slab-use-after-free in dummy_timer\n Write of size 512 at addr ffff000015b62000\n __asan_memcpy\n dummy_timer\n hrtimer_run_softirq\n Allocated by task 64:\n usb_alloc_coherent\n tascam_alloc_urbs\n tascam_probe\n Freed by task 170:\n usb_free_coherent\n tascam_free_urbs\n tascam_disconnect\n usb_unbind_interface\n\n BUG: KASAN: slab-use-after-free in capture_urb_complete\n Read of size 4 at addr ffff0000170ee878\n Freed by task 170:\n release_card_device\n snd_card_free\n tascam_disconnect\n\nRestore the usb_anchor_urb() between the reference count bump and the\nresubmission. That also makes the handler's usb_unanchor_urb() failure\narm meaningful again and restores usb_kill_anchored_urbs() as a barrier\non the disconnect, suspend and stop-work paths.\n\nThe anchoring was removed on the premise that the URB is already anchored\nfrom the initial submission, which does not hold once the first giveback\nhas run.\n\nDiscovered by XBOW, triaged by Baul Lee <baul.lee@xbow.com>",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-74639"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/2615f0fb90df8cf5a96133ca4be74294ed288604"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/7779249561d14b8a17c0c83783225794e24a587d"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/a5548ce916594c811bd90ce33d67baa3557a6791"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-22T16:16:37Z"
}
}