LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50773: ALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt

In the Linux kernel, the following vulnerability has been resolved: ALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt I got a null-ptr-defer error report when I do the following tests on the qemu platform: make defconfig and CONFIG_PARPORT=m, CONFIG_PARPORT_PC=m, CONFIG_SND_MTS64=m Then making test scripts: cat>test_mod1.sh<<EOF modprobe snd-mts64 modprobe snd-mts64 EOF Executing the script, perhaps several times, we will get a null-ptr-defer report, as follow: syzkaller:~# ./test_mod.sh snd_mts64: probe of snd_mts64.0 failed with error -5 modprobe: ERROR: could not insert 'snd_mts64': 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: <IRQ> 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 </IRQ> <TASK> 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/0xa0 __device_attach_driver+0x7a/0xb0 bus_for_each_drv+0x62/0xb0 __device_attach+0xe4/0x180 bus_probe_device+0x82/0xa0 device_add+0x550/0x920 platform_device_add+0x106/0x220 snd_mts64_attach+0x2e/0x80 [snd_mts64] port_check+0x14/0x20 [parport] bus_for_each_dev+0x6e/0xc0 __parport_register_driver+0x7c/0xb0 [parport] snd_mts64_module_init+0x31/0x1000 [snd_mts64] do_one_initcall+0x3c/0x1f0 do_init_module+0x46/0x1c6 load_module+0x1d8d/0x1e10 __do_sys_finit_module+0xa2/0xf0 do_syscall_64+0x37/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK> Kernel panic - not syncing: Fatal exception in interrupt Rebooting in 1 seconds.. The mts wa not initialized during interrupt, we add check for mts to fix this bug.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50773 is a Linux kernel bug in the ALSA MTS-64 driver. Under the reported test condition, loading the driver can trigger a NULL pointer dereference in an interrupt handler and cause a kernel panic. Business impact is mainly availability risk on systems with this uncommon sound/MIDI driver enabled or loadable.

Executive priority

Treat as a targeted availability issue, not a broad enterprise emergency. Patch through normal kernel maintenance, with higher priority for systems using legacy parallel-port MIDI/audio hardware or allowing this module to load.

Technical view

The issue is in snd_mts64_interrupt in the Linux kernel ALSA mts64 driver. During module probing, an interrupt can occur before the mts structure is initialized, leading to a NULL pointer dereference and panic. Upstream stable fixes add a check for mts. CVSS and CWE data are not provided in the source bundle.

Likely exposure

Exposure appears limited to Linux systems with CONFIG_SND_MTS64 available, alongside parport support. The source demonstrates failure during repeated module loading in QEMU. Systems without this driver built or loadable are less likely exposed. Distribution-specific affected package ranges are not provided.

Exploitation context

No active exploitation is indicated; the CVE is not marked KEV in the provided data. The public description shows a reproducible local crash scenario involving module loading. The source does not establish remote exploitability, privilege requirements beyond module interaction, or broader exploit availability.

Researcher notes

Affected version metadata is incomplete and commit-oriented. The source lists multiple stable commits and affected Linux versions, but no CVSS score. Analysis should focus on driver reachability, module autoload policy, and whether vendor kernels have backported the specific mts initialization check.

Mitigation direction

  • Update to a vendor kernel containing the upstream ALSA mts64 NULL pointer fix.
  • If unused, disable or avoid loading the snd-mts64 driver.
  • Follow Linux distribution advisories for backported kernel package fixes.
  • Prioritize systems where snd-mts64 and parport modules are enabled or loadable.

Validation and detection

  • Inventory kernels for CONFIG_SND_MTS64 and parport support.
  • Confirm vendor kernel changelog includes the snd_mts64_interrupt NULL pointer fix.
  • Check whether snd-mts64 is loaded or permitted by policy.
  • Validate that deployed kernel versions include the relevant upstream stable commit.
Prepared
Confidence
medium
Sources
11

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50773 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
10Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad, 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad, 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad, 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad, 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad, 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad, 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad, 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad, 68ab801e32bbe2caac8b8c6e6e94f41fe7d687adunaffected
LinuxLinux2.6.19, 0, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.