CVE-2026-31477 ksmbd: fix memory leaks and NULL deref in smb2_lock()

High 7.5 Published Updated

A NULL pointer dereference in the Linux kernel ksmbd module allows local attackers to cause a system crash via crafted SMB lock requests.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-31477?

CVE-2026-31477 is a high-severity vulnerability in Linux kernel, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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

ksmbd: fix memory leaks and NULL deref in smb2_lock()

smb2_lock() has three error handling issues after list_del() detaches smb_lock from lock_list at no_check_cl:

1) If vfs_lock_file() returns an unexpected error in the non-UNLOCK path, goto out leaks smb_lock and its flock because the out: handler only iterates lock_list and rollback_list, neither of which contains the detached smb_lock.

2) If vfs_lock_file() returns -ENOENT in the UNLOCK path, goto out leaks smb_lock and flock for the same reason. The error code returned to the dispatcher is also stale.

3) In the rollback path, smb_flock_init() can return NULL on allocation failure. The result is dereferenced unconditionally, causing a kernel NULL pointer dereference. Add a NULL check to prevent the crash and clean up the bookkeeping; the VFS lock itself cannot be rolled back without the allocation and will be released at file or connection teardown.

Fix cases 1 and 2 by hoisting the locks_free_lock()/kfree() to before the if(!rc) check in the UNLOCK branch so all exit paths share one free site, and by freeing smb_lock and flock before goto out in the non-UNLOCK branch. Propagate the correct error code in both cases. Fix case 3 by wrapping the VFS unlock in an if(rlock) guard and adding a NULL check for locks_free_lock(rlock) in the shared cleanup.

Found via call-graph analysis using sqry.

Weakness: CWE-476

Which versions are affected by CVE-2026-31477?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-31477?

Apply the vendor's patch.

Is CVE-2026-31477 being exploited?

There is no known exploitation of CVE-2026-31477 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2026-31477, DEBIAN-CVE-2026-31477, GHSA-crxr-hqjj-5w24, ROOT-OS-DEBIAN-12-CVE-2026-31477, ROOT-OS-UBUNTU-2204-CVE-2026-31477, ROOT-OS-UBUNTU-2404-CVE-2026-31477 and 1 more.

Is CVE-2026-31477 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free