gpio: Restrict usage of GPIO chip irq members before initialization
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.111, 5.15.34, 5.16.20, 5.17.3
- CVEs
- CVE-2022-49072
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 15:27 UTC · Revision 1
Source evidence
gpio: Restrict usage of GPIO chip irq members before initialization
core-osv · Original sourcePublished 26 Feb 2025, 01:54 UTC
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.
osv:CVE-2022-49072
Kernel
Fixed versions: 5.10.111, 5.15.34, 5.16.20, 5.17.3
Complete source record
{
"id": "b27ce14c056d5f40f35f438ef4f1c0f343de6d8fa77a8ec62b08a226675ad079",
"url": "https://osv.dev/vulnerability/CVE-2022-49072",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "gpio: Restrict usage of GPIO chip irq members before initialization",
"summary": "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.",
"evidence": "osv:CVE-2022-49072",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.111",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.34",
"evidence": "/affected/1/ranges"
},
{
"value": "5.16.20",
"evidence": "/affected/1/ranges"
},
{
"value": "5.17.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-49072",
"aliases": [
"CVE-2022-49072"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "48057ed1840fde9239b1e000bea1a0a1f07c5e99"
},
{
"fixed": "7e88a50704b0c49ad3f2d11e8b963341cf68a89f"
},
{
"fixed": "0912cf021fb5749372b3782611d8b1de4986c13a"
},
{
"fixed": "2c1fa3614795e2b24da1ba95de0b27b8f6ea4537"
},
{
"fixed": "f8dea54f74cae8c2e4d7b2952e8fed7743a85c87"
},
{
"fixed": "5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "5.2.14"
},
{
"fixed": "5.3"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "44dfa46aaf7cf594ac89bc1a0c0e56c498b31269"
}
]
}
],
"versions": [
"v5.2.21",
"v5.2.20",
"v5.2.19",
"v5.2.18",
"v5.2.17",
"v5.2.16",
"v5.2.15",
"v5.2.14"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49072.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.3.0"
},
{
"fixed": "5.10.111"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.34"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "5.16.20"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.17.0"
},
{
"fixed": "5.17.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49072.json"
}
}
],
"modified": "2026-10-28T02:30:20.463959360Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0912cf021fb5749372b3782611d8b1de4986c13a",
"https://git.kernel.org/stable/c/2c1fa3614795e2b24da1ba95de0b27b8f6ea4537",
"https://git.kernel.org/stable/c/5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320",
"https://git.kernel.org/stable/c/7e88a50704b0c49ad3f2d11e8b963341cf68a89f",
"https://git.kernel.org/stable/c/f8dea54f74cae8c2e4d7b2952e8fed7743a85c87",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49072.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-49072",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49072.json"
}
},
"related_cves": [
{
"value": "CVE-2022-49072",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 486502,
"published_at": "2025-02-26T01:54:37.314+00:00"
}