CVE-2024-47706

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-10-21. NVD baseline CVSS 5.5; sources differ by 0.0.

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

A fix is available — apply it.

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

block, bfq: fix possible UAF for bfqq->bic with merge chain

1) initial state, three tasks:

Process 1 Process 2 Process 3 (BIC1) (BIC2) (BIC3) | Λ | Λ | Λ | | | | | | V | V | V | bfqq1 bfqq2 bfqq3 process ref: 1 1 1

2) bfqq1 merged to bfqq2:

Process 1 Process 2 Process 3 (BIC1) (BIC2) (BIC3) | | | Λ \--------------\| | | V V | bfqq1--------->bfqq2 bfqq3 process ref: 0 2 1

3) bfqq2 merged to bfqq3:

Process 1 Process 2 Process 3 (BIC1) (BIC2) (BIC3) here -> Λ | | \--------------\ \-------------\| V V bfqq1--------->bfqq2---------->bfqq3 process ref: 0 1 3

In this case, IO from Process 1 will get bfqq2 from BIC1 first, and then get bfqq3 through merge chain, and finially handle IO by bfqq3. Howerver, current code will think bfqq2 is owned by BIC1, like initial state, and set bfqq2->bic to BIC1.

bfq_insert_request -> by Process 1 bfqq = bfq_init_rq(rq) bfqq = bfq_get_bfqq_handle_split bfqq = bic_to_bfqq -> get bfqq2 from BIC1 bfqq->ref++ rq->elv.priv[0] = bic rq->elv.priv[1] = bfqq if (bfqq_process_refs(bfqq) == 1) bfqq->bic = bic -> record BIC1 to bfqq2

__bfq_insert_request new_bfqq = bfq_setup_cooperator -> get bfqq3 from bfqq2->new_bfqq bfqq_request_freed(bfqq) new_bfqq->ref++ rq->elv.priv[1] = new_bfqq -> handle IO by bfqq3

Fix the problem by checking bfqq is from merge chain fist. And this might fix a following problem reported by our syzkaller(unreproducible):

================================================================== BUG: KASAN: slab-use-after-free in bfq_do_early_stable_merge block/bfq-iosched.c:5692 [inline] BUG: KASAN: slab-use-after-free in bfq_do_or_sched_stable_merge block/bfq-iosched.c:5805 [inline] BUG: KASAN: slab-use-after-free in bfq_get_queue+0x25b0/0x2610 block/bfq-iosched.c:5889 Write of size 1 at addr ffff888123839eb8 by task kworker/0:1H/18595

CPU: 0 PID: 18595 Comm: kworker/0:1H Tainted: G L 6.6.0-07439-gba2303cacfda #6 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 Workqueue: kblockd blk_mq_requeue_work Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x91/0xf0 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:364 [inline] print_report+0x10d/0x610 mm/kasan/report.c:475 kasan_report+0x8e/0xc0 mm/kasan/report.c:588 bfq_do_early_stable_merge block/bfq-iosched.c:5692 [inline] bfq_do_or_sched_stable_merge block/bfq-iosched.c:5805 [inline] bfq_get_queue+0x25b0/0x2610 block/bfq-iosched.c:5889 bfq_get_bfqq_handle_split+0x169/0x5d0 block/bfq-iosched.c:6757 bfq_init_rq block/bfq-iosched.c:6876 [inline] bfq_insert_request block/bfq-iosched.c:6254 [inline] bfq_insert_requests+0x1112/0x5cf0 block/bfq-iosched.c:6304 blk_mq_insert_request+0x290/0x8d0 block/blk-mq.c:2593 blk_mq_requeue_work+0x6bc/0xa70 block/blk-mq.c:1502 process_one_work kernel/workqueue.c:2627 [inline] process_scheduled_works+0x432/0x13f0 kernel/workqueue.c:2700 worker_thread+0x6f2/0x1160 kernel/workqueue.c:2781 kthread+0x33c/0x440 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:305

Allocated by task 20776: kasan_save_stack+0x20/0x40 mm/kasan/common.c:45 kasan_set_track+0x25/0x30 mm/kasan/common.c:52 __kasan_slab_alloc+0x87/0x90 mm/kasan/common.c:328 kasan_slab_alloc include/linux/kasan.h:188 [inline] slab_post_alloc_hook mm/slab.h:763 [inline] slab_alloc_node mm/slub.c:3458 [inline] kmem_cache_alloc_node+0x1a4/0x6f0 mm/slub.c:3503 ioc_create_icq block/blk-ioc.c:370 [inline] ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100CISA SSVC

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%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 21, 2024

Last Modified

August 5, 2026

References (9)

Vendor Advisories for CVE-2024-47706(2)

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

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1073.73) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.127.137~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1078.87~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1039.43) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-21ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1071.77~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1071.71) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gcp-lts-20.04 (5.4.0.1143.145) @ focal2026-05-21ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.208.204) @ focal2026-05-21ubuntu
ubuntulinux-virtual (6.8.0-54.56) @ noble2026-05-21ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1058 (5.4.0-1058.62) @ focal2026-05-21ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1006.8) @ noble2026-05-21ubuntu
ubuntulinux-tools-iot (5.4.0.1048.46) @ focal2026-05-21ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-57.59~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-05-21ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.127.126) @ jammy2026-05-21ubuntu
ubuntulinux-tools-ibm-lts-20.04 (5.4.0.1086.115) @ focal2026-05-21ubuntu
ubuntulinux-tools-oracle-lts-20.04 (5.4.0.1138.131) @ focal2026-05-21ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1020.21) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1025.30~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-05-21ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1024.24) @ noble2026-05-21ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1022.22) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1025.30) @ noble2026-05-21ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-05-21ubuntu
ubuntulinux-tools-kvm (5.4.0.1127.123) @ focal2026-05-21ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1129.142~18.04.1) @ bionic2026-05-21ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1129.160) @ focal2026-05-21ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 4.19.323 (fixes >=4.12.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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)
  • every version up to 5.10.234-1: fixed in 5.10.234-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1
  • every version up to 6.1.119-1~deb11u1: fixed in 6.1.119-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (30 versions)
  • every version up to 6.1.115-1: fixed in 6.1.115-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.2-1: fixed in 6.11.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.2-1: fixed in 6.11.2-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(23)

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 6× in last 7d / 32× 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 209 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-47706?
CVE-2024-47706 is a medium vulnerability published on October 21, 2024. In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix possible UAF for bfqq->bic with merge chain 1) initial state, three tasks: Process 1 Process 2 Process 3 (BIC1) (BIC2) (BIC3) | Λ | Λ | Λ | | | | | | V | V | V | bfqq1 bfqq2 bfqq3 process ref: 1 1 1 2) bfqq1 merged…
When was CVE-2024-47706 disclosed?
CVE-2024-47706 was first published on October 21, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-47706 actively exploited?
CVE-2024-47706 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-47706?
CVE-2024-47706 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-47706?
A fix for CVE-2024-47706 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-47706 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-47706

Explore →

Is Your Infrastructure Affected by CVE-2024-47706?

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

Book a Demo →Browse All CVEs