CVE-2022-50566

  • Published: 2025-10-22T14:15:41.420
  • Last modified: 1761167568

In the Linux kernel, the following vulnerability has been resolved:

mtd: Fix device name leak when register device failed in add_mtd_device()

There is a kmemleak when register device failed:
unreferenced object 0xffff888101aab550 (size 8):
comm “insmod”, pid 3922, jiffies 4295277753 (age 925.408s)
hex dump (first 8 bytes):
6d 74 64 30 00 88 ff ff mtd0….
backtrace:
[] __kmalloc_node_track_caller+0x4e/0x150
[] kvasprintf+0xb0/0x130
[] kobject_set_name_vargs+0x2f/0xb0
[] dev_set_name+0xab/0xe0
[] add_mtd_device+0x4bb/0x700
[] mtd_device_parse_register+0x2ac/0x3f0
[] 0xffffffffa0238457
[] 0xffffffffa02a008f
[] do_one_initcall+0x87/0x2a0
[] do_init_module+0xdf/0x320
[] load_module+0x2f98/0x3330
[] __do_sys_finit_module+0x113/0x1b0
[] do_syscall_64+0x35/0x80
[] entry_SYSCALL_64_after_hwframe+0x46/0xb0

If register device failed, should call put_device() to give up the
reference.

Related CVE by CWE

No related CWE found.

Top CVE for Vendor

No vendor taxonomy on this entry.

Recently Exploited Similar Vulnerabilities

No recent KEV-listed items for this vendor/product.

How to fix CVE-2022-50566

CVE-2022-50566 is a unknown severity vulnerability affecting the affected product.

Description: In the Linux kernel, the following vulnerability has been resolved: mtd: Fix device name leak when register device failed in add_mtd_device() There is a kmemleak when register device failed: unreferenced object 0xffff888101aab550 (size 8): comm “insmod”, pid 3922, jiffies 4295277753 (age 925.408s) hex dump (first 8 bytes): 6d 74 64 30 00 88 ff ff […]

Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public

How to Fix:

1 Identify affected systems

- Check if you're running the affected product

2 Immediate actions

- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access

3 Verification

- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)

4 Long-term prevention

- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations

Exploit Difficulty Assessment

HARD
⏱️ Time to Exploit: > 4 hours
🛠️ Skills Required: Advanced security expertise
💰 Public Exploits: Rare or not public

Vulnerability Timeline

Oct 22, 2025
Vulnerability Published

CVE details first published to NVD database

Jan 01, 1970
Last Modified

CVE details were updated

Oct 28, 2025
Imported to Database

Added to this CVE tracking system

Detection Rules & IOCs

No specific detection rules generated for this vulnerability type.

No vendor/product data available.