CVE-2024-53170

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-12-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 5 sources updated this week

Also known asEUVD-2024-51842 (ENISA EUVD) · GHSA-xq66-2344-jv36 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

block: fix uaf for flush rq while iterating tags

blk_mq_clear_flush_rq_mapping() is not called during scsi probe, by checking blk_queue_init_done(). However, QUEUE_FLAG_INIT_DONE is cleared in del_gendisk by commit aec89dc5d421 ("block: keep q_usage_counter in atomic mode after del_gendisk"), hence for disk like scsi, following blk_mq_destroy_queue() will not clear flush rq from tags->rqs[] as well, cause following uaf that is found by our syzkaller for v6.6:

================================================================== BUG: KASAN: slab-use-after-free in blk_mq_find_and_get_req+0x16e/0x1a0 block/blk-mq-tag.c:261 Read of size 4 at addr ffff88811c969c20 by task kworker/1:2H/224909

CPU: 1 PID: 224909 Comm: kworker/1:2H Not tainted 6.6.0-ga836a5060850 #32 Workqueue: kblockd blk_mq_timeout_work Call Trace:

__dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x91/0xf0 lib/dump_stack.c:106 print_address_description.constprop.0+0x66/0x300 mm/kasan/report.c:364 print_report+0x3e/0x70 mm/kasan/report.c:475 kasan_report+0xb8/0xf0 mm/kasan/report.c:588 blk_mq_find_and_get_req+0x16e/0x1a0 block/blk-mq-tag.c:261 bt_iter block/blk-mq-tag.c:288 [inline] __sbitmap_for_each_set include/linux/sbitmap.h:295 [inline] sbitmap_for_each_set include/linux/sbitmap.h:316 [inline] bt_for_each+0x455/0x790 block/blk-mq-tag.c:325 blk_mq_queue_tag_busy_iter+0x320/0x740 block/blk-mq-tag.c:534 blk_mq_timeout_work+0x1a3/0x7b0 block/blk-mq.c:1673 process_one_work+0x7c4/0x1450 kernel/workqueue.c:2631 process_scheduled_works kernel/workqueue.c:2704 [inline] worker_thread+0x804/0xe40 kernel/workqueue.c:2785 kthread+0x346/0x450 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:293

Allocated by task 942: kasan_save_stack+0x22/0x50 mm/kasan/common.c:45 kasan_set_track+0x25/0x30 mm/kasan/common.c:52 ____kasan_kmalloc mm/kasan/common.c:374 [inline] __kasan_kmalloc mm/kasan/common.c:383 [inline] __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:380 kasan_kmalloc include/linux/kasan.h:198 [inline] __do_kmalloc_node mm/slab_common.c:1007 [inline] __kmalloc_node+0x69/0x170 mm/slab_common.c:1014 kmalloc_node include/linux/slab.h:620 [inline] kzalloc_node include/linux/slab.h:732 [inline] blk_alloc_flush_queue+0x144/0x2f0 block/blk-flush.c:499 blk_mq_alloc_hctx+0x601/0x940 block/blk-mq.c:3788 blk_mq_alloc_and_init_hctx+0x27f/0x330 block/blk-mq.c:4261 blk_mq_realloc_hw_ctxs+0x488/0x5e0 block/blk-mq.c:4294 blk_mq_init_allocated_queue+0x188/0x860 block/blk-mq.c:4350 blk_mq_init_queue_data block/blk-mq.c:4166 [inline] blk_mq_init_queue+0x8d/0x100 block/blk-mq.c:4176 scsi_alloc_sdev+0x843/0xd50 drivers/scsi/scsi_scan.c:335 scsi_probe_and_add_lun+0x77c/0xde0 drivers/scsi/scsi_scan.c:1189 __scsi_scan_target+0x1fc/0x5a0 drivers/scsi/scsi_scan.c:1727 scsi_scan_channel drivers/scsi/scsi_scan.c:1815 [inline] scsi_scan_channel+0x14b/0x1e0 drivers/scsi/scsi_scan.c:1791 scsi_scan_host_selected+0x2fe/0x400 drivers/scsi/scsi_scan.c:1844 scsi_scan+0x3a0/0x3f0 drivers/scsi/scsi_sysfs.c:151 store_scan+0x2a/0x60 drivers/scsi/scsi_sysfs.c:191 dev_attr_store+0x5c/0x90 drivers/base/core.c:2388 sysfs_kf_write+0x11c/0x170 fs/sysfs/file.c:136 kernfs_fop_write_iter+0x3fc/0x610 fs/kernfs/file.c:338 call_write_iter include/linux/fs.h:2083 [inline] new_sync_write+0x1b4/0x2d0 fs/read_write.c:493 vfs_write+0x76c/0xb00 fs/read_write.c:586 ksys_write+0x127/0x250 fs/read_write.c:639 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x70/0x120 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x78/0xe2

