Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-48660

gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully

Medium5.5EPSS 0.24%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully When running gpio test on nxp-ls1028 platform with below command gpiomon --num-events=3 --rising-edge gpiochip1 25 There will be a warning trace as below: Call trace: free_irq+0x204/0x360 lineevent_free+0x64/0x70 gpio_ioctl+0x598/0x6a0 __arm64_sys_ioctl+0xb4/0x100 invoke_syscall+0x5c/0x130 ...... el0t_64_sync+0x1a0/0x1a4 The reason of this issue is that calling request_threaded_irq() function failed, and then lineevent_free() is invoked to release the resource. Since the lineevent_state::irq was already set, so the subsequent invocation of free_irq() would trigger the above warning call trace. To fix this issue, set the lineevent_state::irq after the IRQ register successfully.

Scores

CVSS scores of CVE-2022-48660, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.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.24% · top 85% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Weakness

  • CWE-noinfo Not enough information

Affected products

  • Linux · Linux

    • affected 468242724143a8e732f82f664b1e77432d149618 – < 657803b918e097e47d99d1489da83a603c36bcdd
    • affected 468242724143a8e732f82f664b1e77432d149618 – < 97da736cd11ae73bdf2f5e21e24446b8349e0168
    • affected 468242724143a8e732f82f664b1e77432d149618 – < b1489043d3b9004dd8d5a0357b08b5f0e6691c43
    • affected 468242724143a8e732f82f664b1e77432d149618 – < 69bef19d6b9700e96285f4b4e28691cda3dcd0d1
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 5.10.146 – ≤ 5.10.*
    • unaffected 5.15.71 – ≤ 5.15.*
    • unaffected 5.19.12 – ≤ 5.19.*
    • unaffected 6.0 – ≤ *

References (4)

Sources

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

Badge for a README or a ticket

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

Record last updated .