LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 4.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-22027 is a Linux kernel flaw in the Streamzap media/USB remote driver. A race during device disconnect can crash the kernel path handling infrared events. The documented impact is availability, not data theft or tampering, and exploitation would require local low-privileged access under difficult timing conditions.

Executive priority

Treat this as routine-to-moderate kernel maintenance, not an emergency internet-exposed crisis. Prioritize multi-user Linux hosts, workstations, and systems with local device access. Patch through normal kernel update channels and verify coverage in vulnerability management reporting.

Technical view

The streamzap_disconnect() cleanup order allowed rc_unregister_device() to free and clear dev->raw before usb_kill_urb() waited for in-flight URB callbacks. If streamzap_callback() was still running, ir_raw_event_store_with_filter() could dereference invalid state. The fix reorders cleanup so URBs are killed before unregistering the rc device.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions with the Streamzap media driver path present or reachable. The CVE record lists Linux kernel ranges from 2.6.36 through several stable series before fixed releases. Default status is unaffected except listed affected versions.

Exploitation context

The CVSS vector is local, high-complexity, low-privilege, no user interaction, with high availability impact only. The source bundle marks KEV false and provides no evidence of active exploitation or a public exploit. The bug was found by Syzkaller via Linux Verification Center testing.

Researcher notes

Evidence supports a race-triggered kernel availability issue in the Streamzap driver. The record does not establish confidentiality or integrity impact. Avoid assuming broad exploitability: CVSS indicates local access and high attack complexity, and the provided sources do not show exploitation in the wild.

Mitigation direction

  • Apply Linux kernel updates that include the referenced stable fixes.
  • For Debian LTS systems, review and apply the cited Debian security updates.
  • Prioritize systems where local users can access relevant media or USB device paths.
  • If patching is delayed, follow vendor guidance for temporary exposure reduction.

Validation and detection

  • Inventory running Linux kernel versions against the affected and fixed version ranges.
  • Confirm whether the Streamzap media driver is built, loaded, or operationally needed.
  • Check vendor kernel changelogs for inclusion of the referenced stable commits.
  • Review Debian LTS advisory applicability for Debian-based assets.
  • Retest scanners after patching to confirm CVE closure.
Prepared
Confidence
high
Sources
12

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-476: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-22027 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.7CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H13.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

4.7Medium
CVSS 3.1 vector shape for CVE-2025-22027Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8e9e60640067858e8036d4d43bbf725c60613359, 8e9e60640067858e8036d4d43bbf725c60613359, 8e9e60640067858e8036d4d43bbf725c60613359, 8e9e60640067858e8036d4d43bbf725c60613359, 8e9e60640067858e8036d4d43bbf725c60613359, 8e9e60640067858e8036d4d43bbf725c60613359, 8e9e60640067858e8036d4d43bbf725c60613359, 8e9e60640067858e8036d4d43bbf725c60613359unaffected
LinuxLinux2.6.36, 0, 5.10.237, 5.15.181, 6.1.134, 6.6.87, 6.12.23, 6.13.11, 6.14.2, 6.15affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-476 · source CWE mapping

NULL Pointer Dereference

NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.