---
id: CVE-2023-32246
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  ksmbd: call rcu_barrier() in ksmbd_server_exit()

  racy issue is triggered the bug by racing between closing a connection
  and rmmod
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  ksmbd: call rcu_barrier() in ksmbd_server_exit()

  racy issue is triggered the bug by racing between closing a connection
  and rmmod. In ksmbd, rcu_barrier() is not calle…
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 5.15, < 5.15.111'
  - 'linux_kernel >= 5.16, < 6.1.28'
  - 'linux_kernel >= 6.2, < 6.2.15'
  - 'linux_kernel >= 6.3, < 6.3.2'
patched:
  - linux_kernel 6.3.2
published: '2025-08-16'
updated: '2026-08-15'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2023-32246'
references:
  - url: 'https://git.kernel.org/stable/c/5a7090ccc242ab009ee7769e9d7fad6644dbe9bd'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/b80422474ffe44cb5e813cd6da1f1c6bc50fd9d2'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c053e389db0d892e2ff5a60ec5e533b976503795'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d4174505016a3b2996eb7ff1530dcabbf15d47b6'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/eb307d09fe15844fdaebeb8cc8c9b9e925430aa5'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00172
epssPercentile: 0.05888
ingestedAt: '2026-08-15T13:26:45.207Z'
---

## Overview

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

ksmbd: call rcu_barrier() in ksmbd_server_exit()

racy issue is triggered the bug by racing between closing a connection
and rmmod. In ksmbd, rcu_barrier() is not called at module unload time,
so nothing prevents ksmbd from getting unloaded while it still has RCU
callbacks pending. It leads to trigger unintended execution of kernel
code locally and use to defeat protections such as Kernel Lockdown

## Affected

- `linux_kernel >= 5.15, < 5.15.111`
- `linux_kernel >= 5.16, < 6.1.28`
- `linux_kernel >= 6.2, < 6.2.15`
- `linux_kernel >= 6.3, < 6.3.2`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.3.2`