Vulnary
← back to the feed
Critical· 9.1official fix available

CVE-2023-52441

A critical flaw in the Linux kernel’s SMB server (ksmbd) allows an attacker to crash the system by sending a specific sequence of SMB requests. The bug was fixed in a kernel patch that ignores SMB1 packets after the SMB2 negotiation flag is cleared. Users should update to a kernel version that includes this patch.

publishedFeb 21, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.1
critical · how bad it is
exploitation · epss
<1%
49th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 5, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel, specifically the ksmbd SMB server component.

02

Real-world impact

An attacker could send a crafted SMB2 negotiate request followed by an SMB1 negotiate request to trigger an out‑of‑bounds memory access, causing the kernel to crash and resulting in a denial of service.

03

Why this severity

The CVSS score of 9.1 reflects that the vulnerability can be exploited remotely over the network (AV:N), requires no user interaction or privileges (PR:N, UI:N), and has a low attack complexity (AC:L). It fully compromises confidentiality and availability (C:H, A:H) while integrity is unaffected.

04

What to do about it

official fix available
recommended steps
  1. 011. Identify the current Linux kernel version you are running.
  2. 022. Update the kernel to a version that includes the ksmbd patch for init_smb2_rsp_hdr().
  3. 033. Reboot the system to load the updated kernel.

NVD-referenced vendor advisory

05

Timeline

  1. Feb 21, 2024 · Feb 21, 2024
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 6, 2026 · 8h ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactNone
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →