VulnerabilityPublished 28 Oct 2026

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

Source GCVE Database

Authoritative record:CVE-2026-99207

Not known to be exploited : upgrade to 7563650522732041ccfb2e4593878b5ea98d498c or 04a67a8b1a4460345d22fe75d93430cbf7e651d7 when convenient.

Data as of 28 Oct 2026, 13:42 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in 7563650522732041ccfb2e4593878b5ea98d498c, 04a67a8b1a4460345d22fe75d93430cbf7e651d7

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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.

ghsa-7j96-q76x-x86v

What to do

Upgrade Linux kernel to 7563650522732041ccfb2e4593878b5ea98d498c or 04a67a8b1a4460345d22fe75d93430cbf7e651d7.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 06933066d88a3093953b062922c016a67d2cdbf8, < 7563650522732041ccfb2e4593878b5ea98d498c	Fixed in 7563650522732041ccfb2e4593878b5ea98d498c
LinuxLinux	Affected ≥ 06933066d88a3093953b062922c016a67d2cdbf8, < 04a67a8b1a4460345d22fe75d93430cbf7e651d7	Fixed in 04a67a8b1a4460345d22fe75d93430cbf7e651d7
LinuxLinux	Affected =7.1	Fixed in–
Debiandebian/linux`pkg:deb/debian/linux`Other threats	Affected =7.1	Fixed in–

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

AI-suggested

A fix is available as the vulnerability has been resolved in the Linux kernel. Users should update to the fixed kernel versions once released. Since this is a kernel-level locking issue, applying the official kernel patch is the recommended mitigation. No other specific mitigations are indicated.

Description

A Linux kernel vulnerability in the SCSI target subsystem involves improper interrupt handling while holding the delayed_cmd_lock spinlock. This can cause a deadlock when certain ordered commands complete in interrupt context, due to inconsistent locking with interrupts enabled. The issue arises when target_do_delayed_work() uses spin_lock() without disabling interrupts, conflicting with other code paths that use spin_lock_irqsave(). This flaw requires specific conditions including complete_type=1 and ordered commands, which are not default. No exploitation in the wild has been reported.

Impact

The impact is a potential deadlock in the Linux kernel SCSI target subsystem when processing certain ordered commands that complete in interrupt context. This can cause system hangs or stalls in SCSI target operations under specific configurations. The vulnerability does not appear to be exploitable remotely or widely, as it requires specific backend and command attributes that are not default. No known exploitation in the wild has been reported.

References

Community reviews

Loading reviews…