CVE-2026-43314

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-08. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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:

  • prepare dm which has iscsi slave device
  • 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
  • read/write dm
  • 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] [ 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]

Remove the blk_should_fake_timeout() check from dm, as dm has no native timeout handling and should not attempt to fake timeouts.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
3.6%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 15, 2026

Advisory Details (8)

Auto-updated May 15, 2026
No patch confirmed yet.
generic

dm: remove fake timeout to avoid leak request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f3a9c95a15d2f4466acad5c68faeff79ca5e9f47
generic

dm: remove fake timeout to avoid leak request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ece6720de9403260088209b0b92d45e0b49ff856
generic

dm: remove fake timeout to avoid leak request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cf2d06c9fd4b6521ea5b7f73c99c64c2c6f5e224
generic

dm: remove fake timeout to avoid leak request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c8a23d4c995ef4227bd4de64cd3910637ee6162e
generic

dm: remove fake timeout to avoid leak request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b307b6307f6459841312432bd4bc9519cbac97f5
generic

dm: remove fake timeout to avoid leak request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8200fca818c1e2f65bc6cb16d934ff6049302197
generic

dm: remove fake timeout to avoid leak request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6cdb21e0c9fdee484feba14fc9e72e9d07daf9f3
generic

dm: remove fake timeout to avoid leak request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4f9e7ca933a9fbf9912a384b061a00c77332cbf0

Vendor Advisories for CVE-2026-43314(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:16 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-01 15:06 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 05:09 UTCEG score recompute
  14. 2026-06-28 05:09 UTCGHSA enrichment
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-26 21:35 UTCEG score recompute
  18. 2026-06-26 21:35 UTCGHSA enrichment
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 14:05 UTCEPSS rescore
  22. 2026-06-23 21:33 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-06-21 14:56 UTCEPSS rescore
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-19 19:25 UTCEPSS rescore
  4. 2026-06-17 17:53 UTCEPSS rescore
  5. 2026-06-17 02:00 UTCEG score recompute
  6. 2026-06-17 02:00 UTCGHSA enrichment
  7. 2026-06-16 17:52 UTCEPSS rescore
  8. 2026-06-15 17:49 UTCEPSS rescore
  9. 2026-06-15 03:33 UTCEG score recompute
  10. 2026-06-15 03:33 UTCGHSA enrichment
  11. 2026-06-14 02:59 UTCEG score recompute
  12. 2026-06-14 02:59 UTCGHSA enrichment
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-12 14:31 UTCEG score recompute
  17. 2026-06-12 14:30 UTCGHSA enrichment
  18. 2026-06-11 14:00 UTCEPSS rescore
  19. 2026-06-11 13:33 UTCEG score recompute
  20. 2026-06-11 13:33 UTCGHSA enrichment
  21. 2026-06-10 22:18 UTCEPSS rescore
  22. 2026-06-10 13:22 UTCEPSS rescore
  23. 2026-06-10 13:22 UTCEPSS rescore
  24. 2026-06-10 13:01 UTCEG score recompute
  25. 2026-06-10 13:01 UTCGHSA enrichment
  26. 2026-06-09 12:29 UTCEG score recompute
  27. 2026-06-09 12:29 UTCGHSA enrichment
  28. 2026-06-08 14:17 UTCEPSS rescore
  29. 2026-06-08 14:17 UTCEPSS rescore
  30. 2026-06-08 11:57 UTCEG score recompute
  31. 2026-06-08 11:57 UTCGHSA enrichment
  32. 2026-06-07 15:25 UTCEPSS rescore
  33. 2026-06-07 15:25 UTCEPSS rescore
  34. 2026-06-07 11:21 UTCEG score recompute
  35. 2026-06-07 11:21 UTCGHSA enrichment
  36. 2026-06-06 13:47 UTCEPSS rescore
  37. 2026-06-06 13:47 UTCEPSS rescore
  38. 2026-06-06 10:49 UTCEG score recompute
  39. 2026-06-06 10:49 UTCGHSA enrichment
  40. 2026-06-05 22:47 UTCEPSS rescore
  41. 2026-06-05 10:16 UTCEG score recompute
  42. 2026-06-05 10:16 UTCGHSA enrichment
  43. 2026-06-05 06:10 UTCEPSS rescore
  44. 2026-06-05 06:10 UTCEPSS rescore
  45. 2026-06-04 13:12 UTCEPSS rescore
  46. 2026-06-04 13:12 UTCEPSS rescore
  47. 2026-06-04 09:44 UTCEG score recompute
  48. 2026-06-04 09:44 UTCGHSA enrichment
  49. 2026-06-03 09:10 UTCEG score recompute
  50. 2026-06-03 09:10 UTCGHSA enrichment
  51. 2026-06-02 20:13 UTCEPSS rescore
  52. 2026-06-02 08:37 UTCEG score recompute
  53. 2026-06-02 08:37 UTCGHSA enrichment
  54. 2026-06-01 13:52 UTCEPSS rescore
  55. 2026-06-01 13:52 UTCEPSS rescore
  56. 2026-06-01 08:05 UTCEG score recompute
  57. 2026-06-01 08:05 UTCGHSA enrichment
  58. 2026-05-31 22:30 UTCEPSS rescore
  59. 2026-05-31 22:30 UTCEPSS rescore
  60. 2026-05-31 00:16 UTCEPSS rescore
  61. 2026-05-31 00:16 UTCEPSS rescore
  62. 2026-05-29 13:44 UTCEPSS rescore
  63. 2026-05-29 13:44 UTCEPSS rescore
  64. 2026-05-28 13:44 UTCEPSS rescore
  65. 2026-05-28 13:44 UTCEPSS rescore
  66. 2026-05-27 13:40 UTCEPSS rescore
  67. 2026-05-27 13:40 UTCEPSS rescore
  68. 2026-05-26 13:44 UTCEPSS rescore
  69. 2026-05-26 07:18 UTCEPSS rescore
  70. 2026-05-21 22:43 UTCEPSS rescore
  71. 2026-05-20 22:38 UTCEPSS rescore
  72. 2026-05-20 13:43 UTCEG score recompute
  73. 2026-05-20 13:43 UTCGHSA enrichment
  74. 2026-05-20 11:22 UTCEPSS rescore
  75. 2026-05-20 11:22 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-43314?
CVE-2026-43314 is a medium vulnerability published on May 8, 2026. 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 blkmqcomplete_request"), drivers are responsible for calling blkshouldfake_timeout() at appropriate code paths and…
When was CVE-2026-43314 disclosed?
CVE-2026-43314 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43314 actively exploited?
CVE-2026-43314 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43314?
CVE-2026-43314 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43314?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43314, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-43314

Explore →

Is Your Infrastructure Affected by CVE-2026-43314?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs