BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2025-71132High confidence

smc91x: fix broken irq-context in PREEMPT_RT

Linux · Linux

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.27% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.69-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.162-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-71132 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: smc91x: fix broken irq-context in PREEMPT_RT
184 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A locking context bug was found in the Linux kernel's smc91x Ethernet driver on PREEMPT_RT kernels. The smc_special_trylock() function disables IRQs but smc_special_unlock() does not properly restore IRQs on PREEMPT_RT. This mismatch causes RCU read unlock to fail in __dev_queue_xmit(), triggering a "workqueue leaked atomic, lock or RCU" warning.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-2483

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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

What

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

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticated
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-3595IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-0119Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260121Security Bulletin 21 Jan 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 21 Jan 2026, published on 21 January 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1256Multiples vulnérabilités dans les produits IBM

d?id=CVE-2025-59250 Référence CVE CVE-2025-59471 https://www.cve.org/CVERecord?id=CVE-2025-59471 Référence CVE CVE-2025-62718 https://www.cve.org/CVERecord?id=CVE-2025-62718 Référence CVE CVE-2025-64718 https://www.cve.org/CVERecord?id=CVE-2025-64718 Référence CVE CVE-2025-64756 https://www.cve.org/CVERecord?id=CVE-2025-64756 Référence CVE CVE-2025-68157 https://www.cve.org/CVERecord?id=CVE-2025-68157 Référence CVE CVE-2025-68161 https://www.cve.org/CVERecord?id=CVE-2025-68161 Référence CVE CVE-2025-68458 https://www.cve.org/CVERecord?id=CVE-2025-68458 Référence CVE CVE-2025-69873 https://www.cve.org/CVERecord?id=CVE-2025-69873 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71176 https://www.cve.org/CVERecord?id=CVE-2025-71176 Référence CVE CVE-2025-7783 https://www.cve.org/CVERecord?id=CVE-2025-7783 Référence CVE CVE-2026-0540 https://www.cve.org/CVERecord?id=CVE-2026-0540 Référence CVE CVE-2026-0636 https://www.cve.org/CVERecord?id=CVE-2026-0636 Référence CVE CVE-2026-10723 https://www.cve.org/CVERecord?id=CVE-2026-10723 Référence CVE CVE-2026-10805 https://www.cve.org/CVERecord?id=CVE-2026-10805 Référence CVE CVE-2026-11622 https://www.cve.org/CVERecord?id=CVE-2026-11622 Référence CVE CVE-2026-11721 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1118Multiples vulnérabilités dans le noyau Linux de Red Hat

