Threats Tagged 'cve-2025-71132'
View all threats tagged with 'cve-2025-71132'. 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-71132'
Click on any threat for detailed analysis and mitigation recommendations
This Red Hat Security Advisory addresses multiple vulnerabilities and bugs in the Linux kernel packages for Red Hat Enterprise Linux 8. The update includes fixes for several use-after-free issues, out-of-bounds accesses, and other kernel-level security flaws. These vulnerabilities affect core kernel components such as CPU hotplug handling, network bonding, NFS, RDMA, and IPv6. The advisory recommends updating the kernel packages and rebooting the system to apply the fixes. Join the discussion | GCVE Database | 09/03/2026, 04:54:40 UTC Added: 09/03/2026, 15:16:44 UTC |
Red Hat has released a security advisory for the kernel-rt packages in Red Hat Enterprise Linux 8, addressing multiple security vulnerabilities including use-after-free, out-of-bounds writes, and other kernel bugs. These vulnerabilities affect the Real Time Linux Kernel used for systems requiring high determinism. The update includes fixes for 14 CVEs covering various kernel subsystems such as CPU hotplug handling, network bonding, zram, pNFS, NFSv4, RDMA, and IPv6. The advisory also includes bug fixes and enhancements unrelated to security. Systems must be rebooted after applying the update to ensure the fixes take effect. Join the discussion | GCVE Database | 09/03/2026, 04:15:14 UTC Added: 09/03/2026, 15:16:44 UTC |
In the Linux kernel, the following vulnerability has been resolved: smc91x: fix broken irq-context in PREEMPT_RT When smc91x.c is built with PREEMPT_RT, the following splat occurs in FVP_RevC: [ 13.055000] smc91x LNRO0003:00 eth0: link up, 10Mbps, half-duplex, lpa 0x0000 [ 13.062137] BUG: workqueue leaked atomic, lock or RCU: kworker/2:1[106] [ 13.062137] preempt=0x00000000 lock=0->0 RCU=0->1 workfn=mld_ifc_work [ 13.062266] C ** replaying previous printk message ** [ 13.062266] CPU: 2 UID: 0 PID: 106 Comm: kworker/2:1 Not tainted 6.18.0-dirty #179 PREEMPT_{RT,(full)} [ 13.062353] Hardware name: , BIOS [ 13.062382] Workqueue: mld mld_ifc_work [ 13.062469] Call trace: [ 13.062494] show_stack+0x24/0x40 (C) [ 13.062602] __dump_stack+0x28/0x48 [ 13.062710] dump_stack_lvl+0x7c/0xb0 [ 13.062818] dump_stack+0x18/0x34 [ 13.062926] process_scheduled_works+0x294/0x450 [ 13.063043] worker_thread+0x260/0x3d8 [ 13.063124] kthread+0x1c4/0x228 [ 13.063235] ret_from_fork+0x10/0x20 This happens because smc_special_trylock() disables IRQs even on PREEMPT_RT, but smc_special_unlock() does not restore IRQs on PREEMPT_RT. The reason is that smc_special_unlock() calls spin_unlock_irqrestore(), and rcu_read_unlock_bh() in __dev_queue_xmit() cannot invoke rcu_read_unlock() through __local_bh_enable_ip() when current->softirq_disable_cnt becomes zero. To address this issue, replace smc_special_trylock() with spin_trylock_irqsave(). Join the discussion | GCVE Database | 01/14/2026, 15:16:00 UTC Added: 07/18/2026, 11:30:14 UTC |
Showing 1 to 3 of 3 results