CVE-2022-49709 [Medium] | Security Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: cfi: Fix __cfi_slowpath_diag RCU usage with cpuidle RCU_NONIDLE usage during __cfi_slowpath_diag can result in an invalid RCU state in the cpuidle code path: WARNING: CPU: 1 PID: 0 at kernel/rcu/tree.c:613 rcu_eqs_enter+0xe4/0x138 ... Call trace: rcu_eqs_enter+0xe4/0x138 rcu_idle_enter+0xa8/0x100 cpuidle_enter_state+0x154/0x3a8 cpuidle_enter+0x3c/0x58 do_idle.llvm.6590768638138871020+0x1f4/0x2ec cpu_startup_entry+0x28/0x2c secondary_start_kernel+0x1b8/0x220 __secondary_switched+0x94/0x98 Instead, call rcu_irq_enter/exit to wake up RCU only when needed and disable interrupts for the entire CFI shadow/module check when we do.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-06	0.04%	0.08%	+0.04%
2	2025-02-27	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-06

0.04%

0.08%

+0.04%

2025-02-27

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2022-49709

vendor	priority	summary	link
`debian`	unimportant	CVE-2022-49709 unimportant 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-49709
`redhat`	—	—	https://access.redhat.com/security/cve/CVE-2022-49709
`suse`	medium	CVE-2022-49709 severity moderate: SUSE including 26 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 198 product×package rows across 36 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Availability Extension 12 SP5, … (36 product lines)): Known Not Affected 198.	https://www.suse.com/security/cve/CVE-2022-49709/
`ubuntu`	medium	CVE-2022-49709 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 146, not-affected 145, released 114, needs-triage 1.	https://ubuntu.com/security/CVE-2022-49709

Affected software / configurations for CVE-2022-49709

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.13, < 5.15.49	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.18.6	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc1::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc2::::::

References for CVE-2022-49709

URL	Tags
https://git.kernel.org/stable/c/57cd6d157eb479f0a8e820fd36b7240845c8a937	Patch
https://git.kernel.org/stable/c/75f3a5fa2ad049c85ab5d5ee1ed9cfaa7e62c5ed	Patch
https://git.kernel.org/stable/c/ca3897f2ac02ceae5e6fa794f83c36f9885b93da	Patch

URL

CVE-2022-49709 | cfi: Fix __cfi_slowpath_diag RCU usage with cpuidle

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

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

Weakness enumeration for CVE-2022-49709

OS Trackers for CVE-2022-49709

Affected software / configurations for CVE-2022-49709

References for CVE-2022-49709