HighCVE-2025-71132

    Linux Kernel: security vulnerability (CVE-2025-71132)

    Published Last modified Sources: Ubuntu, SUSE, Red Hat, BSI, Debian LTS, Debian, CVE.org, Msrc Update Guide, EUVD

    Share

    What is affected, what to do

    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.

    Update Linux Kernel to version 5.15.198, Linux Kernel to version 6.1.160, Linux Kernel to version 6.6.120.

    Affected
    • Linux Kernel lt 5.15..5.15.198
    • Linux Kernel lt 5.16..6.1.160
    • Linux Kernel lt 6.2..6.6.120
    • Linux Kernel lt 6.7..6.12.64
    • Linux Kernel lt 6.13..6.18.4
    Fixed in
    • Linux Kernel 5.15.198
    • Linux Kernel 6.1.160
    • Linux Kernel 6.6.120
    • Linux Kernel 6.12.64
    • Linux Kernel 6.18.4
    • Linux Kernel 6.19

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.5

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    7.5

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: Ubuntu, SUSE, Red Hat, BSI, Debian LTS, Debian, CVE.org, Msrc Update Guide, EUVD

    0.2 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 12.5

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    52.06 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.2 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    12.5
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 10 June 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-667

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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().

    Source: Ubuntu Security Notices, suse_csaf, redhat_csaf, BSI WID Portal, BSI CSAF, Debian LTS Advisories, Debian Security Advisories, cvelistv5, NVD (NIST), Microsoft Security Update Guide, CVE.org (MITRE), ENISA EUVD

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    LinuxLinux
    • 5.15 – < 5.15.198
    • 5.16 – < 6.1.160
    • —
    • 6.13 – < 6.18.4
    • 6.2 – < 6.6.120
    • 6.7 – < 6.12.64
    • 5.15.198
    • 6.1.160
    • 6.19
    • 6.18.4
    • 6.6.120
    • 6.12.64
    IBMQRadar SIEM
    • < 7.6.0.3
    • <7.5.0 UP16 IF01
    • 7.6.0.3
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianlinuxbookworm
    Linuxdebianlinuxtrixie
    Linuxdebianlinux-6.1bullseye
    Linuxlinuxlinux_kernel5.15
    Linuxlinuxlinux_kernel6.19
    Linuxlinuxlinux_kernel—

    Weakness classes (CWE)

    • CWE-667Improper Locking

      Class

      The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

      Entry at MITRE CWE-667

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedLinux

      Show 18 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://git.kernel.org/stable/c/1c4cb705e733250d13243f6a69b8b5a92e39b9f6
      Referenceadded
      —
      https://git.kernel.org/stable/c/36561b86cb2501647662cfaf91286dd6973804a6
      Referenceadded
      —
      https://git.kernel.org/stable/c/6402078bd9d1ed46e79465e1faaa42e3458f8a33
      Referenceadded
      —
      https://git.kernel.org/stable/c/9d222141b00156509d67d80c771fbefa92c43ace
      Referenceadded
      —
      https://git.kernel.org/stable/c/b6018d5c1a8f09d5efe4d6961d7ee45fdf3a7ce3
      Referenceadded
      —
      https://git.kernel.org/stable/c/ef277ae121b3249c99994652210a326b52d527b0
      Referenceremoved
      https://git.kernel.org/stable/c/1c4cb705e733250d13243f6a69b8b5a92e39b9f6
      —
      Referenceremoved
      https://git.kernel.org/stable/c/36561b86cb2501647662cfaf91286dd6973804a6
      —
      Referenceremoved
      https://git.kernel.org/stable/c/6402078bd9d1ed46e79465e1faaa42e3458f8a33
      —
      Referenceremoved
      https://git.kernel.org/stable/c/9d222141b00156509d67d80c771fbefa92c43ace
      —
      Referenceremoved
      https://git.kernel.org/stable/c/b6018d5c1a8f09d5efe4d6961d7ee45fdf3a7ce3
      —
      Referenceremoved
      https://git.kernel.org/stable/c/ef277ae121b3249c99994652210a326b52d527b0
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/1c4cb705e733250d13243f6a69b8b5a92e39b9f6 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/36561b86cb2501647662cfaf91286dd6973804a6 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/6402078bd9d1ed46e79465e1faaa42e3458f8a33 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/9d222141b00156509d67d80c771fbefa92c43ace Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/b6018d5c1a8f09d5efe4d6961d7ee45fdf3a7ce3 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/ef277ae121b3249c99994652210a326b52d527b0 Types: Patch
      —

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    2. Record modifiedCISA ADP

      Weakness type: CWE-667

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Weakness type (CWE)added
      —
      CWE-667

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. Record modifiedLinux

      CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2025-71132
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-71132"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-71132.svg?lang=en" alt="CVE-2025-71132 – NEOSEC Intel" height="20"></a>