Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-49842

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: ASoC: core: Fix use-after-free in snd_soc_exit() KASAN reports a use-after-free: BUG: KASAN: use-after-free in device_del+0xb5…

Published May 1, 2025CWE-416EPSS 0.22%

Overview

CVE-2022-49842 is a high-severity vulnerability. It was published on May 1, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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

ASoC: core: Fix use-after-free in snd_soc_exit()

KASAN reports a use-after-free:

BUG: KASAN: use-after-free in device_del+0xb5b/0xc60

Read of size 8 at addr ffff888008655050 by task rmmod/387

CPU: 2 PID: 387 Comm: rmmod

Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)

Call Trace:

<TASK>

dump_stack_lvl+0x79/0x9a

print_report+0x17f/0x47b

kasan_report+0xbb/0xf0

device_del+0xb5b/0xc60

platform_device_del.part.0+0x24/0x200

platform_device_unregister+0x2e/0x40

snd_soc_exit+0xa/0x22 [snd_soc_core]

__do_sys_delete_module.constprop.0+0x34f/0x5b0

do_syscall_64+0x3a/0x90

entry_SYSCALL_64_after_hwframe+0x63/0xcd

...

</TASK>

It's bacause in snd_soc_init(), snd_soc_util_init() is possble to fail,

but its ret is ignored, which makes soc_dummy_dev unregistered twice.

snd_soc_init()

snd_soc_util_init()

platform_device_register_simple(soc_dummy_dev)

platform_driver_register() # fail

platform_device_unr

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/2ec3f558db343b045a7c7419cdbaec266b8ac1a7Refgit.kernel.org/stable/c/34eee4189bcebbd5f6a2ff25ef0cb893ad33d51eRefgit.kernel.org/stable/c/41fad4f712e081acdfde8b59847f9f66eaf407a0Refgit.kernel.org/stable/c/6ec27c53886c8963729885bcf2dd996eba2767a7Refgit.kernel.org/stable/c/8d21554ec7680e9585fb852d933203c3db60dad1Refgit.kernel.org/stable/c/90bbdf30a51e42378cb23a312005a022794b8e1eRefgit.kernel.org/stable/c/a3365e62239dc064019a244bde5686ac18527c22Refgit.kernel.org/stable/c/c5674bd073c0fd9f620ca550c5ff08d0d429bdd9

How CyberStrike helps

Frequently asked questions

What is CVE-2022-49842?

CVE-2022-49842 is a high-severity vulnerability. It was published on May 1, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2022-49842?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-49842?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-49842?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-49842 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2022

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999