CVE-2024-46796: smb: client: fix double put of @cfile in smb2_set_path_size()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.44% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 5a72d1edb0843e4c927a4096f81e631031c25c28, 6.6.51, 762099898309218b4a7954f3d49e985dc4dfd638; Azure Linux 3.0 ARM 6.6.51.1-5; Azure Linux 3.0 x64 6.6.51.1-5.
- Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 7.8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 5a72d1edb0843e4c927a4096f81e631031c25c28, 6.6.51, 762099898309218b4a7954f3d49e985dc4dfd638; Azure Linux 3.0 ARM 6.6.51.1-5; Azure Linux 3.0 x64 6.6.51.1-5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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: <TASK> 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 </TASK> 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
- Published
- Sep 18, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.4% · 38th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 9.8
- 2.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.6.32 and later · before 6.6.51
- linux linux kernel6.9 and later · before 6.10.10
- linux linux kernel6.11
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.9affected
- 1e60bc0e954389af82f1d9a85f13a63f6572350f and later · before 5a72d1edb0843e4c927a4096f81e631031c25c28affected · git
- 71f15c90e785d1de4bcd65a279e7256684c25c0d and later · before 762099898309218b4a7954f3d49e985dc4dfd638affected · git
- 71f15c90e785d1de4bcd65a279e7256684c25c0d and later · before f9c169b51b6ce20394594ef674d6b10efba31220affected · git
- 6.6.32 and later · before 6.6.51affected · semver
- before 6.9not affected · semver
- 6.6.51 and later · up to and including 6.6.*not affected · semver
- 6.10.10 and later · up to and including 6.10.*not affected · semver
- 6.11 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.10.11-1 | 6.10.11-1 |
| openSUSE:Leap 15.6 | dtb-aarch64 | before 6.4.0-150600.23.47.1 | 6.4.0-150600.23.47.1 |
| openSUSE:Leap 15.6 | kernel-64kb | before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
| openSUSE:Leap 15.6 | kernel-azure | before 6.4.0-150600.8.34.2 | 6.4.0-150600.8.34.2 |
| openSUSE:Leap 15.6 | kernel-debug | before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
| openSUSE:Leap 15.6 | kernel-default | before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
| openSUSE:Leap 15.6 | kernel-default-base | before 6.4.0-150600.23.47.2.150600.12.20.2 | 6.4.0-150600.23.47.2.150600.12.20.2 |
| openSUSE:Leap 15.6 | kernel-docs | before 6.4.0-150600.23.47.1 | 6.4.0-150600.23.47.1 |
| openSUSE:Leap 15.6 | kernel-kvmsmall | before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
| openSUSE:Leap 15.6 | kernel-obs-build | before 6.4.0-150600.23.47.1 | 6.4.0-150600.23.47.1 |
| openSUSE:Leap 15.6 | kernel-obs-qa | before 6.4.0-150600.23.47.1 | 6.4.0-150600.23.47.1 |
| openSUSE:Leap 15.6 | kernel-rt | before 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 |
| openSUSE:Leap 15.6 | kernel-rt_debug | before 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 |
| openSUSE:Leap 15.6 | kernel-source | before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
| openSUSE:Leap 15.6 | kernel-source-azure | before 6.4.0-150600.8.34.2 | 6.4.0-150600.8.34.2 |
| openSUSE:Leap 15.6 | kernel-source-rt | before 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 |
| openSUSE:Leap 15.6 | kernel-syms | before 6.4.0-150600.23.47.1 | 6.4.0-150600.23.47.1 |
| openSUSE:Leap 15.6 | kernel-syms-azure | before 6.4.0-150600.8.34.1 | 6.4.0-150600.8.34.1 |
| openSUSE:Leap 15.6 | kernel-syms-rt | before 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 |
| openSUSE:Leap 15.6 | kernel-zfcpdump | before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_10 | before 1-150600.13.5.1 | 1-150600.13.5.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_10 | before 1-150600.1.5.1 | 1-150600.1.5.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | kernel-64kb | before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | kernel-default | before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
+13
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-46794Sep 18, 2024 · x86/tdx: Fix data leak in mmio_read()13Monitor
- ← EarlierCVE-2024-46795Sep 18, 2024 · ksmbd: unset the binding mark of a reused connection22Monitor
- Later →CVE-2024-46797Sep 18, 2024 · powerpc/qspinlock: Fix deadlock in MCS queue22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 5a72d1edb0843e4c927a4096f81e631031c25c28 | Vendor (CNA) |
| Linux Linux | 6.6.51 | Vendor (CNA) |
| Linux Linux | 762099898309218b4a7954f3d49e985dc4dfd638 | Vendor (CNA) |
| Linux Linux | f9c169b51b6ce20394594ef674d6b10efba31220 | Vendor (CNA) |
| Azure Linux 3.0 ARM | 6.6.51.1-5 · kernel | Microsoft (MSRC) |
| Azure Linux 3.0 x64 | 6.6.51.1-5 · kernel | Microsoft (MSRC) |
| debian:linux | 6.10.11-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.4.0-150600.23.47.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.4.0-150600.23.47.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-azure | 6.4.0-150600.8.34.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-debug | 6.4.0-150600.23.47.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default | 6.4.0-150600.23.47.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.4.0-150600.23.47.2.150600.12.20.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-rt | 6.4.0-150600.10.34.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-rt_debug | 6.4.0-150600.10.34.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-source-azure | 6.4.0-150600.8.34.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-source-rt | 6.4.0-150600.10.34.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-syms-azure | 6.4.0-150600.8.34.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-syms-rt | 6.4.0-150600.10.34.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:kernel-64kb | 6.4.0-150600.23.47.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-azure | 6.4.0-150600.8.34.2 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-150600.23.47.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-default-base | 6.4.0-150600.23.47.2.150600.12.20.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_10 | 1-150600.1.5.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-150600.10.34.1 · SUSE:Real Time Module 15 SP6 | Package registry (OSV) |
| suse:kernel-rt_debug | 6.4.0-150600.10.34.1 · SUSE:Real Time Module 15 SP6 | Package registry (OSV) |
| suse:kernel-source | 6.4.0-150600.23.47.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-source-azure | 6.4.0-150600.8.34.2 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-150600.10.34.1 · SUSE:Real Time Module 15 SP6 | Package registry (OSV) |
| suse:kernel-syms-azure | 6.4.0-150600.8.34.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
+1
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1498 · Sep 19, 2024(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.