CVE-2026-74641
CVE CVE-2026-74641EUVD EUVD-2026-64578Published 2026-08-22T15:32:19.000ZLast changed 2026-08-25T05:41:03.000ZCVSS 7.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: ALSA: usx2y: bound the hwdep mmap fault offset snd_us428ctls_vm_fault() turns the faulting page offset into a kernel address with no bound of any kind: offset = vmf->pgoff << PAGE_SHIFT; vaddr = (char *)(...)->us428ctls_sharedmem + offset; page = virt_to_page(vaddr); get_page(page); vmf->page = page; return 0; snd_us428ctls_mmap() checks only the length of the mapping, never the offset, and us428ctls_sharedmem is a single page from alloc_pages_exact(). For a character device file_mmap_size_max() returns ULONG_MAX, so the mm layer imposes no ceiling either. Every page offset above zero resolves to a struct page outside the object, and the handler installs it into the caller's address space read-write; the vma is not marked read-only. The caller picks the page frame with a single mmap() argument and gets read-write access to a page of kernel memory it does not own; an offset that lands in an unpopulated vmemmap region oopses instead. A process that can open the hwdep node of an attached US-X2Y reaches this after loading the FPGA image through the same node; no capability check is involved. On 7.2.0-rc5 (arm64), mmap() with a large offset: Unable to handle kernel paging request at virtual address fffffdffc45d5ac8 pc : snd_us428ctls_vm_fault+0x68/0x140 [snd_usb_usx2y] Call trace: snd_us428ctls_vm_fault+0x68/0x140 [snd_usb_usx2y] __do_fault __handle_mm_fault handle_mm_fault el0_da Reject any offset outside the shared region. The pcm hwdep handler in usx2yhwdeppcm.c computes its address the same way and needs the same bound. Discovered by XBOW, triaged by Baul Lee <baul.lee@xbow.com>
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.1.183; patch: 6.18.45; patch: 5.10.266; patch: 7.2; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ad6fedea65c6e90eda00d716c8bf20cdc437ed10; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2ca1eea3cd17930daffe9e429a7c89232036ec24; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5bf5ccddf00b59f1e3ea7e65d76a5f5b5c21cc2e; patch: 5.15.216; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <34ab56ed854baa73a731cfd99af689f0b1bac444; patch: 6.6.152; patch: 0; patch: 6.12.104; 2.6.12; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <10a87401fb3148c388e55df0148295b3b137da07; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f75d6f61f0d9c5c1ea725104014e10d26d1e3a00; patch: 7.1.9; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f613b4a2d87247b51a1b2b330f2e083a454125f2; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4208db2453e1ea71b8048a5b7802360cb29a53f1
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.