CVE-2024-46796

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 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:

smb: client: fix double put of @cfile in smb2_set_path_size()

If smb2_compound_op() is called with a valid @cfile and returned -EINVAL, we need to call cifs_get_writable_path() before retrying it as the reference of @cfile was already dropped by previous call.

This fixes the following KASAN splat when running fstests generic/013 against Windows Server 2022:

CIFS: Attempting to mount //w22-fs0/scratch run fstests generic/013 at 2024-09-02 19:48:59 ================================================================== BUG: KASAN: slab-use-after-free in detach_if_pending+0xab/0x200 Write of size 8 at addr ffff88811f1a3730 by task kworker/3:2/176

CPU: 3 UID: 0 PID: 176 Comm: kworker/3:2 Not tainted 6.11.0-rc6 #2 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 Workqueue: cifsoplockd cifs_oplock_break [cifs] Call Trace: dump_stack_lvl+0x5d/0x80 ? detach_if_pending+0xab/0x200 print_report+0x156/0x4d9 ? detach_if_pending+0xab/0x200 ? __virt_addr_valid+0x145/0x300 ? __phys_addr+0x46/0x90 ? detach_if_pending+0xab/0x200 kasan_report+0xda/0x110 ? detach_if_pending+0xab/0x200 detach_if_pending+0xab/0x200 timer_delete+0x96/0xe0 ? __pfx_timer_delete+0x10/0x10 ? rcu_is_watching+0x20/0x50 try_to_grab_pending+0x46/0x3b0 __cancel_work+0x89/0x1b0 ? __pfx___cancel_work+0x10/0x10 ? kasan_save_track+0x14/0x30 cifs_close_deferred_file+0x110/0x2c0 [cifs] ? __pfx_cifs_close_deferred_file+0x10/0x10 [cifs] ? __pfx_down_read+0x10/0x10 cifs_oplock_break+0x4c1/0xa50 [cifs] ? __pfx_cifs_oplock_break+0x10/0x10 [cifs] ? lock_is_held_type+0x85/0xf0 ? mark_held_locks+0x1a/0x90 process_one_work+0x4c6/0x9f0 ? find_held_lock+0x8a/0xa0 ? __pfx_process_one_work+0x10/0x10 ? lock_acquired+0x220/0x550 ? __list_add_valid_or_report+0x37/0x100 worker_thread+0x2e4/0x570 ? __kthread_parkme+0xd1/0xf0 ? __pfx_worker_thread+0x10/0x10 kthread+0x17f/0x1c0 ? kthread+0xda/0x1c0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x31/0x60 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30

Allocated by task 1118: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 cifs_new_fileinfo+0xc8/0x9d0 [cifs] cifs_atomic_open+0x467/0x770 [cifs] lookup_open.isra.0+0x665/0x8b0 path_openat+0x4c3/0x1380 do_filp_open+0x167/0x270 do_sys_openat2+0x129/0x160 __x64_sys_creat+0xad/0xe0 do_syscall_64+0xbb/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 83: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x70 poison_slab_object+0xe9/0x160 __kasan_slab_free+0x32/0x50 kfree+0xf2/0x300 process_one_work+0x4c6/0x9f0 worker_thread+0x2e4/0x570 kthread+0x17f/0x1c0 ret_from_fork+0x31/0x60 ret_from_fork_asm+0x1a/0x30

Last potentially related work creation: kasan_save_stack+0x30/0x50 __kasan_record_aux_stack+0xad/0xc0 insert_work+0x29/0xe0 __queue_work+0x5ea/0x760 queue_work_on+0x6d/0x90 _cifsFileInfo_put+0x3f6/0x770 [cifs] smb2_compound_op+0x911/0x3940 [cifs] smb2_set_path_size+0x228/0x270 [cifs] cifs_set_file_size+0x197/0x460 [cifs] cifs_setattr+0xd9c/0x14b0 [cifs] notify_change+0x4e3/0x740 do_truncate+0xfa/0x180 vfs_truncate+0x195/0x200 __x64_sys_truncate+0x109/0x150 do_syscall_64+0xbb/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

September 18, 2024

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

smb: client: fix double put of @cfile in smb2_set_path_size() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: client: fix double put of @cfile in smb2_set_path_size() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/762099898309218b4a7954f3d49e985dc4dfd638
generic

smb: client: fix double put of @cfile in smb2_set_path_size() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a72d1edb0843e4c927a4096f81e631031c25c28

Vendor Advisories for CVE-2024-46796(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.6.51osv

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.10.11-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.10.11-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× 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.

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

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

Frequently asked(5)

What is CVE-2024-46796?
CVE-2024-46796 is a high vulnerability published on September 18, 2024. In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double put of @cfile in smb2setpath_size() If smb2compoundop() is called with a valid @cfile and returned -EINVAL, we need to call cifsgetwritable_path() before retrying it as the reference of @cfile was already…
When was CVE-2024-46796 disclosed?
CVE-2024-46796 was first published in the National Vulnerability Database on September 18, 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-46796 actively exploited?
CVE-2024-46796 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 63.3% of all scored CVEs.
What is the CVSS score of CVE-2024-46796?
CVE-2024-46796 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-46796?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-46796, 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-46796

Explore →

Is Your Infrastructure Affected by CVE-2024-46796?

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