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

In the Linux kernel, the following vulnerability has been resolved: pinctrl: ralink: Check for null return of devm_kcalloc Because of the possible failure of the allocation, data->domains might be NULL pointer and will cause the dereference of the NULL pointer later. Therefore, it might be better to check it and directly return -ENOMEM without releasing data manually if fails, because the comment of the devm_kmalloc() says "Memory allocated with this function is automatically freed on driver detach.".

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-21	0.06%	0.03%	-0.03%
2	2025-11-18	0.04%	0.06%	+0.02%
3	2025-07-25	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-21

0.06%

0.03%

-0.03%

2025-11-18

0.04%

0.06%

+0.02%

2025-07-25

—

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]
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	134c704f-9b21-4f2e-91b3-4a467353bcc0

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]

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

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

OS Trackers for CVE-2022-49608

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49608 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-49608
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49608
`suse`	medium	CVE-2022-49608 severity moderate: SUSE including 25 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 160 product×package rows across 28 product lines (SUSE Linux Enterprise High Availability Extension 12 SP5, SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS, … (28 product lines)): Known Not Affected 160.	https://www.suse.com/security/cve/CVE-2022-49608/
`ubuntu`	medium	CVE-2022-49608 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 149, released 135, not-affected 102, needed 19, needs-triage 1.	https://ubuntu.com/security/CVE-2022-49608

Affected software / configurations for CVE-2022-49608

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 4.18, < 4.19.254	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.20, < 5.4.208	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.134	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.58	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.18.15	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::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc3::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc4::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc5::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc6::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc7::::::

References for CVE-2022-49608

URL	Tags
https://git.kernel.org/stable/c/13596e6c9e541e90e5fc2c52b23f08b951370da9	Patch
https://git.kernel.org/stable/c/44016a85419ca0d4f1e4d0127b330f8e4e2a57d0	Patch
https://git.kernel.org/stable/c/5595d30c4dc27d939635c3188c68203b6ece1711	Patch
https://git.kernel.org/stable/c/5694b162f275fb9a9f89422701b2b963be11e496	Patch
https://git.kernel.org/stable/c/6194c021496addc11763d1ffa89ce5751889fe3c	Patch
https://git.kernel.org/stable/c/c3b821e8e406d5650e587b7ac624ac24e9b780a8	Patch

URL

CVE-2022-49608 | pinctrl: ralink: Check for null return of devm_kcalloc

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

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

Weakness enumeration for CVE-2022-49608

OS Trackers for CVE-2022-49608

Affected software / configurations for CVE-2022-49608

References for CVE-2022-49608