<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 17:42:41 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74641</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74641</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-74641</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1090 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090</link>
      <description>certfr-2026-avi-1090</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090</guid>
    </item>
    <item>
      <title>EUVD-2026-358531</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-358531</link>
      <description>EUVD-2026-358531</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-358531</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74641</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74641</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ALSA: usx2y: bound the hwdep mmap fault offset&lt;/p&gt;
&lt;p&gt;snd_us428ctls_vm_fault() turns the faulting page offset into a kernel
address with no bound of any kind:&lt;/p&gt;
&lt;p&gt;offset = vmf-&amp;gt;pgoff &amp;lt;&amp;lt; PAGE_SHIFT;
	vaddr = (char *)(...)-&amp;gt;us428ctls_sharedmem + offset;
	page = virt_to_page(vaddr);
	get_page(page);
	vmf-&amp;gt;page = page;&lt;/p&gt;
&lt;p&gt;return 0;&lt;/p&gt;
&lt;p&gt;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&amp;#39;s address space read-write; the vma
is not marked read-only.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;On 7.2.0-rc5 (arm64), mmap() with a large offset:&lt;/p&gt;
&lt;p&gt;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
   e…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ALSA: usx2y: bound the hwdep mmap fault offset&lt;/p&gt;
&lt;p&gt;snd_us428ctls_vm_fault() turns the faulting page offset into a kernel
address with no bound of any kind:&lt;/p&gt;
&lt;p&gt;offset = vmf-&amp;gt;pgoff &amp;lt;&amp;lt; PAGE_SHIFT;
	vaddr = (char *)(...)-&amp;gt;us428ctls_sharedmem + offset;
	page = virt_to_page(vaddr);
	get_page(page);
	vmf-&amp;gt;page = page;&lt;/p&gt;
&lt;p&gt;return 0;&lt;/p&gt;
&lt;p&gt;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&amp;#39;s address space read-write; the vma
is not marked read-only.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;On 7.2.0-rc5 (arm64), mmap() with a large offset:&lt;/p&gt;
&lt;p&gt;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
   e…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-74641</guid>
    </item>
    <item>
      <title>GHSA-mrvc-mw2v-9ww4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mrvc-mw2v-9ww4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ALSA: usx2y: bound the hwdep mmap fault offset&lt;/p&gt;
&lt;p&gt;snd_us428ctls_vm_fault() turns the faulting page offset into a kernel
address with no bound of any kind:&lt;/p&gt;
&lt;p&gt;offset = vmf-&amp;gt;pgoff &amp;lt;&amp;lt; PAGE_SHIFT;
	vaddr = (char *)(...)-&amp;gt;us428ctls_sharedmem + offset;
	page = virt_to_page(vaddr);
	get_page(page);
	vmf-&amp;gt;page = page;&lt;/p&gt;
&lt;p&gt;return 0;&lt;/p&gt;
&lt;p&gt;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&amp;#39;s address space read-write; the vma
is not marked read-only.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;On 7.2.0-rc5 (arm64), mmap() with a large offset:&lt;/p&gt;
&lt;p&gt;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
   e…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ALSA: usx2y: bound the hwdep mmap fault offset&lt;/p&gt;
&lt;p&gt;snd_us428ctls_vm_fault() turns the faulting page offset into a kernel
address with no bound of any kind:&lt;/p&gt;
&lt;p&gt;offset = vmf-&amp;gt;pgoff &amp;lt;&amp;lt; PAGE_SHIFT;
	vaddr = (char *)(...)-&amp;gt;us428ctls_sharedmem + offset;
	page = virt_to_page(vaddr);
	get_page(page);
	vmf-&amp;gt;page = page;&lt;/p&gt;
&lt;p&gt;return 0;&lt;/p&gt;
&lt;p&gt;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&amp;#39;s address space read-write; the vma
is not marked read-only.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;On 7.2.0-rc5 (arm64), mmap() with a large offset:&lt;/p&gt;
&lt;p&gt;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
   e…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mrvc-mw2v-9ww4</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-74641 — ALSA: usx2y: bound the hwdep mmap fault offset</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-74641</link>
      <description>msrc_CVE-2026-74641</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-74641</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74641</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74641</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;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-&amp;gt;pgoff &amp;lt;&amp;lt; PAGE_SHIFT; 	vaddr = (char *)(...)-&amp;gt;us428ctls_sharedmem + offset; 	page = virt_to_page(vaddr); 	get_page(page); 	vmf-&amp;gt;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&amp;#39;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 Rej…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;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-&amp;gt;pgoff &amp;lt;&amp;lt; PAGE_SHIFT; 	vaddr = (char *)(...)-&amp;gt;us428ctls_sharedmem + offset; 	page = virt_to_page(vaddr); 	get_page(page); 	vmf-&amp;gt;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&amp;#39;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 Rej…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74641</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2970 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2970</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2970</guid>
    </item>
  </channel>
</rss>
