Vulnerability · CVE-2026-99185
firewire: core: fix race condition in split transaction handling
Published Oct 28, 2026 · catalog updated Nov 1, 2026 · Linux Linux
Last checked Nov 7, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-99185. EPSS is 0.22%. Act only if a listed version of Linux Linux is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-100082 · Unknown
- CVE-2026-100080 · Unknown
- CVE-2026-100081 · Unknown
- CVE-2026-99260 · Medium
- CVE-2026-99259 · Medium
- Severity
- High8.8
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.22%
- Remediation
- Advisory link
- Affected products
- Debian:14 linux · Linux Kernel · vendor Linux Linux
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Debian:14 linux6.12.100-1, 6.12.101-1, 6.12.105-1
- Linux Kernel6.19.0 → 7.2.13
- vendor Linux Linuxversion unspecified
How to fix CVE-2026-99185
Upgrade
CVE-2026-99185 lists a fix boundary at 7.2.13. Compare the installed build with that boundary before you change production.
Version check
Seen in 6.12.100-1 · 3 other packages on the advisory
Advisory
Open the bsi record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-99185. EPSS is 0.22%. Act only if a listed version of Linux Linux is installed.
Which versions are affected?
Compare what you have installed with Kernel 6.19.0 → 7.2.13. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.22%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 28, 2026 · Tenable CVE Database
Detected
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 t
Oct 28, 2026 · CVE.org
Updated
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 t
Nov 1, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 7.2.13
Nov 1, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 7.2.13
Nov 1, 2026 · OpenSSF OSV / OSV Scanner
Updated
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 t
Nov 1, 2026 · Trivy Vulnerability DB
Updated
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 t
Sources
- BSI CERT-BundGovernment advisoryCVE-2026-99185
Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff
wid.cert-bund.de - CVE.orgVulnerability recordCVE-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
cve.org - FIRST EPSSExploitation probabilityCVE-2026-99185
30-day exploitation probability 0.22%
first.org - OpenSSF OSV / OSV ScannerPackage advisoryCVE-2026-99185
firewire: core: fix race condition in split transaction handling
osv.dev - Tenable CVE DatabaseVulnerability recordCVE-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 t
tenable.com - Trivy Vulnerability DBPackage advisoryDEBIAN-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
osv.dev
References
Freshness
Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 7, 2026
- Trivy Vulnerability DBNov 1, 2026
- OpenSSF OSV / OSV ScannerNov 1, 2026
- BSI CERT-BundOct 30, 2026
- CVE.orgOct 29, 2026
- Tenable CVE DatabaseOct 28, 2026