CVE-2026-100076

In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix xmit_frame/xmit_buf leaks on mgnt-frame error paths issue_beacon(), issue_probersp() and issue_asocrsp() obtain a management xmit_frame together with its xmit_buf from the driver's fixed-size management-TX pools via alloc_mgtxmitframe(). On the normal path the frame is handed to dump_mgntframe(), which transfers ownership and eventually returns both objects to their pools (the frame and, for beacons, the buf in rtl8723bs_mgnt_xmit(); other bufs via the pending-xmitbuf/TX-completion path). Several error/edge paths return early after a successful alloc_mgtxmitframe() but before dump_mgntframe(), so ownership is never transferred and neither object is freed: - issue_beacon(): beacon larger than 512 bytes - issue_probersp(): cur_network->ie_length > MAX_IE_SZ - issue_probersp(): kzalloc() of the SSID scratch buffer fails - issue_asocrsp(): pkt_type is neither ASSOCRSP nor REASSOCRSP Because alloc_mgtxmitframe() removes the frame and buf from their free lists (list_del_init) without placing them on any pending list, an orphaned pair is on no list and referenced by nobody, so it is only reclaimed at driver teardown. Repeated hits progressively exhaust the management-TX pools until alloc_mgtxmitframe() returns NULL and the interface can no longer send beacons or probe/assoc responses. Free the frame and buffer on these paths, matching the existing correct error handling in issue_assocreq().

• CWE-401

• https://git.kernel.org/stable/c/17260b5215d4ced17a733e2c027a76290e476fad
• https://git.kernel.org/stable/c/2f5e2752c2b4bad01df4523cfe2b41b702c60f00
• https://git.kernel.org/stable/c/41b8209376dffbd7b0b85c8bc4697d9166ac62efPatch
• https://git.kernel.org/stable/c/6c9f6a3b9fdd31a0836b681053155b5997c0156ePatch
• https://git.kernel.org/stable/c/973a629f19c226c8f6080badea7ccf59cc04233f
• https://git.kernel.org/stable/c/c48e5aa01525577d6b6e782962a5bfb0e1535cb5Patch

Published

Sep 25, 2026

Last Modified

Oct 30, 2026

Status

Undergoing Analysis

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-100070In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-100071In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-100072In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-100073In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-100074In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-100075In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-100077In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-100078In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-100079In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-10008Uninitialized Use in GPU in Google Chrome on Android prior t…6.5
• CVE-2026-100080In the Linux kernel, the following vulnerability has been re…
• CVE-2026-100081In the Linux kernel, the following vulnerability has been re…7.8