<?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://vulnerability.circl.lu</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>Thu, 01 Oct 2026 13:13:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50773 — ALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50773</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt&lt;/p&gt;
&lt;p&gt;I got a null-ptr-defer error report when I do the following tests
on the qemu platform:&lt;/p&gt;
&lt;p&gt;make defconfig and CONFIG_PARPORT=m, CONFIG_PARPORT_PC=m,
CONFIG_SND_MTS64=m&lt;/p&gt;
&lt;p&gt;Then making test scripts:
cat&amp;gt;test_mod1.sh&amp;lt;&amp;lt;EOF
modprobe snd-mts64
modprobe snd-mts64
EOF&lt;/p&gt;
&lt;p&gt;Executing the script, perhaps several times, we will get a null-ptr-defer
report, as follow:&lt;/p&gt;
&lt;p&gt;syzkaller:~# ./test_mod.sh
snd_mts64: probe of snd_mts64.0 failed with error -5
modprobe: ERROR: could not insert &amp;#39;snd_mts64&amp;#39;: No such device
 BUG: kernel NULL pointer dereference, address: 0000000000000000
 #PF: supervisor write access in kernel mode
 #PF: error_code(0x0002) - not-present page
 PGD 0 P4D 0
 Oops: 0002 [#1] PREEMPT SMP PTI
 CPU: 0 PID: 205 Comm: modprobe Not tainted 6.1.0-rc8-00588-g76dcd734eca2 #6
 Call Trace:
  &amp;lt;IRQ&amp;gt;
  snd_mts64_interrupt+0x24/0xa0 [snd_mts64]
  parport_irq_handler+0x37/0x50 [parport]
  __handle_irq_event_percpu+0x39/0x190
  handle_irq_event_percpu+0xa/0x30
  handle_irq_event+0x2f/0x50
  handle_edge_irq+0x99/0x1b0
  __common_interrupt+0x5d/0x100
  common_interrupt+0xa0/0xc0
  &amp;lt;/IRQ&amp;gt;
  &amp;lt;TASK&amp;gt;
  asm_common_interrupt+0x22/0x40
 RIP: 0010:_raw_write_unlock_irqrestore+0x11/0x30
  parport_claim+0xbd/0x230 [parport]
  snd_mts64_probe+0x14a/0x465 [snd_mts64]
  platform_probe+0x3f/0xa0
  really_probe+0x129/0x2c0
  __driver_probe_device+0x6d/0xc0
  driver_probe_device+0x1a…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt&lt;/p&gt;
&lt;p&gt;I got a null-ptr-defer error report when I do the following tests
on the qemu platform:&lt;/p&gt;
&lt;p&gt;make defconfig and CONFIG_PARPORT=m, CONFIG_PARPORT_PC=m,
CONFIG_SND_MTS64=m&lt;/p&gt;
&lt;p&gt;Then making test scripts:
cat&amp;gt;test_mod1.sh&amp;lt;&amp;lt;EOF
modprobe snd-mts64
modprobe snd-mts64
EOF&lt;/p&gt;
&lt;p&gt;Executing the script, perhaps several times, we will get a null-ptr-defer
report, as follow:&lt;/p&gt;
&lt;p&gt;syzkaller:~# ./test_mod.sh
snd_mts64: probe of snd_mts64.0 failed with error -5
modprobe: ERROR: could not insert &amp;#39;snd_mts64&amp;#39;: No such device
 BUG: kernel NULL pointer dereference, address: 0000000000000000
 #PF: supervisor write access in kernel mode
 #PF: error_code(0x0002) - not-present page
 PGD 0 P4D 0
 Oops: 0002 [#1] PREEMPT SMP PTI
 CPU: 0 PID: 205 Comm: modprobe Not tainted 6.1.0-rc8-00588-g76dcd734eca2 #6
 Call Trace:
  &amp;lt;IRQ&amp;gt;
  snd_mts64_interrupt+0x24/0xa0 [snd_mts64]
  parport_irq_handler+0x37/0x50 [parport]
  __handle_irq_event_percpu+0x39/0x190
  handle_irq_event_percpu+0xa/0x30
  handle_irq_event+0x2f/0x50
  handle_edge_irq+0x99/0x1b0
  __common_interrupt+0x5d/0x100
  common_interrupt+0xa0/0xc0
  &amp;lt;/IRQ&amp;gt;
  &amp;lt;TASK&amp;gt;
  asm_common_interrupt+0x22/0x40
 RIP: 0010:_raw_write_unlock_irqrestore+0x11/0x30
  parport_claim+0xbd/0x230 [parport]
  snd_mts64_probe+0x14a/0x465 [snd_mts64]
  platform_probe+0x3f/0xa0
  really_probe+0x129/0x2c0
  __driver_probe_device+0x6d/0xc0
  driver_probe_device+0x1a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50773</guid>
    </item>
  </channel>
</rss>