Freed by task 244687: kasan_save_stack+0x22/0x50 mm/kasan/common.c:45 kasan_set_track+0x25/0x30 mm/kasan/common.c:52 kasan_save_free_info+0x2b/0x50 mm/kasan/generic.c:522 ____kasan_slab_free mm/kasan/common.c:236 [inline] __kasan_slab_free+0x12a/0x1b0 mm/kasan/common.c:244 kasan_slab_free include/linux/kasan.h:164 [in ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
15th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 27, 2024

Last Modified

October 15, 2026

Advisory Details (7)

Auto-updated Jul 14, 2026
Patch available.
Web page

SSA-019113

https://cert-portal.siemens.com/productcert/html/ssa-019113.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4076-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Web page

block: fix uaf for flush rq while iterating tags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a0e93b9fefafe97d596f9c98701ae6c3b04b3ff6
Web page

block: fix uaf for flush rq while iterating tags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61092568f2a9acb0e6e186f03f2e0649a4e86d09
Web page

block: fix uaf for flush rq while iterating tags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3802f73bd80766d70f319658f334754164075bc3
Web page

block: fix uaf for flush rq while iterating tags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1921fe7d2836f8be1d321cf430d17e0d4e05301b
Web page

block: fix uaf for flush rq while iterating tags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1364a29b71c7837770f1902c49e7a6e234d72c92

Vendor Advisories for CVE-2024-53170(3)

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

Patch Availability(16)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-30ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-10-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-30ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1022.23~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1025.30) @ noble2026-10-30ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1022.22) @ noble2026-10-30ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1024.24) @ noble2026-10-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1018.19) @ noble2026-10-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1025.30~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-57.59~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-10-30ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-10-30ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-30ubuntu
redhatkernel-0:5.14.0-611.5.1.el9_72025-11-11redhat
linuxKernel @ 6.1.127 (fixes >=5.19.0)—osv

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 rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u1
  • every version up to 6.1.128-1~deb11u1: fixed in 6.1.128-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (34 versions)
  • every version up to 6.1.128-1: fixed in 6.1.128-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(14)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 216 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-53170?
CVE-2024-53170 is a high-severity vulnerability; its CVE record was published on December 27, 2024. In the Linux kernel, the following vulnerability has been resolved: block: fix uaf for flush rq while iterating tags blk_mq_clear_flush_rq_mapping() is not called during scsi probe, by checking blk_queue_init_done(). However, QUEUE_FLAG_INIT_DONE is cleared in del_gendisk by commit aec89dc5d421…
When was the CVE record for CVE-2024-53170 published?
The CVE record for CVE-2024-53170 was published on December 27, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-53170 actively exploited?
CVE-2024-53170 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-53170?
CVE-2024-53170 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-53170?
A fix for CVE-2024-53170 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-53170 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-53170

Explore →

Is Your Infrastructure Affected by CVE-2024-53170?

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

Book a Demo →Browse All CVEs