Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-49072

gpio: Restrict usage of GPIO chip irq members before initialization

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 15 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-49072, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.27% · top 81% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 48057ed1840fde9239b1e000bea1a0a1f07c5e99 – < 7e88a50704b0c49ad3f2d11e8b963341cf68a89f
    • affected 48057ed1840fde9239b1e000bea1a0a1f07c5e99 – < 0912cf021fb5749372b3782611d8b1de4986c13a
    • affected 48057ed1840fde9239b1e000bea1a0a1f07c5e99 – < 2c1fa3614795e2b24da1ba95de0b27b8f6ea4537
    • affected 48057ed1840fde9239b1e000bea1a0a1f07c5e99 – < f8dea54f74cae8c2e4d7b2952e8fed7743a85c87
    • affected 48057ed1840fde9239b1e000bea1a0a1f07c5e99 – < 5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320
    • affected 44dfa46aaf7cf594ac89bc1a0c0e56c498b31269
    • affected 5.2.14 – < 5.3
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 5.10.111 – ≤ 5.10.*
    • unaffected 5.15.34 – ≤ 5.15.*
    • unaffected 5.16.20 – ≤ 5.16.*
    • unaffected 5.17.3 – ≤ 5.17.*
    • unaffected 5.18 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49072 badge
[![CVE-2022-49072](https://cveledger.app/badge/CVE-2022-49072.svg)](https://cveledger.app/cve/CVE-2022-49072)

Record last updated .