NULL pointer dereference in Linux
CVE-2025-22027
In the Linux kernel, the following vulnerability has been resolved: media: streamzap: fix race between device disconnection and urb callback Syzkaller has reported a general protection fault at function ir_raw_event_store_with_filter(). This crash is caused by a NULL pointer dereference of dev->raw pointer, even though it is checked for NULL in the same function, which means there is a race condition. It occurs due to the incorrect order of actions in the streamzap_disconnect() function: rc_unregister_device() is called before usb_kill_urb(). The dev->raw pointer is freed and set to NULL in rc_unregister_device(), and only after that usb_kill_urb() waits for in-progress requests to finish. If rc_unregister_device() is called while streamzap_callback() handler is not finished, this can lead to accessing freed resources. Thus rc_unregister_device() should be called after usb_kill_urb(). Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
Vulnerability class: Race Condition
EPSS: 0.001 (4.1th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 4.7 (Medium). Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H.
Affected products
- Linux — versions 8e9e60640067858e8036d4d43bbf725c60613359, 2.6.36, 0
- Linux Linux_kernel
Weakness classification (CWE)
Public proof-of-concept exploits
References
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- af854a3a-2127-422b-91ae-364da2661108
- af854a3a-2127-422b-91ae-364da2661108
Frequently asked questions
- What is CVE-2025-22027?
- CVE-2025-22027 is a medium-severity vulnerability in Linux, classified under Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition). CVSS score: 4.7/10. Published 2025-04-16.
- How severe is CVE-2025-22027?
- Medium severity. CVSS v3 base score is 4.7 out of 10.
- Is CVE-2025-22027 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.