PatchSiren cyber security CVE debrief
CVE-2026-23428 Linux CVE debrief
A use-after-free vulnerability exists in the Linux kernel's ksmbd module when handling compound requests. This issue arises because smb2_get_ksmbd_tcon() reuses work->tcon in compound requests without validating tcon->t_state. Specifically, if a prior command in the compound (SMB2_TREE_DISCONNECT) sets t_state to TREE_DISCONNECTED and frees share_conf via ksmbd_share_config_put(), subsequent commands dereference the freed share_conf through work->tcon->share_conf. This can lead to a use-after-free error.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- CRITICAL 9.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-04-03
- Original CVE updated
- 2026-10-19
- Advisory published
- 2026-04-03
- Advisory updated
- 2026-10-19
Who should care
Linux kernel developers and maintainers, Linux distribution maintainers, system administrators responsible for Linux systems, security teams monitoring Linux infrastructure, operators managing Linux-based platforms, and vulnerability management teams responsible for Linux systems.
Why it matters
This vulnerability in the Linux kernel's ksmbd module requires immediate attention from Linux system administrators and security teams. The use-after-free error can lead to potential remote code execution, denial of service, or elevation of privileges on affected systems. It is crucial to review and apply patches from Linux kernel maintainers, implement additional monitoring, restrict access to affected systems, and verify system configurations and inventory for exposure.
- Potential for remote code execution or denial of service
- Elevation of privileges on affected systems
- Data tampering or unauthorized access
Technical summary
The ksmbd module in the Linux kernel is vulnerable to a use-after-free error when handling compound requests. This occurs because the tcon->t_state is not validated before reusing work->tcon. An attacker could potentially exploit this by crafting a sequence of SMB commands that trigger the free of share_conf and then attempt to access it, leading to a use-after-free error. This vulnerability can lead to potential remote code execution, denial of service, or elevation of privileges on affected systems. Linux kernel developers and maintainers should review and apply patches to update the ksmbd module. System administrators responsible for Linux systems should implement additional monitoring to detect potential
Defensive priority
High
Recommended defensive actions
- Review and apply patches from Linux kernel maintainers to update ksmbd module
- Implement additional monitoring to detect potential exploitation attempts
- Restrict access to affected systems and limit SMBv2 compound request usage
- Verify system configurations and inventory for exposure
- Conduct vulnerability scanning to identify potentially affected systems
- Isolate affected systems from the network until patches are applied
- Review system logs for signs of exploitation
Evidence notes
The vulnerability was reported via a KASAN (Kernel Address Sanitizer) report, which indicated a slab-use-after-free error in smb2_write. The issue was resolved through a series of patches applied to the Linux kernel's ksmbd module.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-23428 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-23428
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-23428 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-23428
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
ksmbd: fix use-after-free of share_conf in compound request
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/23xxx/CVE-2026-23428.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/d08417981155883068b7260d9500ca306a03edac
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/eae0dc86f71e6f3294c0cd7ffc05039258d243af
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/806f13752652216db0c309392b4db3e64eeed4f2
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/c742b46a153d3ff95ff0825ab1950c87b9e14470
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/7f7468fd2a7554cea91b7d430335a3dbf01dcc09
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/a5929c2020ce54e1dcbd1078c0f30b8aaf73c105
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/c33615f995aee80657b9fdfbc4ee7f49c2bd733d
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.