Skip to main content
VulnerabilityPublished Updated

CVE-2026-43314: Linux kernel · dm: remove fake timeout to avoid leak request

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f3a9c95a15d2f4466acad5c68faeff79ca5e9f47 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in f3a9c95a15d2f4466acad5c68faeff79ca5e9f47, ece6720de9403260088209b0b92d45e0b49ff856, cf2d06c9fd4b6521ea5b7f73c99c64c2c6f5e224 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e6ee8c0b767540f59e20da3ced282601db8aa502, < f3a9c95a15d2f4466acad5c68faeff79ca5e9f47
Fixed in
  • f3a9c95a15d2f4466acad5c68faeff79ca5e9f47
LinuxLinuxAffected
  • ≥ e6ee8c0b767540f59e20da3ced282601db8aa502, < ece6720de9403260088209b0b92d45e0b49ff856
Fixed in
  • ece6720de9403260088209b0b92d45e0b49ff856
LinuxLinuxAffected
  • ≥ e6ee8c0b767540f59e20da3ced282601db8aa502, < cf2d06c9fd4b6521ea5b7f73c99c64c2c6f5e224
Fixed in
  • cf2d06c9fd4b6521ea5b7f73c99c64c2c6f5e224
LinuxLinuxAffected
  • ≥ e6ee8c0b767540f59e20da3ced282601db8aa502, < c8a23d4c995ef4227bd4de64cd3910637ee6162e
Fixed in
  • c8a23d4c995ef4227bd4de64cd3910637ee6162e
LinuxLinuxAffected
  • ≥ e6ee8c0b767540f59e20da3ced282601db8aa502, < b307b6307f6459841312432bd4bc9519cbac97f5
Fixed in
  • b307b6307f6459841312432bd4bc9519cbac97f5
LinuxLinuxAffected
  • ≥ e6ee8c0b767540f59e20da3ced282601db8aa502, < 8200fca818c1e2f65bc6cb16d934ff6049302197
Fixed in
  • 8200fca818c1e2f65bc6cb16d934ff6049302197

Description

In the Linux kernel, the following vulnerability has been resolved: dm: remove fake timeout to avoid leak request Since commit 15f73f5b3e59 ("blk-mq: move failure injection out of blk_mq_complete_request"), drivers are responsible for calling blk_should_fake_timeout() at appropriate code paths and opportunities. However, the dm driver does not implement its own timeout handler and relies on the timeout handling of its slave devices. If an io-timeout-fail error is injected to a dm device, the request will be leaked and never completed, causing tasks to hang indefinitely. Reproduce: 1. prepare dm which has iscsi slave device 2. inject io-timeout-fail to dm echo 1 >/sys/class/block/dm-0/io-timeout-fail echo 100 >/sys/kernel/debug/fail_io_timeout/probability echo 10 >/sys/kernel/debug/fail_io_timeout/times 3. read/write dm 4. iscsiadm -m node -u Result: hang task like below [ 862.243768] INFO: task kworker/u514:2:151 blocked for more than 122 seconds. [ 862.244133] Tainted: G E 6.19.0-rc1+ #51 [ 862.244337] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 862.244718] task:kworker/u514:2 state:D stack:0 pid:151 tgid:151 ppid:2 task_flags:0x4288060 flags:0x00080000 [ 862.245024] Workqueue: iscsi_ctrl_3:1 __iscsi_unbind_session [scsi_transport_iscsi] [ 862.245264] Call Trace: [ 862.245587] <TASK> [ 862.245814] __schedule+0x810/0x15c0 [ 862.246557] schedule+0x69/0x180 [ 862.246760] blk_mq_freeze_queue_wait+0xde/0x120 [ 862.247688] elevator_change+0x16d/0x460 [ 862.247893] elevator_set_none+0x87/0xf0 [ 862.248798] blk_unregister_queue+0x12e/0x2a0 [ 862.248995] __del_gendisk+0x231/0x7e0 [ 862.250143] del_gendisk+0x12f/0x1d0 [ 862.250339] sd_remove+0x85/0x130 [sd_mod] [ 862.250650] device_release_driver_internal+0x36d/0x530 [ 862.250849] bus_remove_device+0x1dd/0x3f0 [ 862.251042] device_del+0x38a/0x930 [ 862.252095] __scsi_remove_device+0x293/0x360 [ 862.252291] scsi_remove_target+0x486/0x760 [ 862.252654] __iscsi_unbind_session+0x18a/0x3e0 [scsi_transport_iscsi] [ 862.252886] process_one_work+0x633/0xe50 [ 862.253101] worker_thread+0x6df/0xf10 [ 862.253647] kthread+0x36d/0x720 [ 862.254533] ret_from_fork+0x2a6/0x470 [ 862.255852] ret_from_fork_asm+0x1a/0x30 [ 862.256037] </TASK> Remove the blk_should_fake_timeout() check from dm, as dm has no native timeout handling and should not attempt to fake timeouts.

References

Community reviews

Loading reviews…