CVE-2025-71132 Details
Description
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().
A vulnerability in the Linux kernel's handling of interrupt request (IRQ) contexts within the SMC91X network driver has been identified. When the driver is compiled with PREEMPT_RT support, a workqueue management issue arises, leading to a 'workqueue leaked atomic, lock or RCU' error. This problem occurs because the custom lock management in the driver improperly handles IRQs under PREEMPT_RT, causing a failure to restore IRQs after they are disabled. As a result, certain operations cannot complete correctly, potentially leading to degraded system performance or stability.
The issue has been addressed by modifying the driver to use a proper IRQ-safe locking mechanism. Users should apply the latest patches available in the Linux kernel stable tree to resolve this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 10, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1c4cb705e733250d13243f6a69b8b5a92e39b9f6 | kernel.org | Patch |
| https://git.kernel.org/stable/c/36561b86cb2501647662cfaf91286dd6973804a6 | kernel.org | Patch |
| https://git.kernel.org/stable/c/6402078bd9d1ed46e79465e1faaa42e3458f8a33 | kernel.org | Patch |
| https://git.kernel.org/stable/c/9d222141b00156509d67d80c771fbefa92c43ace | kernel.org | Patch |
| https://git.kernel.org/stable/c/b6018d5c1a8f09d5efe4d6961d7ee45fdf3a7ce3 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ef277ae121b3249c99994652210a326b52d527b0 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
| CWE-667 | Improper Locking | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.15.1, < 5.15.198 >= 5.16, < 6.1.160 >= 6.2, < 6.6.120 >= 6.7, < 6.12.64 >= 6.13, < 6.18.4 5.15 - 6.19 rc1 6.19 rc2 6.19 rc3 6.19 rc4 6.19 rc5 6.19 rc6 6.19 rc7 6.19 rc8 |
CPE
Remediation
| |
Change History
8 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 19, 2026 | CVE Modified | kernel.org |
| Oct 19, 2026 | CVE Modified | CISA-ADP |
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Mar 25, 2026 | Initial Analysis | [email protected] |
| Jan 19, 2026 | CVE Modified | kernel.org |
| Jan 14, 2026 | New CVE Received | kernel.org |