Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-50423

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: ACPICA: Fix use-after-free in acpi_ut_copy_ipackage_to_ipackage() There is an use-after-free reported by KASAN: BUG: KASAN:…

Published Oct 1, 2025CWE-416EPSS 0.16%

Overview

CVE-2022-50423 is a high-severity vulnerability. It was published on October 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:

ACPICA: Fix use-after-free in acpi_ut_copy_ipackage_to_ipackage()

There is an use-after-free reported by KASAN:

BUG: KASAN: use-after-free in acpi_ut_remove_reference+0x3b/0x82

Read of size 1 at addr ffff888112afc460 by task modprobe/2111

CPU: 0 PID: 2111 Comm: modprobe Not tainted 6.1.0-rc7-dirty

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

Call Trace:

<TASK>

kasan_report+0xae/0xe0

acpi_ut_remove_reference+0x3b/0x82

acpi_ut_copy_iobject_to_iobject+0x3be/0x3d5

acpi_ds_store_object_to_local+0x15d/0x3a0

acpi_ex_store+0x78d/0x7fd

acpi_ex_opcode_1A_1T_1R+0xbe4/0xf9b

acpi_ps_parse_aml+0x217/0x8d5

...

</TASK>

The root cause of the problem is that the acpi_operand_object

is freed when acpi_ut_walk_package_tree() fails in

acpi_ut_copy_ipackage_to_ipackage(), lead to repeated release in

acpi_ut_copy_iobject_to_iobject(). The problem was introduced

by "8aa5e56eeb61" commit, t

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/01f2c2052ea50fb9a8ce12e4e83aed0267934ef0Refgit.kernel.org/stable/c/02617006b5a46f2ea55ac61f5693c7afd7bf9276Refgit.kernel.org/stable/c/02f237423c9c6a18e062de2d474f85d5659e4eb9Refgit.kernel.org/stable/c/133462d35dae95edb944af86b986d4c9dec59bd1Refgit.kernel.org/stable/c/470188b09e92d83c5a997f25f0e8fb8cd2bc3469Refgit.kernel.org/stable/c/6fde666278f91b85d71545a0ebbf41d8d7af8074Refgit.kernel.org/stable/c/c9125b643fc51b8e662f2f614096ceb45a0adbc3Refgit.kernel.org/stable/c/dfdde4d5138bc023897033a5ac653a84e94805beRefgit.kernel.org/stable/c/f51b2235e4f320edc839c3e5cb0d1f8a6e8657c6

How CyberStrike helps

Frequently asked questions

What is CVE-2022-50423?

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

How severe is CVE-2022-50423?

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-50423?

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-50423?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50423 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