CVE-2022-48660

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

MEDIUM
5.5
CVSS Score
Published: April 28, 2024 at 01:01 PM UTC
Updated: June 17, 2026 at 05:15 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.11 ≤ v < 5.15.715.16 ≤ v < 5.19.125.9 ≤ v < 5.10.1465.9 ≤ v < 5.15.715.9 ≤ v < 5.19.125.9 ≤ v < 6.0468242724143a8e732f82f664b1e77432d1496185.9
Vendor states this is fixed in 657803b918e097e47d99d1489da83a603c36bcdd (fixed)
Vendor states this is fixed in 69bef19d6b9700e96285f4b4e28691cda3dcd0d1 (fixed)
Vendor states this is fixed in 97da736cd11ae73bdf2f5e21e24446b8349e0168 (fixed)
Vendor states this is fixed in b1489043d3b9004dd8d5a0357b08b5f0e6691c43 (fixed)
Vendor states this is fixed in 5.10.146 (unaffected)
Vendor states this is fixed in 5.15.71 (unaffected)
Vendor states this is fixed in 5.19.12 (unaffected)
Vendor states this is fixed in 5.9 (unaffected)
Vendor states this is fixed in 6.0 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/657803b918e097e47d99d1489da83a603c36bcdd
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/69bef19d6b9700e96285f4b4e28691cda3dcd0d1
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/97da736cd11ae73bdf2f5e21e24446b8349e0168
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b1489043d3b9004dd8d5a0357b08b5f0e6691c43

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card