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

In the Linux kernel, the following vulnerability has been resolved: gpio: Restrict usage of GPIO chip irq members before initialization GPIO chip irq members are exposed before they could be completely initialized and this leads to race conditions. One such issue was observed for the gc->irq.domain variable which was accessed through the I2C interface in gpiochip_to_irq() before it could be initialized by gpiochip_add_irqchip(). This resulted in Kernel NULL pointer dereference. Following are the logs for reference :- kernel: Call Trace: kernel: gpiod_to_irq+0x53/0x70 kernel: acpi_dev_gpio_irq_get_by+0x113/0x1f0 kernel: i2c_acpi_get_irq+0xc0/0xd0 kernel: i2c_device_probe+0x28a/0x2a0 kernel: really_probe+0xf2/0x460 kernel: RIP: 0010:gpiochip_to_irq+0x47/0xc0 To avoid such scenarios, restrict usage of GPIO chip irq members before they are completely initialized.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-12-28	0.03%	0.05%	+0.02%
2	2025-12-27	0.05%	0.03%	-0.02%
3	2025-12-23	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-12-28

0.03%

0.05%

+0.02%

2025-12-27

0.05%

0.03%

-0.02%

2025-12-23

—

0.05%

—

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-49072

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49072 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-49072
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49072
`suse`	medium	CVE-2022-49072 severity moderate: SUSE including 52 source package names (bpftool-7.0.0-284.11.1.el9_2, cluster-md-kmp-default, …), 140 product×package rows across 23 product lines (SUSE Liberty Linux 9, SUSE Linux Enterprise High Availability Extension 12 SP5, … (23 product lines)): Known Not Affected 113, Fixed 27.	https://www.suse.com/security/cve/CVE-2022-49072/
`ubuntu`	medium	CVE-2022-49072 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 130, released 127, pending 3.	https://ubuntu.com/security/CVE-2022-49072

Affected software / configurations for CVE-2022-49072

Vendor	Product	Version	Raw CPE
linux	linux_kernel	< 5.10.111	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.34	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.16.20	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.17, < 5.17.3	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	5.18	cpe:2.3:o:linux:linux_kernel:5.18:rc1::::::

References for CVE-2022-49072

URL	Tags
https://git.kernel.org/stable/c/0912cf021fb5749372b3782611d8b1de4986c13a	Patch
https://git.kernel.org/stable/c/2c1fa3614795e2b24da1ba95de0b27b8f6ea4537	Patch
https://git.kernel.org/stable/c/5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320	Patch
https://git.kernel.org/stable/c/7e88a50704b0c49ad3f2d11e8b963341cf68a89f	Patch
https://git.kernel.org/stable/c/f8dea54f74cae8c2e4d7b2952e8fed7743a85c87	Patch

URL

CVE-2022-49072 | gpio: Restrict usage of GPIO chip irq members before initialization

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

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

Weakness enumeration for CVE-2022-49072

OS Trackers for CVE-2022-49072

Affected software / configurations for CVE-2022-49072

References for CVE-2022-49072