Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
  • Fixed version: Linux Linux 0649129359219ce6ff380ec401f87308485c6ae3, 06ec592389f2be3199779ab823c4323dcfd2121f, 1a763c748acd5540ccc43306c57c9c6c5fb60884.

Low priority for now. Upgrade to Linux Linux 0649129359219ce6ff380ec401f87308485c6ae3, 06ec592389f2be3199779ab823c4323dcfd2121f, 1a763c748acd5540ccc43306c57c9c6c5fb60884 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Dec 24, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 20th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-50773

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.19affected
    • 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before 06ec592389f2be3199779ab823c4323dcfd2121faffected · git
    • 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before b471fe61da523a15e4cb60fa81f5a2377e4bad98affected · git
    • 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before 7e91667db38abb056da5a496d40fbd044c66bed2affected · git
    • 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before c7e9624d90bf20f1eed6b228949396d614b94020affected · git
    • 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before 0649129359219ce6ff380ec401f87308485c6ae3affected · git
    • 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before cba633b24a98d957e8190ef8bc4d4cdb4f6e9313affected · git
    • 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before 1a763c748acd5540ccc43306c57c9c6c5fb60884affected · git
    • 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before 250eed7b9994d79f9c409f954dbd08e88f5afd83affected · git
    • 68ab801e32bbe2caac8b8c6e6e94f41fe7d687ad and later · before cf2ea3c86ad90d63d1c572b43e1ca9276b0357adaffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.4-16.1.4-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-50771Dec 24, 2025 · rcu: Fix __this_cpu_read() lockdep warning in rcu_force_quiescent_state()
    0Monitor
  • ← EarlierCVE-2022-50772Dec 24, 2025 · netdevsim: fix memory leak in nsim_bus_dev_new()
    0Monitor
  • Later →CVE-2022-50774Dec 24, 2025 · crypto: qat - fix DMA transfer direction
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0649129359219ce6ff380ec401f87308485c6ae3Vendor (CNA)
Linux Linux06ec592389f2be3199779ab823c4323dcfd2121fVendor (CNA)
Linux Linux1a763c748acd5540ccc43306c57c9c6c5fb60884Vendor (CNA)
Linux Linux250eed7b9994d79f9c409f954dbd08e88f5afd83Vendor (CNA)
Linux Linux7e91667db38abb056da5a496d40fbd044c66bed2Vendor (CNA)
Linux Linuxb471fe61da523a15e4cb60fa81f5a2377e4bad98Vendor (CNA)
Linux Linuxc7e9624d90bf20f1eed6b228949396d614b94020Vendor (CNA)
Linux Linuxcba633b24a98d957e8190ef8bc4d4cdb4f6e9313Vendor (CNA)
Linux Linuxcf2ea3c86ad90d63d1c572b43e1ca9276b0357adVendor (CNA)
debian:linux6.1.4-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records