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
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
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.

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1112.119~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-23ubuntu
linuxKernel @ 5.10.252osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (113 versions)6.19.6-1

Weakness Classification(1)

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

All Vendor Advisories

(24)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 67× 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.

Showing the most recent 100 of 168 total refreshes for this CVE.

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

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 0% probability of exploitation in the next 30 days, which ranks it in the top 96.5% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.