CVE-2025-22027
Last modified
CVE-2025-22027 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. 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. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 2.6.36, < 6.1.134 |
| Linux | Linux Kernel | >= 6.2, < 6.6.87 |
| Linux | Linux Kernel | >= 6.7, < 6.12.23 |
| Linux | Linux Kernel | >= 6.13, < 6.13.11 |
| Linux | Linux Kernel | >= 6.14, < 6.14.2 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-22027?
How severe is CVE-2025-22027?
How do I fix CVE-2025-22027?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-22021In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-22022In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-22023In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-22024In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-22025In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-22026In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-22028In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-22029Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2025-2203The FunnelKit WordPress plugin before 3.10.2 does not sanit…6.1
- CVE-2025-22030In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-22031In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-22032In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-22027?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