rata/RHSA-2026:63189 Bulletin de sécurité Red Hat RHSA-2026:63537 du 04 septembre 2026 https://access.redhat.com/errata/RHSA-2026:63537 Bulletin de sécurité Red Hat RHSA-2026:63539 du 04 septembre 2026 https://access.redhat.com/errata/RHSA-2026:63539 Référence CVE CVE-2023-52924 https://www.cve.org/CVERecord?id=CVE-2023-52924 Référence CVE CVE-2024-46744 https://www.cve.org/CVERecord?id=CVE-2024-46744 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2025-21834 https://www.cve.org/CVERecord?id=CVE-2025-21834 Référence CVE CVE-2025-68211 https://www.cve.org/CVERecord?id=CVE-2025-68211 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2026-23003 https://www.cve.org/CVERecord?id=CVE-2026-23003 Référence CVE CVE-2026-43023 https://www.cve.org/CVERecord?id=CVE-2026-43023 Référence CVE CVE-2026-43114 https://www.cve.org/CVERecord?id=CVE-2026-43114 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43454 https://www.cve.org/CVERecord?id=CVE-2026-43454 Référence CVE CVE-2026-45970 https://www.cve.org/CVERecord?id=CVE-2026-45970 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0787Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-71120 Référence CVE CVE-2025-71121 https://www.cve.org/CVERecord?id=CVE-2025-71121 Référence CVE CVE-2025-71122 https://www.cve.org/CVERecord?id=CVE-2025-71122 Référence CVE CVE-2025-71123 https://www.cve.org/CVERecord?id=CVE-2025-71123 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71126 https://www.cve.org/CVERecord?id=CVE-2025-71126 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71130 https://www.cve.org/CVERecord?id=CVE-2025-71130 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71135 https://www.cve.org/CVERecord?id=CVE-2025-71135 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71138 https://www.cve.org/CVERecord?id=CVE-2025-71138 Référence CVE CVE-2025-71140 https://www.cve.org/CVERecord?id=CVE-2025-71140 Référence CVE CVE-2025-71141 https://www.cve.org/CVERecord?id=CVE-2025-71141 Référence CVE CVE-2025-71143 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0602Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-71120 Référence CVE CVE-2025-71121 https://www.cve.org/CVERecord?id=CVE-2025-71121 Référence CVE CVE-2025-71122 https://www.cve.org/CVERecord?id=CVE-2025-71122 Référence CVE CVE-2025-71123 https://www.cve.org/CVERecord?id=CVE-2025-71123 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71126 https://www.cve.org/CVERecord?id=CVE-2025-71126 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71130 https://www.cve.org/CVERecord?id=CVE-2025-71130 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71135 https://www.cve.org/CVERecord?id=CVE-2025-71135 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71138 https://www.cve.org/CVERecord?id=CVE-2025-71138 Référence CVE CVE-2025-71140 https://www.cve.org/CVERecord?id=CVE-2025-71140 Référence CVE CVE-2025-71141 https://www.cve.org/CVERecord?id=CVE-2025-71141 Référence CVE CVE-2025-71143 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0545Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-71120 Référence CVE CVE-2025-71121 https://www.cve.org/CVERecord?id=CVE-2025-71121 Référence CVE CVE-2025-71122 https://www.cve.org/CVERecord?id=CVE-2025-71122 Référence CVE CVE-2025-71123 https://www.cve.org/CVERecord?id=CVE-2025-71123 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71126 https://www.cve.org/CVERecord?id=CVE-2025-71126 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71130 https://www.cve.org/CVERecord?id=CVE-2025-71130 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71135 https://www.cve.org/CVERecord?id=CVE-2025-71135 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71138 https://www.cve.org/CVERecord?id=CVE-2025-71138 Référence CVE CVE-2025-71140 https://www.cve.org/CVERecord?id=CVE-2025-71140 Référence CVE CVE-2025-71141 https://www.cve.org/CVERecord?id=CVE-2025-71141 Référence CVE CVE-2025-71143 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0522Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-71120 Référence CVE CVE-2025-71121 https://www.cve.org/CVERecord?id=CVE-2025-71121 Référence CVE CVE-2025-71122 https://www.cve.org/CVERecord?id=CVE-2025-71122 Référence CVE CVE-2025-71123 https://www.cve.org/CVERecord?id=CVE-2025-71123 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71126 https://www.cve.org/CVERecord?id=CVE-2025-71126 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71130 https://www.cve.org/CVERecord?id=CVE-2025-71130 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71135 https://www.cve.org/CVERecord?id=CVE-2025-71135 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71138 https://www.cve.org/CVERecord?id=CVE-2025-71138 Référence CVE CVE-2025-71140 https://www.cve.org/CVERecord?id=CVE-2025-71140 Référence CVE CVE-2025-71141 https://www.cve.org/CVERecord?id=CVE-2025-71141 Référence CVE CVE-2025-71143 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0495Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-71121 Référence CVE CVE-2025-71122 https://www.cve.org/CVERecord?id=CVE-2025-71122 Référence CVE CVE-2025-71123 https://www.cve.org/CVERecord?id=CVE-2025-71123 Référence CVE CVE-2025-71124 https://www.cve.org/CVERecord?id=CVE-2025-71124 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71126 https://www.cve.org/CVERecord?id=CVE-2025-71126 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71130 https://www.cve.org/CVERecord?id=CVE-2025-71130 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71135 https://www.cve.org/CVERecord?id=CVE-2025-71135 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71138 https://www.cve.org/CVERecord?id=CVE-2025-71138 Référence CVE CVE-2025-71140 https://www.cve.org/CVERecord?id=CVE-2025-71140 Référence CVE CVE-2025-71141 https://www.cve.org/CVERecord?id=CVE-2025-71141 Référence CVE CVE-2025-71143 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0453Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-71121 Référence CVE CVE-2025-71122 https://www.cve.org/CVERecord?id=CVE-2025-71122 Référence CVE CVE-2025-71123 https://www.cve.org/CVERecord?id=CVE-2025-71123 Référence CVE CVE-2025-71124 https://www.cve.org/CVERecord?id=CVE-2025-71124 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71126 https://www.cve.org/CVERecord?id=CVE-2025-71126 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71130 https://www.cve.org/CVERecord?id=CVE-2025-71130 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71135 https://www.cve.org/CVERecord?id=CVE-2025-71135 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71138 https://www.cve.org/CVERecord?id=CVE-2025-71138 Référence CVE CVE-2025-71140 https://www.cve.org/CVERecord?id=CVE-2025-71140 Référence CVE CVE-2025-71141 https://www.cve.org/CVERecord?id=CVE-2025-71141 Référence CVE CVE-2025-71143 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0421Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-71114 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=CVE-2025-71116 Référence CVE CVE-2025-71118 https://www.cve.org/CVERecord?id=CVE-2025-71118 Référence CVE CVE-2025-71120 https://www.cve.org/CVERecord?id=CVE-2025-71120 Référence CVE CVE-2025-71121 https://www.cve.org/CVERecord?id=CVE-2025-71121 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71128 https://www.cve.org/CVERecord?id=CVE-2025-71128 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2025-71163 https://www.cve.org/CVERecord?id=CVE-2025-71163 Référence CVE CVE-2025-71180 https://www.cve.org/CVERecord?id=CVE-2025-71180 Référence CVE CVE-2025-71182 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0397Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-71114 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=CVE-2025-71116 Référence CVE CVE-2025-71118 https://www.cve.org/CVERecord?id=CVE-2025-71118 Référence CVE CVE-2025-71120 https://www.cve.org/CVERecord?id=CVE-2025-71120 Référence CVE CVE-2025-71121 https://www.cve.org/CVERecord?id=CVE-2025-71121 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71128 https://www.cve.org/CVERecord?id=CVE-2025-71128 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2025-71180 https://www.cve.org/CVERecord?id=CVE-2025-71180 Référence CVE CVE-2025-71182 https://www.cve.org/CVERecord?id=CVE-2025-71182 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0371Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-71114 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=CVE-2025-71116 Référence CVE CVE-2025-71118 https://www.cve.org/CVERecord?id=CVE-2025-71118 Référence CVE CVE-2025-71120 https://www.cve.org/CVERecord?id=CVE-2025-71120 Référence CVE CVE-2025-71121 https://www.cve.org/CVERecord?id=CVE-2025-71121 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71128 https://www.cve.org/CVERecord?id=CVE-2025-71128 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2025-71180 https://www.cve.org/CVERecord?id=CVE-2025-71180 Référence CVE CVE-2025-71182 https://www.cve.org/CVERecord?id=CVE-2025-71182 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0369Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-71116 Référence CVE CVE-2025-71118 https://www.cve.org/CVERecord?id=CVE-2025-71118 Référence CVE CVE-2025-71119 https://www.cve.org/CVERecord?id=CVE-2025-71119 Référence CVE CVE-2025-71120 https://www.cve.org/CVERecord?id=CVE-2025-71120 Référence CVE CVE-2025-71123 https://www.cve.org/CVERecord?id=CVE-2025-71123 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71126 https://www.cve.org/CVERecord?id=CVE-2025-71126 Référence CVE CVE-2025-71130 https://www.cve.org/CVERecord?id=CVE-2025-71130 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71135 https://www.cve.org/CVERecord?id=CVE-2025-71135 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71138 https://www.cve.org/CVERecord?id=CVE-2025-71138 Référence CVE CVE-2025-71145 https://www.cve.org/CVERecord?id=CVE-2025-71145 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71148 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0331Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-71114 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=CVE-2025-71116 Référence CVE CVE-2025-71118 https://www.cve.org/CVERecord?id=CVE-2025-71118 Référence CVE CVE-2025-71120 https://www.cve.org/CVERecord?id=CVE-2025-71120 Référence CVE CVE-2025-71121 https://www.cve.org/CVERecord?id=CVE-2025-71121 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71128 https://www.cve.org/CVERecord?id=CVE-2025-71128 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2025-71180 https://www.cve.org/CVERecord?id=CVE-2025-71180 Référence CVE CVE-2025-71182 https://www.cve.org/CVERecord?id=CVE-2025-71182 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-71114 Référence CVE CVE-2025-71115 https://www.cve.org/CVERecord?id=CVE-2025-71115 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=CVE-2025-71116 Référence CVE CVE-2025-71118 https://www.cve.org/CVERecord?id=CVE-2025-71118 Référence CVE CVE-2025-71120 https://www.cve.org/CVERecord?id=CVE-2025-71120 Référence CVE CVE-2025-71121 https://www.cve.org/CVERecord?id=CVE-2025-71121 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71150 https://www.cve.org/CVERecord?id=CVE-2025-71150 Référence CVE CVE-2025-71152 https://www.cve.org/CVERecord?id=CVE-2025-71152 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2025-71158 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-71114 Référence CVE CVE-2025-71115 https://www.cve.org/CVERecord?id=CVE-2025-71115 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=CVE-2025-71116 Référence CVE CVE-2025-71118 https://www.cve.org/CVERecord?id=CVE-2025-71118 Référence CVE CVE-2025-71120 https://www.cve.org/CVERecord?id=CVE-2025-71120 Référence CVE CVE-2025-71121 https://www.cve.org/CVERecord?id=CVE-2025-71121 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71150 https://www.cve.org/CVERecord?id=CVE-2025-71150 Référence CVE CVE-2025-71152 https://www.cve.org/CVERecord?id=CVE-2025-71152 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2025-71158 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0247Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-71114 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=CVE-2025-71116 Référence CVE CVE-2025-71118 https://www.cve.org/CVERecord?id=CVE-2025-71118 Référence CVE CVE-2025-71119 https://www.cve.org/CVERecord?id=CVE-2025-71119 Référence CVE CVE-2025-71120 https://www.cve.org/CVERecord?id=CVE-2025-71120 Référence CVE CVE-2025-71123 https://www.cve.org/CVERecord?id=CVE-2025-71123 Référence CVE CVE-2025-71126 https://www.cve.org/CVERecord?id=CVE-2025-71126 Référence CVE CVE-2025-71130 https://www.cve.org/CVERecord?id=CVE-2025-71130 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71135 https://www.cve.org/CVERecord?id=CVE-2025-71135 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71138 https://www.cve.org/CVERecord?id=CVE-2025-71138 Référence CVE CVE-2025-71141 https://www.cve.org/CVERecord?id=CVE-2025-71141 Référence CVE CVE-2025-71142 https://www.cve.org/CVERecord?id=CVE-2025-71142 Référence CVE CVE-2025-71143 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0225Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-71112 Référence CVE CVE-2025-71114 https://www.cve.org/CVERecord?id=CVE-2025-71114 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=CVE-2025-71116 Référence CVE CVE-2025-71118 https://www.cve.org/CVERecord?id=CVE-2025-71118 Référence CVE CVE-2025-71119 https://www.cve.org/CVERecord?id=CVE-2025-71119 Référence CVE CVE-2025-71120 https://www.cve.org/CVERecord?id=CVE-2025-71120 Référence CVE CVE-2025-71123 https://www.cve.org/CVERecord?id=CVE-2025-71123 Référence CVE CVE-2025-71130 https://www.cve.org/CVERecord?id=CVE-2025-71130 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71135 https://www.cve.org/CVERecord?id=CVE-2025-71135 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71138 https://www.cve.org/CVERecord?id=CVE-2025-71138 Référence CVE CVE-2025-71141 https://www.cve.org/CVERecord?id=CVE-2025-71141 Référence CVE CVE-2025-71142 https://www.cve.org/CVERecord?id=CVE-2025-71142 Référence CVE CVE-2025-71143 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0170Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-71112 Référence CVE CVE-2025-71114 https://www.cve.org/CVERecord?id=CVE-2025-71114 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=CVE-2025-71116 Référence CVE CVE-2025-71118 https://www.cve.org/CVERecord?id=CVE-2025-71118 Référence CVE CVE-2025-71119 https://www.cve.org/CVERecord?id=CVE-2025-71119 Référence CVE CVE-2025-71120 https://www.cve.org/CVERecord?id=CVE-2025-71120 Référence CVE CVE-2025-71123 https://www.cve.org/CVERecord?id=CVE-2025-71123 Référence CVE CVE-2025-71130 https://www.cve.org/CVERecord?id=CVE-2025-71130 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71135 https://www.cve.org/CVERecord?id=CVE-2025-71135 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71138 https://www.cve.org/CVERecord?id=CVE-2025-71138 Référence CVE CVE-2025-71141 https://www.cve.org/CVERecord?id=CVE-2025-71141 Référence CVE CVE-2025-71142 https://www.cve.org/CVERecord?id=CVE-2025-71142 Référence CVE CVE-2025-71143 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0167Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2025-71119 Référence CVE CVE-2025-71120 https://www.cve.org/CVERecord?id=CVE-2025-71120 Référence CVE CVE-2025-71121 https://www.cve.org/CVERecord?id=CVE-2025-71121 Référence CVE CVE-2025-71123 https://www.cve.org/CVERecord?id=CVE-2025-71123 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71126 https://www.cve.org/CVERecord?id=CVE-2025-71126 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71130 https://www.cve.org/CVERecord?id=CVE-2025-71130 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71149 https://www.cve.org/CVERecord?id=CVE-2025-71149 Référence CVE CVE-2025-71150 https://www.cve.org/CVERecord?id=CVE-2025-71150 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2025-71162 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0166Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2025-71121 Référence CVE CVE-2025-71122 https://www.cve.org/CVERecord?id=CVE-2025-71122 Référence CVE CVE-2025-71123 https://www.cve.org/CVERecord?id=CVE-2025-71123 Référence CVE CVE-2025-71125 https://www.cve.org/CVERecord?id=CVE-2025-71125 Référence CVE CVE-2025-71126 https://www.cve.org/CVERecord?id=CVE-2025-71126 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71129 https://www.cve.org/CVERecord?id=CVE-2025-71129 Référence CVE CVE-2025-71130 https://www.cve.org/CVERecord?id=CVE-2025-71130 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71134 https://www.cve.org/CVERecord?id=CVE-2025-71134 Référence CVE CVE-2025-71135 https://www.cve.org/CVERecord?id=CVE-2025-71135 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71138 https://www.cve.org/CVERecord?id=CVE-2025-71138 Référence CVE CVE-2025-71140 https://www.cve.org/CVERecord?id=CVE-2025-71140 Référence CVE CVE-2025-71143 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-008647LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。smc91xはPREEMPT_RT環境下でIRQコンテキストの破損を引き起こしていました。smc91x.cがPREEMPT_RTでビルドされると、FVP_RevC環境でスプラッシュ(クラッシュ)が発生します。[ 13.055000] smc91x LNRO0003:00 eth0: link up, 10Mbps, half-duplex, lpa 0x0000[ 13.062137] BUG: workqueueがatomic、lock、またはRCUをリークしました: kworker/2:1[106][ 13.062137] preempt=0x00000000 lock=0-0 RCU=0-1 workfn=mld_ifc_work[ 13.062266] ** 以前のprintkメッセージを再生中 **[ 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] コールトレース:[ 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これは、smc_special_trylock()がPREEMPT_RT環境下でもIRQを無効化する一方で、smc_special_unlock()はPREEMPT_RT環境下でIRQを復元しなかったために発生しました。原因は、smc_special_unlock()がspin_unlock_irqrestore()を呼び出すことにありますが、__dev_queue_xmit()内のrcu_read_unlock_bh()がcurrent-softirq_disable_cntがゼロになるときに__local_bh_enable_ip()を経由してrcu_read_unlock()を呼び出せなかったためです。この問題に対処するために、smc_special_trylock()をspin_trylock_irqsave()に置き換えました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 14 Jan 2026 · Last source change 5 Aug 2026, 12:12 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-2483
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2025-71132 to remediation: access.redhat.com/CVE-2025-71132.
    Before
    remediation: access.redhat.com/CVE-2025-71132
    After
    remediation: access.redhat.com/CVE-2025-71132
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel as a component of Red Hat Enterprise Linux 10; kernel-64k as a component of Red Hat Enterprise Linux 10; kernel-64k-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-64k-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 202 more
    After
    kernel as a component of Red Hat Enterprise Linux 10; kernel-64k as a component of Red Hat Enterprise Linux 10; kernel-64k-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-64k-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 154 more · Fixed: bpftool-0:4.18.0-553.159.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.159.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.159.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.159.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.159.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.159.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.159.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.159.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.159.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.159.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.159.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.159.1.el8_10.src as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.159.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-abi-stablelists-0:4.18.0-553.159.1.el8_10.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.159.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.159.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.159.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.159.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.159.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.159.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.159.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.159.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.159.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.159.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.159.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.159.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.159.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.159.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.159.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.159.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); and 120 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-71132 · cve.blacktree.nl