Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-74639— ALSA: us144mkii: re-anchor capture URBs on resubmission

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

在 Linux 内核中,已修复以下漏洞: ALSA: us144mkii:在重新提交(resubmission)时重新锚定捕获 URB 在重新提交每个捕获 URB 时未进行锚定操作: 锚定(anchoring)是提交操作的一个属性,而非 URB 本身的属性。在“给出”(giveback)路径中,会在调用 之前调用 ,因此从 URB 自身完成处理函数重新提交的 URB 将不再处于锚定状态。捕获 URB 仅在流启动时锚定一次,因此从第一次完成之后, 即为空。 、 、 以及停止工作路径(stop-work path)均会

AI Predicted 6.5 Difficulty: Moderate EPSS 0.21% · P11

Possible ATT&CK Techniques 1 AI

T1068 · Exploitation for Privilege Escalation

Affected Version Matrix 5

VendorProduct Version RangeStatus
Linux Linux 16f14f55141d4c55c3f321f93c328fff7cd6860a< 7779249561d14b8a17c0c83783225794e24a587d affected
ab1db64912428cdf06a4f9542e16e0575e9ad59f< a5548ce916594c811bd90ce33d67baa3557a6791 affected
5cff1529a2f9b3461a7f5a6e36a86682fc290534< 2615f0fb90df8cf5a96133ca4be74294ed288604 affected
6.18.39< 6.18.45 affected
7.1.4< 7.1.9 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-74639

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
ALSA: us144mkii: re-anchor capture URBs on resubmission
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: ALSA: us144mkii: re-anchor capture URBs on resubmission capture_urb_complete() resubmits each capture URB without anchoring it: usb_get_urb(urb); ret = usb_submit_urb(urb, GFP_ATOMIC); Anchoring is a property of a submission, not of the URB. The giveback path calls usb_unanchor_urb() before urb->complete(), so an URB resubmitted from its own completion handler is off the anchor. The capture URBs are anchored once, at stream start, so from the first completion onward tascam->capture_anchor is empty. tascam_free_urbs(), tascam_disconnect(), tascam_suspend() and the stop-work path all call usb_kill_anchored_urbs(&tascam->capture_anchor) to reap the capture URBs before anything is freed. With the anchor empty those calls return immediately and the URBs stay queued on the host controller. tascam_free_urbs() then returns the capture transfer buffers with usb_free_coherent(), and snd_card_free() releases the snd_card allocation that embeds tascam (card->private_data). The controller completes the queued URBs afterwards, writing device-supplied data into the freed transfer buffer, and capture_urb_complete() dereferences the freed driver object. KASAN on 7.2.0-rc5 (arm64): BUG: KASAN: slab-use-after-free in dummy_timer Write of size 512 at addr ffff000015b62000 __asan_memcpy dummy_timer hrtimer_run_softirq Allocated by task 64: usb_alloc_coherent tascam_alloc_urbs tascam_probe Freed by task 170: usb_free_coherent tascam_free_urbs tascam_disconnect usb_unbind_interface BUG: KASAN: slab-use-after-free in capture_urb_complete Read of size 4 at addr ffff0000170ee878 Freed by task 170: release_card_device snd_card_free tascam_disconnect Restore the usb_anchor_urb() between the reference count bump and the resubmission. That also makes the handler's usb_unanchor_urb() failure arm meaningful again and restores usb_kill_anchored_urbs() as a barrier on the disconnect, suspend and stop-work paths. The anchoring was removed on the premise that the URB is already anchored from the initial submission, which does not hold once the first giveback has run. Discovered by XBOW, triaged by Baul Lee <baul.lee@xbow.com>
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux 16f14f55141d4c55c3f321f93c328fff7cd6860a ~ 7779249561d14b8a17c0c83783225794e24a587d -
Linux Linux 6.18.39 ~ 6.18.45 -

II. Public POCs for CVE-2026-74639

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-74639

登录查看更多情报信息。

Patches & Fixes for CVE-2026-74639 (3)

Same Patch Batch · Linux · 2026-08-22 · 150 CVEs total

CVE-2026-74640 ALSA: FCP: fix OOB write in fcp_meter_ctl_get()
CVE-2026-74621 net/sched: act_ct: fix sk_buff leak when the header checks reject a packet
CVE-2026-74622 net: atlantic: free RX pages of consumed but not refilled buffers
CVE-2026-74623 net: atlantic: free stranded TX buffers on ring deinit
CVE-2026-74624 netfilter: nf_conntrack: defer invalid log until after unlock
CVE-2026-74625 netfilter: bridge: release template ct on non-IP path
CVE-2026-74627 net: devmem: prevent net-iov / page mixing
CVE-2026-74626 NTB: ntb_netdev: Preserve RX queue depth on allocation failure
CVE-2026-74628 net/x25: fix use-after-free of the socket by its timers
CVE-2026-74629 net/dibs: Correct freeing of dmb_clientid_arr
CVE-2026-74631 net: smc: fix splice entry lifetime imbalance in smc_rx_splice
CVE-2026-74630 ipv6: prevent in6_dev_get() from resurrecting inet6_dev
CVE-2026-74632 mm/huge_memory: fix huge_zero_pfn race
CVE-2026-74633 tracing: Fix NULL pointer dereference in module event cache removal
CVE-2026-74634 ring-buffer: Prevent subbuf order change when resizing is disabled
CVE-2026-74635 fbdev: bitblit: bound-check glyph index in bit_cursor()
CVE-2026-74636 tracing: Fix race between update_event_fields and, event_define_fields
CVE-2026-74637 perf/core: Fix group leader use-after-free after sibling detach
CVE-2026-74638 drm/v3d: Serialize the scheduler timeout handlers
CVE-2026-74651 staging: rtl8723bs: fix OOB read in rtw_get_wpa_ie()

Showing top 20 of 150 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-74639

No comments yet


Leave a comment