nday
CVE-2023-52751

smb: client: fix use-after-free in smb2_query_info_compound()

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags weakness typeuse-after-free accesslocalno user interaction productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

use-after-free
CWE-416, stated by NVD's analysts
local
AV:L in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
7.8 HIGH v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2024-05-21T15:30Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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

smb: client: fix use-after-free in smb2_query_info_compound()

The following UAF was triggered when running fstests generic/072 with KASAN enabled against Windows Server 2022 and mount options 'multichannel,max_channels=2,vers=3.1.1,mfsymlinks,noperm'

BUG: KASAN: slab-use-after-free in smb2_query_info_compound+0x423/0x6d0 [cifs]
Read of size 8 at addr ffff888014941048 by task xfs_io/27534

CPU: 0 PID: 27534 Comm: xfs_io Not tainted 6.6.0-rc7 #1
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS
rel-1.16.2-3-gd478f380-rebuilt.opensuse.org 04/01/2014
Call Trace:
 dump_stack_lvl+0x4a/0x80
 print_report+0xcf/0x650
 ? srso_alias_return_thunk+0x5/0x7f
 ? srso_alias_return_thunk+0x5/0x7f
 ? __phys_addr+0x46/0x90
 kasan_report+0xda/0x110
 ? smb2_query_info_compound+0x423/0x6d0 [cifs]
 ? smb2_query_info_compound+0x423/0x6d0 [cifs]
 smb2_query_info_compound+0x423/0x6d0 [cifs]
 ? __pfx_smb2_query_info_compound+0x10/0x10 [cifs]
 ? srso_alias_return_thunk+0x5/0x7f
 ? __stack_depot_save+0x39/0x480
 ? kasan_save_stack+0x33/0x60
 ? kasan_set_track+0x25/0x30
 ? ____kasan_slab_free+0x126/0x170
 smb2_queryfs+0xc2/0x2c0 [cifs]
 ? __pfx_smb2_queryfs+0x10/0x10 [cifs]
 ? __pfx___lock_acquire+0x10/0x10
 smb311_queryfs+0x210/0x220 [cifs]
 ? __pfx_smb311_queryfs+0x10/0x10 [cifs]
 ? srso_alias_return_thunk+0x5/0x7f
 ? __lock_acquire+0x480/0x26c0
 ? lock_release+0x1ed/0x640
 ? srso_alias_return_thunk+0x5/0x7f
 ? do_raw_spin_unlock+0x9b/0x100
 cifs_statfs+0x18c/0x4b0 [cifs]
 statfs_by_dentry+0x9b/0xf0
 fd_statfs+0x4e/0xb0
 __do_sys_fstatfs+0x7f/0xe0
 ? __pfx___do_sys_fstatfs+0x10/0x10
 ? srso_alias_return_thunk+0x5/0x7f
 ? lockdep_hardirqs_on_prepare+0x136/0x200
 ? srso_alias_return_thunk+0x5/0x7f
 do_syscall_64+0x3f/0x90
 entry_SYSCALL_64_after_hwframe+0x6e/0xd8

Allocated by task 27534:
 kasan_save_stack+0x33/0x60
 kasan_set_track+0x25/0x30
 __kasan_kmalloc+0x8f/0xa0
 open_cached_dir+0x71b/0x1240 [cifs]
 smb2_query_info_compound+0x5c3/0x6d0 [cifs]
 smb2_queryfs+0xc2/0x2c0 [cifs]
 smb311_queryfs+0x210/0x220 [cifs]
 cifs_statfs+0x18c/0x4b0 [cifs]
 statfs_by_dentry+0x9b/0xf0
 fd_statfs+0x4e/0xb0
 __do_sys_fstatfs+0x7f/0xe0
 do_syscall_64+0x3f/0x90
 entry_SYSCALL_64_after_hwframe+0x6e/0xd8

Freed by task 27534:
 kasan_save_stack+0x33/0x60
 kasan_set_track+0x25/0x30
 kasan_save_free_info+0x2b/0x50
 ____kasan_slab_free+0x126/0x170
 slab_free_freelist_hook+0xd0/0x1e0
 __kmem_cache_free+0x9d/0x1b0
 open_cached_dir+0xff5/0x1240 [cifs]
 smb2_query_info_compound+0x5c3/0x6d0 [cifs]
 smb2_queryfs+0xc2/0x2c0 [cifs]

This is a race between open_cached_dir() and cached_dir_lease_break() where the cache entry for the open directory handle receives a lease break while creating it. And before returning from open_cached_dir(), we put the last reference of the new @cfid because of !@cfid->has_lease.

Besides the UAF, while running xfstests a lot of missed lease breaks have been noticed in tests that run several concurrent statfs(2) calls on those cached fids

CIFS: VFS: \\w22-root1.gandalf.test No task to wake, unknown frame... CIFS: VFS: \\w22-root1.gandalf.test Cmd: 18 Err: 0x0 Flags: 0x1... CIFS: VFS: \\w22-root1.gandalf.test smb buf 00000000715bfe83 len 108 CIFS: VFS: Dump pending requests: CIFS: VFS: \\w22-root1.gandalf.test No task to wake, unknown frame...

CIFS: VFS: \\w22-root1.gandalf.test Cmd: 18 Err: 0x0 Flags: 0x1...
CIFS: VFS: \\w22-root1.gandalf.test smb buf 000000005aa7316e len 108
...

To fix both, in open_cached_dir() ensure that @cfid->has_lease is set right before sending out compounded request so that any potential lease break will be get processed by demultiplex thread while we're still caching @cfid. And, if open failed for some reason, re-check @cfid->has_lease to decide whether or not put lease reference.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA Linux.

Event log

+DISdisclosed

CVE record published by Linux. CVSS 7.8, high.

src cvelist · nday , bulk import · raw
{
  "id": 309031,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2023-52751",
  "occurred_at": "2024-05-21T15:30:40.226Z",
  "observed_at": "2026-11-13T05:38:14.046808Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 7.8,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2024-09-10T15:37:15.794672Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2024-05-21T15:30:40.226Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.