← Back to CVE intelligence
CVE intelligence

CVE-2026-99185

Vulnerability intelligence

Published Oct 28, 2026Sources checked Nov 20, 2026
8.8HIGHCVSS out of 10
What this means

Review the available evidence

CVE-2026-99185 and is rated High severity with a CVSS score of 8.8. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Ubuntu Security Notices guidance

Vendor revision: Nov 19, 2026
Vendor remediation details

This update corrects flaws in the following subsystems: - S390 architecture; - x86 architecture; - Block layer subsystem; - Cryptographic API; - Compute Acceleration Framework; - FireWire subsystem; - GPIO subsystem; - GPU drivers; - Microsoft Hyper-V drivers; - I2C subsystem; - Multiple devices driver; - Network drivers; - STMicroelectronics network drivers; - Power supply drivers; - S/390 drivers; - SCSI subsystem; - SPI subsystem; - TCM subsystem; - UFS subsystem; - File systems infrastructure; - Ext4 file system; - File system notification infrastructure; - NTFS3 file system; - OCFS2 file system; - SMB network file system; - Tracing file system; - XFS file system; - Kernel futex primitives; - Key management; - Key Management; - VMware vSockets driver; - io_uring subsystem; - IPC subsys

CISA KEVNot listedBased on the latest collected catalog
EPSS0.2%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors0Source-linked actor relationships
Overview

What is CVE-2026-99185?

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.

Source: NVD