Threats Tagged 'cve-2026-53253'
View all threats tagged with 'cve-2026-53253'. 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-53253'
Click on any threat for detailed analysis and mitigation recommendations
0 Multiple security vulnerabilities affecting the SUSE Linux Enterprise 15 SP4 RT kernel were addressed in a security update. The update fixes a range of issues including Bluetooth event handling, IPv6 ICMP error processing, use-after-free conditions, stale data exposure, buffer overflows, locking issues, and memory management bugs. These vulnerabilities impact kernel components such as Bluetooth, networking, crypto, KVM virtualization, and filesystem handling. The update mitigates these issues to improve system stability and security. Join the discussion | GCVE Database | 07/10/2026, 09:24:47 UTC Added: 06/29/2026, 22:11:28 UTC |
0 A security update for the SUSE Linux Enterprise 11 SP4 kernel addresses multiple vulnerabilities, including use-after-free bugs, race conditions, and improper handling of network protocols. The update fixes 10 distinct CVEs affecting components such as SCSI, TCP, bonding, ALSA, KVM, networking, and Bluetooth subsystems. These vulnerabilities could lead to memory corruption or unexpected behavior in kernel modules. Join the discussion | GCVE Database | 07/10/2026, 09:09:30 UTC Added: 07/11/2026, 09:38:21 UTC |
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: bnep: reject short frames before parsing A BNEP peer can send a short BNEP SDU. bnep_rx_frame() reads the packet type byte immediately and, for control packets, reads the control opcode and setup UUID-size byte before proving that those bytes are present. bnep_rx_control() also dereferences the control opcode without rejecting an empty control payload. Use skb_pull_data() for the fixed fields in bnep_rx_frame() so a NULL return gates each dereference. Split the control handler so the frame path can pass an opcode that has already been pulled, and keep the byte-buffer wrapper for extension control payloads. For BNEP_SETUP_CONN_REQ, name the UUID-size byte before pulling the setup payload. struct bnep_setup_conn_req carries destination and source service UUIDs after that byte, each uuid_size bytes, so the parser now documents that tuple explicitly instead of leaving the pull length as an opaque multiplication. Validation reproduced this kernel report: KASAN slab-out-of-bounds in bnep_rx_frame.isra.0+0x130c/0x1790 The buggy address belongs to the object at ffff88800c0f7908 which belongs to the cache kmalloc-8 of size 8 The buggy address is located 0 bytes to the right of allocated 1-byte region [ffff88800c0f7908, ffff88800c0f7909) Read of size 1 Call trace: dump_stack_lvl+0xb3/0x140 (?:?) print_address_description+0x57/0x3a0 (?:?) bnep_rx_frame+0x130c/0x1790 (net/bluetooth/bnep/core.c:306) print_report+0xb9/0x2b0 (?:?) __virt_addr_valid+0x1ba/0x3a0 (?:?) srso_alias_return_thunk+0x5/0xfbef5 (?:?) kasan_addr_to_slab+0x21/0x60 (?:?) kasan_report+0xe0/0x110 (?:?) process_one_work+0xfce/0x17e0 (kernel/workqueue.c:3200) worker_thread+0x65c/0xe40 (?:?) __kthread_parkme+0x184/0x230 (?:?) kthread+0x35e/0x470 (?:?) _raw_spin_unlock_irq+0x28/0x50 (?:?) ret_from_fork+0x586/0x870 (?:?) __switch_to+0x74f/0xdc0 (?:?) ret_from_fork_asm+0x1a/0x30 (?:?) Join the discussion | GCVE Database | 06/25/2026, 09:16:00 UTC Added: 07/17/2026, 10:15:59 UTC |
Showing 1 to 3 of 3 results