CVE-2026-23220

N/A Unknown

📋 TL;DR

A vulnerability in the Linux kernel's ksmbd SMB server module causes an infinite loop when processing malformed SMB2 requests with invalid signatures. This leads to denial of service through high CPU consumption and log flooding. Systems running affected Linux kernel versions with ksmbd enabled are vulnerable.

💻 Affected Systems

Products:
  • Linux kernel
Versions: Kernel versions with the vulnerable ksmbd code (specific versions not provided in CVE, but references indicate stable kernel patches)
Operating Systems: Linux distributions with affected kernel versions
Default Config Vulnerable: ✅ No
Notes: Only vulnerable if ksmbd module is loaded and enabled. Many distributions don't enable ksmbd by default.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete denial of service on affected systems due to 100% CPU consumption, potentially requiring physical reboot if kernel becomes unresponsive.

🟠

Likely Case

Degraded system performance, log flooding, and potential service disruption for SMB file sharing services.

🟢

If Mitigated

Minimal impact if ksmbd is disabled or systems are patched; normal operations continue.

🌐 Internet-Facing: MEDIUM - Requires SMB service exposure and ability to send crafted packets, but SMB should not typically be internet-facing.
🏢 Internal Only: MEDIUM - Internal attackers or compromised systems could trigger the infinite loop to disrupt services.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires sending specially crafted SMB2 packets with invalid signatures to trigger the error path.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Kernel versions containing commit 5accdc5b7f28a81bbc5880ac0b8886e60c86e8c8 or later

Vendor Advisory: https://git.kernel.org/stable/c/5accdc5b7f28a81bbc5880ac0b8886e60c86e8c8

Restart Required: Yes

Instructions:

1. Update Linux kernel to patched version from your distribution. 2. Reboot system to load new kernel. 3. Verify ksmbd module loads correctly if needed.

🔧 Temporary Workarounds

Disable ksmbd module

linux

Prevent loading of the vulnerable ksmbd kernel module

echo 'blacklist ksmbd' >> /etc/modprobe.d/blacklist-ksmbd.conf
rmmod ksmbd

Block SMB traffic

linux

Use firewall rules to block SMB traffic to vulnerable systems

iptables -A INPUT -p tcp --dport 445 -j DROP
iptables -A INPUT -p tcp --dport 139 -j DROP

🧯 If You Can't Patch

  • Disable ksmbd module if not required for operations
  • Implement network segmentation to restrict SMB access to trusted sources only

🔍 How to Verify

Check if Vulnerable:

Check if ksmbd module is loaded: lsmod | grep ksmbd. If loaded and kernel version is unpatched, system is vulnerable.

Check Version:

uname -r

Verify Fix Applied:

Check kernel version is patched: uname -r and verify against distribution security advisories. Confirm ksmbd module loads without issues.

📡 Detection & Monitoring

Log Indicators:

  • Repeated 'bad smb2 signature' messages in kernel logs (dmesg)
  • High CPU usage by kernel processes

Network Indicators:

  • Multiple SMB2 connection attempts with malformed packets
  • Unusual SMB traffic patterns

SIEM Query:

source="kernel" AND "bad smb2 signature" OR process_cpu_usage>90 AND process_name="ksmbd"

🔗 References

📤 Share & Export