VulnerabilityPublished 28 Oct 2026Updated 29 Oct 2026

CVE-2026-99207: Linux kernel · scsi: target: Disable interrupts while holding delayed_cmd_lock

Affects Linux kernelSource GCVE Database

Compare

Authoritative record:CVE-2026-99207· High

Not known to be exploited.

Data as of 29 Oct 2026, 22:38 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10linux`pkg:deb/ubuntu/linux?arch=source&distro=stonking`Other threats	Affected 7.0.0-14.14 – 7.3.0-10.10 7 affected builds	Fixed in–
Ubuntu 26.10linux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=stonking`Other threats	Affected =7.0.0-1004.4 =7.3.0-1002.3 =7.3.0-1003.4	Fixed in–
Ubuntu 26.10linux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-oracle`pkg:deb/ubuntu/linux-oracle?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, avoid configurations that enable complete_type=1 with direct completion support on backends completing I/O from interrupt context and using ordered commands. Monitor vendor channels for patches addressing this issue.

Description

CVE-2026-99207 is a Linux kernel vulnerability in the SCSI target subsystem related to improper interrupt handling while holding the delayed_cmd_lock spinlock. The issue arises because target_do_delayed_work() uses a plain spin_lock() without disabling interrupts, whereas other code paths use spin_lock_irqsave(). This inconsistency can cause a deadlock when certain ordered SCSI commands complete in interrupt context, leading to a spinlock being held with interrupts enabled. The vulnerability requires specific conditions including complete_type=1 and a backend completing I/O from interrupt context. It was found by code inspection and has no known exploitation in the wild.

Impact

This vulnerability can cause a deadlock in the Linux kernel SCSI target subsystem when handling certain ordered commands completing in interrupt context. The deadlock arises from a spinlock being held with interrupts enabled, leading to indefinite spinning and potential system hang or denial of service. There is no evidence of exploitation in the wild. The impact is limited to specific configurations and workloads that use ordered commands with direct completion from interrupt context.

Summary

The vulnerability in the Linux kernel SCSI target subsystem involves inconsistent locking of delayed_cmd_lock. target_do_delayed_work() acquires the lock with spin_lock() allowing interrupts, while other code paths use spin_lock_irqsave() which disables interrupts. Since commit 06933066d88a, completions can occur inline in interrupt context, causing a deadlock if an ORDERED command completion triggers delayed_cmd_lock acquisition while interrupts are enabled. This can cause the CPU to spin indefinitely waiting for the lock. The issue requires complete_type=1 with direct completion support and ordered commands, conditions not default in common configurations. The flaw was identified by inspection without runtime reports or known exploits.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 22:38 UTC

Technical details

References

Community reviews

Related threats