Threats Tagged 'cve-2025-39761'
View all threats tagged with 'cve-2025-39761'. 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-2025-39761'
Click on any threat for detailed analysis and mitigation recommendations
0 The kernel packages contain the Linux kernel, the core of any Linux operating system. Security Fix(es): * kernel: security/keys: fix slab-out-of-bounds in key_task_permission (CVE-2024-50301) * kernel: KVM: x86/hyper-v: Skip non-canonical addresses during PV TLB flush (CVE-2025-38351) * kernel: wifi: ath12k: Decrement TID on RX peer frag setup error handling (CVE-2025-39761) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Join the discussion | GCVE Database | 10/06/2025, 23:22:32 UTC Added: 06/25/2026, 21:47:14 UTC |
In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Decrement TID on RX peer frag setup error handling Currently, TID is not decremented before peer cleanup, during error handling path of ath12k_dp_rx_peer_frag_setup(). This could lead to out-of-bounds access in peer->rx_tid[]. Hence, add a decrement operation for TID, before peer cleanup to ensures proper cleanup and prevents out-of-bounds access issues when the RX peer frag setup fails. Found during code review. Compile tested only. Join the discussion | GCVE Database | 09/11/2025, 17:15:00 UTC Added: 07/21/2026, 20:04:07 UTC |
In the Linux kernel, the following vulnerability has been resolved: HID: core: Harden s32ton() against conversion to 0 bits Testing by the syzbot fuzzer showed that the HID core gets a shift-out-of-bounds exception when it tries to convert a 32-bit quantity to a 0-bit quantity. Ideally this should never occur, but there are buggy devices and some might have a report field with size set to zero; we shouldn't reject the report or the device just because of that. Instead, harden the s32ton() routine so that it returns a reasonable result instead of crashing when it is called with the number of bits set to 0 -- the same as what snto32() does. Join the discussion | GCVE Database | 08/19/2025, 17:15:00 UTC Added: 06/25/2026, 21:47:12 UTC |
Showing 1 to 3 of 3 results