CVE-2022-50411 [High] | Use-After-Free in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: ACPICA: Fix error code path in acpi_ds_call_control_method() A use-after-free in acpi_ps_parse_aml() after a failing invocaion of acpi_ds_call_control_method() is reported by KASAN [1] and code inspection reveals that next_walk_state pushed to the thread by acpi_ds_create_walk_state() is freed on errors, but it is not popped from the thread beforehand. Thus acpi_ds_get_current_walk_state() called by acpi_ps_parse_aml() subsequently returns it as the new walk state which is incorrect. To address this, make acpi_ds_call_control_method() call acpi_ds_pop_walk_state() to pop next_walk_state from the thread before returning an error.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.03%	0.15%	+0.12%
2	2025-09-19	—	0.03%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.03%

0.15%

+0.12%

2025-09-19

—

0.03%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

134c704f-9b21-4f2e-91b3-4a467353bcc0

OS Trackers for CVE-2022-50411

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-50411 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-50411
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-50411
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-50411/
`ubuntu`	medium	CVE-2022-50411 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1414 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 1017, ignored 161, released 150, not-affected 80, needed 5, needs-triage 1.	https://ubuntu.com/security/CVE-2022-50411

Affected software / configurations for CVE-2022-50411

Vendor	Product	Version	Raw CPE
linux	linux_kernel	< 4.9.337	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.10, < 4.14.303	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.15, < 4.19.270	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.20, < 5.4.229	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.163	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.86	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.0.16	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.1, < 6.1.2	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2022-50411

URL	Tags
https://git.kernel.org/stable/c/0462fec709d51762ba486245bc344f44cc6cfa97	Patch
https://git.kernel.org/stable/c/2deb42c4f9776e59bee247c14af9c5e8c05ca9a6	Patch
https://git.kernel.org/stable/c/38e251d356a01b61a86cb35213cafd7e8fe7090c	Patch
https://git.kernel.org/stable/c/404ec60438add1afadaffaed34bb5fe4ddcadd40	Patch
https://git.kernel.org/stable/c/5777432ebaaf797e24f059979b42df3139967163	Patch
https://git.kernel.org/stable/c/799881db3e03b5e98fe6a900d9d7de8c7d61e7ee	Patch
https://git.kernel.org/stable/c/9ef353c92f9d04c88de3af1a46859c1fb76db0f8	Patch
https://git.kernel.org/stable/c/b0b83d3f3ffa96e8395c56b83d6197e184902a34	Patch
https://git.kernel.org/stable/c/f520d181477ec29a496c0b3bbfbdb7e2606c2713	Patch

URL

CVE-2022-50411 | ACPICA: Fix error code path in acpi_ds_call_control_method()

Exploit prediction scoring system (EPSS) score for CVE-2022-50411

Common vulnerability scoring system (CVSS) metrics for CVE-2022-50411

Weakness enumeration for CVE-2022-50411

OS Trackers for CVE-2022-50411

Affected software / configurations for CVE-2022-50411

References for CVE-2022-50411