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

ipv6: fix a BUG in rt6_get_pcpu_route() under 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 110 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.30% 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 110 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 · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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-71080 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT
90 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 race condition vulnerability was found in the Linux kernel's IPv6 routing subsystem on PREEMPT_RT kernels. When rt6_get_pcpu_route() returns NULL and the task is preempted, another task can install a per-CPU route entry. When the original task resumes and attempts cmpxchg() in rt6_make_pcpu_route(), the operation fails because the pointer is no longer NULL, triggering a BUG_ON crash.
Remediation
Fix deferred
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-2250

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 110 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: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT On PREEMPT_RT kernels, after rt6_get_pcpu_route() returns NULL, the current task can be preempted. Another task running on the same CPU may then execute rt6_make_pcpu_route() and successfully install a pcpu_rt entry. When the first task resumes execution, its cmpxchg() in rt6_make_pcpu_route() will fail because rt6i_pcpu is no longer NULL, triggering the BUG_ON(prev). It's easy to reproduce it by adding mdelay() after rt6_get_pcpu_route(). Using preempt_disable/enable is not appropriate here because ip6_rt_pcpu_alloc() may sleep. Fix this by handling the cmpxchg() failure gracefully on PREEMPT_RT: free our allocation and return the existing pcpu_rt installed by another task. The BUG_ON is replaced by WARN_ON_ONCE for non-PREEMPT_RT kernels where such races should not occur.

What

In the Linux kernel, the following vulnerability has been resolved: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT On PREEMPT_RT kernels, after rt6_get_pcpu_route() returns NULL, the current task can be preempted. Another task running on the same CPU may then execute rt6_make_pcpu_route() and successfully install a pcpu_rt entry. When the first task resumes execution, its cmpxchg() in rt6_make_pcpu_route() will fail because rt6i_pcpu is no longer NULL, triggering the BUG_ON(prev). It's easy to reproduce it by adding mdelay() after rt6_get_pcpu_route(). Using preempt_disable/enable is not appropriate here because ip6_rt_pcpu_alloc() may sleep. Fix this by handling the cmpxchg() failure gracefully on PREEMPT_RT: free our allocation and return the existing pcpu_rt installed by another task. The BUG_ON is replaced by WARN_ON_ONCE for non-PREEMPT_RT kernels where such races should not occur.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT On PREEMPT_RT kernels, after rt6_get_pcpu_route() returns NULL, the current task can be preempted. Another task running on the same CPU may then execute rt6_make_pcpu_route() and successfully install a pcpu_rt entry. When the first task resumes execution, its cmpxchg() in rt6_make_pcpu_route() will fail because rt6i_pcpu is no longer NULL, triggering the BUG_ON(prev). It's easy to reproduce it by adding mdelay() after rt6_get_pcpu_route(). Using preempt_disable/enable is not appropriate here because ip6_rt_pcpu_alloc() may sleep. Fix this by handling the cmpxchg() failure gracefully on PREEMPT_RT: free our allocation and return the existing pcpu_rt installed by another task. The BUG_ON is replaced by WARN_ON_ONCE for non-PREEMPT_RT kernels where such races should not occur.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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 → Reachable Assertion → 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: a standard category for the underlying weakness.
CWE-617 ↗

