Threats Tagged 'cve-2026-64139'
View all threats tagged with 'cve-2026-64139'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-64139'
Click on any threat for detailed analysis and mitigation recommendations
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix SID memory leak in set_posix_acl_entries_dacl() on overflow Commit 299f962c0b02 ("ksmbd: use check_add_overflow() to prevent u16 DACL size overflow") added check_add_overflow() guards that break out of the ACE-building loops in set_posix_acl_entries_dacl() when the accumulated DACL size would wrap past 65535. However, each iteration allocates a struct smb_sid via kmalloc_obj() at the top of the loop and relies on the kfree(sid) call at the end of the loop body (the 'pass_same_sid' label in the first loop, and the explicit kfree at the tail of the second loop) to release it. The newly introduced 'break' statements bypass those kfree() calls, leaking the sid buffer every time an overflow is detected. A malicious or malformed file with enough POSIX ACL entries to trip the overflow check will leak one or more struct smb_sid allocations on every request that touches the file's DACL, providing a trivial kernel memory exhaustion vector. Free sid before breaking out of the loops to plug the leak. Join the discussion | GCVE Database | 07/20/2026, 00:00:00 UTC Added: 07/21/2026, 19:58:52 UTC |
A memory leak vulnerability in the Linux kernel's ksmbd component was fixed. The issue occurs in the set_posix_acl_entries_dacl() function where an overflow check causes early loop termination but bypasses memory free calls, leaking allocated memory. This leak can be triggered by a malicious or malformed file with many POSIX ACL entries, potentially leading to kernel memory exhaustion. The fix involves freeing allocated memory before breaking out of the loops to prevent the leak. Join the discussion | GCVE Database | 07/19/2026, 18:31:53 UTC Added: 07/19/2026, 19:38:16 UTC |
Showing 1 to 2 of 2 results