CVE-2026-99185

firewire: core: fix race condition in split transaction handling

Published Oct 28, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

firewire: core: fix race condition in split transaction handling

For a split transaction, either fw_core_handle_response() or
split_transaction_timeout_callback() may manipulate the same transaction
entry in the pending transaction list. The return value of timer_delete()
is used to determine which function handles the entry. If the transaction
is a split transaction and timer_delete() returns zero, the timeout
callback may already be running. In this case, the response handler must
leave the entry in the list for the timeout callback to remove.

A previous code refactoring broke this behavior, introducing a race
condition in which both functions could process the same transaction.
This could lead to a use-after-free on the transaction initiator side.

Fix the regression by ensuring that the response handler does not process
the transaction when timer_delete() returns zero. The timeout callback is
responsible for removing the entry from the pending transaction list.

Analysis

AI-generated

Technical impact

The vulnerability is a race condition between the FireWire core response handler and the timeout callback. Both functions may manipulate the same transaction entry in the pending list, and when a timer deletion returns zero the timeout callback could already be running; the response handler may mistakenly process the entry as well. This double manipulation can lead to a use‑after‑free of the transaction structure, allowing an attacker with local access to corrupt kernel memory or execute arbitrary code. Additionally, the improper removal of the transaction entry when the timeout callback runs (CWE-825) further exacerbates the memory corruption risk.

Affected Systems

All Linux kernel versions that contain the legacy split transaction logic and have not applied the recent patch are potentially vulnerable. The issue is not tied to a specific distribution but affects the generic Linux kernel core. Any system that supports FireWire and loads the firewire core module could be impacted.

Risk and Exploitability

The flaw has no confirmed public exploitation, but its EPSS score is <1%, indicating a low likelihood of widespread exploitation. It remains a high‑severity kernel bug due to the use‑after‑free, with a CVSS score of 8.8. The attack vector is local, with an attacker needing access to a FireWire interface or the ability to generate split transactions against the kernel.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the kernel to a release that incorporates the fix for the split transaction race condition.
  • If an upgrade is not immediately possible, unload or blacklist the firewire modules to prevent the vulnerable code from loading.
  • As a residual safeguard, monitor the system for anomalous kernel panics or memory corruption that may indicate an attempted exploitation of the use‑after‑free condition.

Generated by OpenCVE AI on November 2, 2026 at 03:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Weaknesses CWE-362
CWE-416
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Weaknesses CWE-362
CWE-416
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: firewire: core: fix race condition in split transaction handling For a split transaction, either fw_core_handle_response() or split_transaction_timeout_callback() may manipulate the same transaction entry in the pending transaction list. The return value of timer_delete() is used to determine which function handles the entry. If the transaction is a split transaction and timer_delete() returns zero, the timeout callback may already be running. In this case, the response handler must leave the entry in the list for the timeout callback to remove. A previous code refactoring broke this behavior, introducing a race condition in which both functions could process the same transaction. This could lead to a use-after-free on the transaction initiator side. Fix the regression by ensuring that the response handler does not process the transaction when timer_delete() returns zero. The timeout callback is responsible for removing the entry from the pending transaction list.
Title firewire: core: fix race condition in split transaction handling
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-825

    Expired Pointer Dereference

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 31, 2026, 12:44 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 31, 2026, 1:17 PM
Severity
Moderate
Public date
Oct 28, 2026, 10:35 AM