CWE-617: Reachable Assertion. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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.
NetworkUnauthenticatedCWE-617
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-0086Linux 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-20260114Security Bulletin 14 Jan 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 14 Jan 2026, published on 14 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-0602Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-71067 Référence CVE CVE-2025-71068 https://www.cve.org/CVERecord?id=CVE-2025-71068 Référence CVE CVE-2025-71069 https://www.cve.org/CVERecord?id=CVE-2025-71069 Référence CVE CVE-2025-71071 https://www.cve.org/CVERecord?id=CVE-2025-71071 Référence CVE CVE-2025-71072 https://www.cve.org/CVERecord?id=CVE-2025-71072 Référence CVE CVE-2025-71075 https://www.cve.org/CVERecord?id=CVE-2025-71075 Référence CVE CVE-2025-71077 https://www.cve.org/CVERecord?id=CVE-2025-71077 Référence CVE CVE-2025-71078 https://www.cve.org/CVERecord?id=CVE-2025-71078 Référence CVE CVE-2025-71079 https://www.cve.org/CVERecord?id=CVE-2025-71079 Référence CVE CVE-2025-71080 https://www.cve.org/CVERecord?id=CVE-2025-71080 Référence CVE CVE-2025-71081 https://www.cve.org/CVERecord?id=CVE-2025-71081 Référence CVE CVE-2025-71082 https://www.cve.org/CVERecord?id=CVE-2025-71082 Référence CVE CVE-2025-71083 https://www.cve.org/CVERecord?id=CVE-2025-71083 Référence CVE CVE-2025-71084 https://www.cve.org/CVERecord?id=CVE-2025-71084 Référence CVE CVE-2025-71085 https://www.cve.org/CVERecord?id=CVE-2025-71085 Référence CVE CVE-2025-71086 https://www.cve.org/CVERecord?id=CVE-2025-71086 Référence CVE CVE-2025-71087 https://www.cve.org/CVERecord?id=CVE-2025-71087 Référence CVE CVE-2025-71088 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-71070 Référence CVE CVE-2025-71071 https://www.cve.org/CVERecord?id=CVE-2025-71071 Référence CVE CVE-2025-71072 https://www.cve.org/CVERecord?id=CVE-2025-71072 Référence CVE CVE-2025-71073 https://www.cve.org/CVERecord?id=CVE-2025-71073 Référence CVE CVE-2025-71075 https://www.cve.org/CVERecord?id=CVE-2025-71075 Référence CVE CVE-2025-71076 https://www.cve.org/CVERecord?id=CVE-2025-71076 Référence CVE CVE-2025-71077 https://www.cve.org/CVERecord?id=CVE-2025-71077 Référence CVE CVE-2025-71078 https://www.cve.org/CVERecord?id=CVE-2025-71078 Référence CVE CVE-2025-71079 https://www.cve.org/CVERecord?id=CVE-2025-71079 Référence CVE CVE-2025-71080 https://www.cve.org/CVERecord?id=CVE-2025-71080 Référence CVE CVE-2025-71081 https://www.cve.org/CVERecord?id=CVE-2025-71081 Référence CVE CVE-2025-71082 https://www.cve.org/CVERecord?id=CVE-2025-71082 Référence CVE CVE-2025-71083 https://www.cve.org/CVERecord?id=CVE-2025-71083 Référence CVE CVE-2025-71084 https://www.cve.org/CVERecord?id=CVE-2025-71084 Référence CVE CVE-2025-71085 https://www.cve.org/CVERecord?id=CVE-2025-71085 Référence CVE CVE-2025-71086 https://www.cve.org/CVERecord?id=CVE-2025-71086 Référence CVE CVE-2025-71087 https://www.cve.org/CVERecord?id=CVE-2025-71087 Référence CVE CVE-2025-71088 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-71070 Référence CVE CVE-2025-71071 https://www.cve.org/CVERecord?id=CVE-2025-71071 Référence CVE CVE-2025-71072 https://www.cve.org/CVERecord?id=CVE-2025-71072 Référence CVE CVE-2025-71073 https://www.cve.org/CVERecord?id=CVE-2025-71073 Référence CVE CVE-2025-71075 https://www.cve.org/CVERecord?id=CVE-2025-71075 Référence CVE CVE-2025-71076 https://www.cve.org/CVERecord?id=CVE-2025-71076 Référence CVE CVE-2025-71077 https://www.cve.org/CVERecord?id=CVE-2025-71077 Référence CVE CVE-2025-71078 https://www.cve.org/CVERecord?id=CVE-2025-71078 Référence CVE CVE-2025-71079 https://www.cve.org/CVERecord?id=CVE-2025-71079 Référence CVE CVE-2025-71080 https://www.cve.org/CVERecord?id=CVE-2025-71080 Référence CVE CVE-2025-71081 https://www.cve.org/CVERecord?id=CVE-2025-71081 Référence CVE CVE-2025-71082 https://www.cve.org/CVERecord?id=CVE-2025-71082 Référence CVE CVE-2025-71083 https://www.cve.org/CVERecord?id=CVE-2025-71083 Référence CVE CVE-2025-71084 https://www.cve.org/CVERecord?id=CVE-2025-71084 Référence CVE CVE-2025-71085 https://www.cve.org/CVERecord?id=CVE-2025-71085 Référence CVE CVE-2025-71086 https://www.cve.org/CVERecord?id=CVE-2025-71086 Référence CVE CVE-2025-71087 https://www.cve.org/CVERecord?id=CVE-2025-71087 Référence CVE CVE-2025-71088 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-68820 Référence CVE CVE-2025-71064 https://www.cve.org/CVERecord?id=CVE-2025-71064 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-2025-71066 Référence CVE CVE-2025-71068 https://www.cve.org/CVERecord?id=CVE-2025-71068 Référence CVE CVE-2025-71069 https://www.cve.org/CVERecord?id=CVE-2025-71069 Référence CVE CVE-2025-71075 https://www.cve.org/CVERecord?id=CVE-2025-71075 Référence CVE CVE-2025-71077 https://www.cve.org/CVERecord?id=CVE-2025-71077 Référence CVE CVE-2025-71078 https://www.cve.org/CVERecord?id=CVE-2025-71078 Référence CVE CVE-2025-71079 https://www.cve.org/CVERecord?id=CVE-2025-71079 Référence CVE CVE-2025-71080 https://www.cve.org/CVERecord?id=CVE-2025-71080 Référence CVE CVE-2025-71081 https://www.cve.org/CVERecord?id=CVE-2025-71081 Référence CVE CVE-2025-71082 https://www.cve.org/CVERecord?id=CVE-2025-71082 Référence CVE CVE-2025-71083 https://www.cve.org/CVERecord?id=CVE-2025-71083 Référence CVE CVE-2025-71084 https://www.cve.org/CVERecord?id=CVE-2025-71084 Référence CVE CVE-2025-71085 https://www.cve.org/CVERecord?id=CVE-2025-71085 Référence CVE CVE-2025-71086 https://www.cve.org/CVERecord?id=CVE-2025-71086 Référence CVE CVE-2025-71087 https://www.cve.org/CVERecord?id=CVE-2025-71087 Référence CVE CVE-2025-71091 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-68821 Référence CVE CVE-2025-68822 https://www.cve.org/CVERecord?id=CVE-2025-68822 Référence CVE CVE-2025-71064 https://www.cve.org/CVERecord?id=CVE-2025-71064 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-2025-71066 Référence CVE CVE-2025-71073 https://www.cve.org/CVERecord?id=CVE-2025-71073 Référence CVE CVE-2025-71076 https://www.cve.org/CVERecord?id=CVE-2025-71076 Référence CVE CVE-2025-71077 https://www.cve.org/CVERecord?id=CVE-2025-71077 Référence CVE CVE-2025-71078 https://www.cve.org/CVERecord?id=CVE-2025-71078 Référence CVE CVE-2025-71079 https://www.cve.org/CVERecord?id=CVE-2025-71079 Référence CVE CVE-2025-71080 https://www.cve.org/CVERecord?id=CVE-2025-71080 Référence CVE CVE-2025-71081 https://www.cve.org/CVERecord?id=CVE-2025-71081 Référence CVE CVE-2025-71082 https://www.cve.org/CVERecord?id=CVE-2025-71082 Référence CVE CVE-2025-71083 https://www.cve.org/CVERecord?id=CVE-2025-71083 Référence CVE CVE-2025-71084 https://www.cve.org/CVERecord?id=CVE-2025-71084 Référence CVE CVE-2025-71085 https://www.cve.org/CVERecord?id=CVE-2025-71085 Référence CVE CVE-2025-71086 https://www.cve.org/CVERecord?id=CVE-2025-71086 Référence CVE CVE-2025-71087 https://www.cve.org/CVERecord?id=CVE-2025-71087 Référence CVE CVE-2025-71088 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-68816 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=CVE-2025-68819 Référence CVE CVE-2025-68820 https://www.cve.org/CVERecord?id=CVE-2025-68820 Référence CVE CVE-2025-71064 https://www.cve.org/CVERecord?id=CVE-2025-71064 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-2025-71066 Référence CVE CVE-2025-71076 https://www.cve.org/CVERecord?id=CVE-2025-71076 Référence CVE CVE-2025-71077 https://www.cve.org/CVERecord?id=CVE-2025-71077 Référence CVE CVE-2025-71078 https://www.cve.org/CVERecord?id=CVE-2025-71078 Référence CVE CVE-2025-71079 https://www.cve.org/CVERecord?id=CVE-2025-71079 Référence CVE CVE-2025-71080 https://www.cve.org/CVERecord?id=CVE-2025-71080 Référence CVE CVE-2025-71081 https://www.cve.org/CVERecord?id=CVE-2025-71081 Référence CVE CVE-2025-71082 https://www.cve.org/CVERecord?id=CVE-2025-71082 Référence CVE CVE-2025-71083 https://www.cve.org/CVERecord?id=CVE-2025-71083 Référence CVE CVE-2025-71084 https://www.cve.org/CVERecord?id=CVE-2025-71084 Référence CVE CVE-2025-71085 https://www.cve.org/CVERecord?id=CVE-2025-71085 Référence CVE CVE-2025-71086 https://www.cve.org/CVERecord?id=CVE-2025-71086 Référence CVE CVE-2025-71087 https://www.cve.org/CVERecord?id=CVE-2025-71087 Référence CVE CVE-2025-71088 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-68816 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=CVE-2025-68819 Référence CVE CVE-2025-68820 https://www.cve.org/CVERecord?id=CVE-2025-68820 Référence CVE CVE-2025-71064 https://www.cve.org/CVERecord?id=CVE-2025-71064 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-2025-71066 Référence CVE CVE-2025-71076 https://www.cve.org/CVERecord?id=CVE-2025-71076 Référence CVE CVE-2025-71077 https://www.cve.org/CVERecord?id=CVE-2025-71077 Référence CVE CVE-2025-71078 https://www.cve.org/CVERecord?id=CVE-2025-71078 Référence CVE CVE-2025-71079 https://www.cve.org/CVERecord?id=CVE-2025-71079 Référence CVE CVE-2025-71080 https://www.cve.org/CVERecord?id=CVE-2025-71080 Référence CVE CVE-2025-71081 https://www.cve.org/CVERecord?id=CVE-2025-71081 Référence CVE CVE-2025-71082 https://www.cve.org/CVERecord?id=CVE-2025-71082 Référence CVE CVE-2025-71083 https://www.cve.org/CVERecord?id=CVE-2025-71083 Référence CVE CVE-2025-71084 https://www.cve.org/CVERecord?id=CVE-2025-71084 Référence CVE CVE-2025-71085 https://www.cve.org/CVERecord?id=CVE-2025-71085 Référence CVE CVE-2025-71086 https://www.cve.org/CVERecord?id=CVE-2025-71086 Référence CVE CVE-2025-71087 https://www.cve.org/CVERecord?id=CVE-2025-71087 Référence CVE CVE-2025-71088 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-71069 Référence CVE CVE-2025-71071 https://www.cve.org/CVERecord?id=CVE-2025-71071 Référence CVE CVE-2025-71072 https://www.cve.org/CVERecord?id=CVE-2025-71072 Référence CVE CVE-2025-71073 https://www.cve.org/CVERecord?id=CVE-2025-71073 Référence CVE CVE-2025-71075 https://www.cve.org/CVERecord?id=CVE-2025-71075 Référence CVE CVE-2025-71076 https://www.cve.org/CVERecord?id=CVE-2025-71076 Référence CVE CVE-2025-71077 https://www.cve.org/CVERecord?id=CVE-2025-71077 Référence CVE CVE-2025-71078 https://www.cve.org/CVERecord?id=CVE-2025-71078 Référence CVE CVE-2025-71079 https://www.cve.org/CVERecord?id=CVE-2025-71079 Référence CVE CVE-2025-71080 https://www.cve.org/CVERecord?id=CVE-2025-71080 Référence CVE CVE-2025-71081 https://www.cve.org/CVERecord?id=CVE-2025-71081 Référence CVE CVE-2025-71082 https://www.cve.org/CVERecord?id=CVE-2025-71082 Référence CVE CVE-2025-71083 https://www.cve.org/CVERecord?id=CVE-2025-71083 Référence CVE CVE-2025-71084 https://www.cve.org/CVERecord?id=CVE-2025-71084 Référence CVE CVE-2025-71085 https://www.cve.org/CVERecord?id=CVE-2025-71085 Référence CVE CVE-2025-71086 https://www.cve.org/CVERecord?id=CVE-2025-71086 Référence CVE CVE-2025-71087 https://www.cve.org/CVERecord?id=CVE-2025-71087 Référence CVE CVE-2025-71088 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-008698LinuxのLinux Kernelにおける到達可能なアサーションに関する脆弱性

Linuxカーネルにおいて、IPv6のPREEMPT_RT環境下でrt6_get_pcpu_route()関数にバグが存在していました。PREEMPT_RTカーネルでは、rt6_get_pcpu_route()がNULLを返した後に現在のタスクがプリエンプトされ、同じCPU上で別のタスクがrt6_make_pcpu_route()を実行してpcpu_rtエントリを正常にインストールすると、その後のcmpxchg()が失敗しBUG_ON(prev)がトリガーされる問題が発生します。preempt_disable/enableの使用は適切ではなく、PREEMPT_RT環境ではcmpxchg()の失敗を穏やかに処理し、メモリ割り当てを解放して既存のpcpu_rtを返すように修正されました。

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
Linux: < 6.12, 6.12.64 ≤ 6.12.*, 6.18.4 ≤ 6.18.*, 6.19 ≤ *
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 13 Jan 2026 · Last source change 5 Aug 2026, 12:11 UTC · CWE-617 · Reachable Assertion

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-2250
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2025-71080 to remediation: access.redhat.com/CVE-2025-71080.
    Before
    remediation: access.redhat.com/CVE-2025-71080
    After
    remediation: access.redhat.com/CVE-2025-71080
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-2250↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
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-71080 · cve.blacktree.nl