CVE-2024-47709

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%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

can: bcm: Clear bo->bcm_proc_read after remove_proc_entry().

syzbot reported a warning in bcm_release(). [0]

The blamed change fixed another warning that is triggered when connect() is issued again for a socket whose connect()ed device has been unregistered.

However, if the socket is just close()d without the 2nd connect(), the remaining bo->bcm_proc_read triggers unnecessary remove_proc_entry() in bcm_release().

Let's clear bo->bcm_proc_read after remove_proc_entry() in bcm_notify().

[0] name '4986' WARNING: CPU: 0 PID: 5234 at fs/proc/generic.c:711 remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Modules linked in: CPU: 0 UID: 0 PID: 5234 Comm: syz-executor606 Not tainted 6.11.0-rc5-syzkaller-00178-g5517ae241919 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Code: ff eb 05 e8 cb 1e 5e ff 48 8b 5c 24 10 48 c7 c7 e0 f7 aa 8e e8 2a 38 8e 09 90 48 c7 c7 60 3a 1b 8c 48 89 de e8 da 42 20 ff 90 <0f> 0b 90 90 48 8b 44 24 18 48 c7 44 24 40 0e 36 e0 45 49 c7 04 07 RSP: 0018:ffffc9000345fa20 EFLAGS: 00010246 RAX: 2a2d0aee2eb64600 RBX: ffff888032f1f548 RCX: ffff888029431e00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000345fb08 R08: ffffffff8155b2f2 R09: 1ffff1101710519a R10: dffffc0000000000 R11: ffffed101710519b R12: ffff888011d38640 R13: 0000000000000004 R14: 0000000000000000 R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fcfb52722f0 CR3: 000000000e734000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: bcm_release+0x250/0x880 net/can/bcm.c:1578 __sock_release net/socket.c:659 [inline] sock_close+0xbc/0x240 net/socket.c:1421 __fput+0x24a/0x8a0 fs/file_table.c:422 task_work_run+0x24f/0x310 kernel/task_work.c:228 exit_task_work include/linux/task_work.h:40 [inline] do_exit+0xa2f/0x27f0 kernel/exit.c:882 do_group_exit+0x207/0x2c0 kernel/exit.c:1031 __do_sys_exit_group kernel/exit.c:1042 [inline] __se_sys_exit_group kernel/exit.c:1040 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1040 x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fcfb51ee969 Code: Unable to access opcode bytes at 0x7fcfb51ee93f. RSP: 002b:00007ffce0109ca8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fcfb51ee969 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 00007fcfb526f3b0 R08: ffffffffffffffb8 R09: 0000555500000000 R10: 0000555500000000 R11: 0000000000000246 R12: 00007fcfb526f3b0 R13: 0000000000000000 R14: 00007fcfb5271ee0 R15: 00007fcfb51bf160

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

October 21, 2024

Last Modified

May 12, 2026

References (13)

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-05-21ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1023.25) @ noble2026-05-21ubuntu
ubuntulinux-tools-raspi (6.8.0-1019.23) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1025.30) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1025.30~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-kvm (5.4.0.1127.123) @ focal2026-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-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-05-21ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-05-21ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-57.59~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-iot (5.4.0.1048.46) @ focal2026-05-21ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1129.160) @ focal2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-21ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1071.71) @ jammy2026-05-21ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1022.25.2) @ noble2026-05-21ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.127.126) @ jammy2026-05-21ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1073.73) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1078.87~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.127.137~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1039.43) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1078.76) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.208.228~18.04.1) @ bionic2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1058 (5.4.0-1058.62) @ focal2026-05-21ubuntu
ubuntulinux-tools-ibm-lts-20.04 (5.4.0.1086.115) @ focal2026-05-21ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1020.21) @ noble2026-05-21ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-05-21ubuntu
ubuntulinux-virtual (6.8.0-54.56) @ noble2026-05-21ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1006.8) @ noble2026-05-21ubuntu
linuxKernel @ 4.19.323—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 rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)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~deb11u16.1.119-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (30 versions)6.1.115-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.11.2-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.11.2-1—

All Vendor Advisories

(25)

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 / 33× 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 185 total refreshes for this CVE.

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

Related CVEs

Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.

Frequently asked(5)

What is CVE-2024-47709?
CVE-2024-47709 is a medium vulnerability published on October 21, 2024. In the Linux kernel, the following vulnerability has been resolved: can: bcm: Clear bo->bcmprocread after removeprocentry(). syzbot reported a warning in bcm_release(). [0] The blamed change fixed another warning that is triggered when connect() is issued again for a socket whose connect()ed device…
When was CVE-2024-47709 disclosed?
CVE-2024-47709 was first published in the National Vulnerability Database on October 21, 2024, with the most recent update on May 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-47709 actively exploited?
CVE-2024-47709 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 83.5% of all scored CVEs.
What is the CVSS score of CVE-2024-47709?
CVE-2024-47709 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-47709?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-47709, 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-2024-47709

Explore →

Is Your Infrastructure Affected by CVE-2024-47709?

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

Start Free Scan →Browse All CVEs