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

wifi: mac80211: Discard Beacon frames to non-broadcast address

Linux · Linux

7.1HighCVSS 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.
  • EPSS is 0.22% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • 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 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.162-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.5-1Debian Security Tracker ↗Source updated 5 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.

2 current
CVE-2025-71127 · CSAF 2.0 · revision 16 · interimSUSE Product Security TeamCVE-2025-71127
133 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required to be sent to the broadcast address, see IEEE Std 802.11-2020, 11.1.3.1 ("The Address 1 field of the Beacon .. frame shall be set to the broadcast address"). A unicast Beacon frame might be used as a targeted attack to get one of the associated STAs to do something (e.g., using CSA to move it to another channel). As such, it is better have strict filtering for this on the received side and discard all Beacon frames that are sent to an unexpected address. This is even more important for cases where beacon protection is used. The current implementation in mac80211 is correctly discarding unicast Beacon frames if the Protected Frame bit in the Frame Control field is set to 0. However, if that bit is set to 1, the logic used for checking for configured BIGTK(s) does not actually work. If the driver does not have logic for dropping unicast Beacon frames with Protected Frame bit 1, these frames would be accepted in mac80211 processing as valid Beacon frames even though they are not protected. This would allow beacon protection to be bypassed. While the logic for checking beacon protection could be extended to cover this corner case, a more generic check for discard all Beacon frames based on A1=unicast address covers this without needing additional changes. Address all these issues by dropping received Beacon frames if they are sent to a non-broadcast address.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2025-71127 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: wifi: mac80211: Discard Beacon frames to non-broadcast address
198 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 beacon protection bypass vulnerability was found in the Linux kernel's mac80211 WiFi stack. According to IEEE 802.11-2020, beacon frames must be sent to the broadcast address, but mac80211 incorrectly accepts unicast beacon frames with the Protected Frame bit set to 1. This allows attackers to send targeted unicast beacons that bypass beacon protection (BIGTK verification), potentially forcing associated stations to perform malicious actions like channel switching via CSA.
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-2465

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: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required to be sent to the broadcast address, see IEEE Std 802.11-2020, 11.1.3.1 ("The Address 1 field of the Beacon .. frame shall be set to the broadcast address"). A unicast Beacon frame might be used as a targeted attack to get one of the associated STAs to do something (e.g., using CSA to move it to another channel). As such, it is better have strict filtering for this on the received side and discard all Beacon frames that are sent to an unexpected address. This is even more important for cases where beacon protection is used. The current implementation in mac80211 is correctly discarding unicast Beacon frames if the Protected Frame bit in the Frame Control field is set to 0. However, if that bit is set to 1, the logic used for checking for configured BIGTK(s) does not actually work. If the driver does not have logic for dropping unicast Beacon frames with Protected Frame bit 1, these frames would be accepted in mac80211 processing as valid Beacon frames even though they are not protected. This would allow beacon protection to be bypassed. While the logic for checking beacon protection could be extended to cover this corner case, a more generic check for discard all Beacon frames based on A1=unicast address covers this without needing additional changes. Address all these issues by dropping received Beacon frames if they are sent to a non-broadcast address.

What

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required to be sent to the broadcast address, see IEEE Std 802.11-2020, 11.1.3.1 ("The Address 1 field of the Beacon .. frame shall be set to the broadcast address"). A unicast Beacon frame might be used as a targeted attack to get one of the associated STAs to do something (e.g., using CSA to move it to another channel). As such, it is better have strict filtering for this on the received side and discard all Beacon frames that are sent to an unexpected address. This is even more important for cases where beacon protection is used. The current implementation in mac80211 is correctly discarding unicast Beacon frames if the Protected Frame bit in the Frame Control field is set to 0. However, if that bit is set to 1, the logic used for checking for configured BIGTK(s) does not actually work. If the driver does not have logic for dropping unicast Beacon frames with Protected Frame bit 1, these frames would be accepted in mac80211 processing as valid Beacon frames even though they are not protected. This would allow beacon protection to be bypassed. While the logic for checking beacon protection could be extended to cover this corner case, a more generic check for discard all Beacon frames based on A1=unicast address covers this without needing additional changes. Address all these issues by dropping received Beacon frames if they are sent to a non-broadcast address.

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 an adjacent network 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: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required to be sent to the broadcast address, see IEEE Std 802.11-2020, 11.1.3.1 ("The Address 1 field of the Beacon .. frame shall be set to the broadcast address"). A unicast Beacon frame might be used as a targeted attack to get one of the associated STAs to do something (e.g., using CSA to move it to another channel). As such, it is better have strict filtering for this on the received side and discard all Beacon frames that are sent to an unexpected address. This is even more important for cases where beacon protection is used. The current implementation in mac80211 is correctly discarding unicast Beacon frames if the Protected Frame bit in the Frame Control field is set to 0. However, if that bit is set to 1, the logic used for checking for configured BIGTK(s) does not actually work. If the driver does not have logic for dropping unicast Beacon frames with Protected Frame bit 1, these frames would be accepted in mac80211 processing as valid Beacon frames even though they are not protected. This would allow beacon protection to be bypassed. While the logic for checking beacon protection could be extended to cover this corner case, a more generic check for discard all Beacon frames based on A1=unicast address covers this without needing additional changes. Address all these issues by dropping received Beacon frames if they are sent to a non-broadcast address.

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 an adjacent network 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
an adjacent network → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Adjacent
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:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

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

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close 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.ILowIntegrity impact: A successful attack can cause a limited loss.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.
Unauthenticated
A

Official authority intelligence

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

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-1204Multiples vulnérabilités dans le noyau Linux de Red Hat

rata/RHSA-2026:68131 Bulletin de sécurité Red Hat RHSA-2026:68507 du 17 septembre 2026 https://access.redhat.com/errata/RHSA-2026:68507 Bulletin de sécurité Red Hat RHSA-2026:68532 du 17 septembre 2026 https://access.redhat.com/errata/RHSA-2026:68532 Référence CVE CVE-2024-53161 https://www.cve.org/CVERecord?id=CVE-2024-53161 Référence CVE CVE-2024-58007 https://www.cve.org/CVERecord?id=CVE-2024-58007 Référence CVE CVE-2025-40026 https://www.cve.org/CVERecord?id=CVE-2025-40026 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-68745 https://www.cve.org/CVERecord?id=CVE-2025-68745 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23172 https://www.cve.org/CVERecord?id=CVE-2026-23172 Référence CVE CVE-2026-23466 https://www.cve.org/CVERecord?id=CVE-2026-23466 Référence CVE CVE-2026-31479 https://www.cve.org/CVERecord?id=CVE-2026-31479 Référence CVE CVE-2026-31539 https://www.cve.org/CVERecord?id=CVE-2026-31539 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=CVE-2026-31566 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31663 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38201 Référence CVE CVE-2025-40005 https://www.cve.org/CVERecord?id=CVE-2025-40005 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-71088 https://www.cve.org/CVERecord?id=CVE-2025-71088 Référence CVE CVE-2025-71089 https://www.cve.org/CVERecord?id=CVE-2025-71089 Référence CVE CVE-2025-71090 https://www.cve.org/CVERecord?id=CVE-2025-71090 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71134 https://www.cve.org/CVERecord?id=CVE-2025-71134 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-71144 https://www.cve.org/CVERecord?id=CVE-2025-71144 Référence CVE CVE-2025-71152 https://www.cve.org/CVERecord?id=CVE-2025-71152 Référence CVE CVE-2025-71155 https://www.cve.org/CVERecord?id=CVE-2025-71155 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71222 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-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-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=

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

letin de sécurité Ubuntu USN-8370-1 du 02 juin 2026 https://ubuntu.com/security/notices/USN-8370-1 Bulletin de sécurité Ubuntu USN-8371-1 du 02 juin 2026 https://ubuntu.com/security/notices/USN-8371-1 Bulletin de sécurité Ubuntu USN-8373-1 du 02 juin 2026 https://ubuntu.com/security/notices/USN-8373-1 Bulletin de sécurité Ubuntu USN-8374-1 du 02 juin 2026 https://ubuntu.com/security/notices/USN-8374-1 Référence CVE CVE-2025-37849 https://www.cve.org/CVERecord?id=CVE-2025-37849 Référence CVE CVE-2025-71088 https://www.cve.org/CVERecord?id=CVE-2025-71088 Référence CVE CVE-2025-71090 https://www.cve.org/CVERecord?id=CVE-2025-71090 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71134 https://www.cve.org/CVERecord?id=CVE-2025-71134 Référence CVE CVE-2025-71139 https://www.cve.org/CVERecord?id=CVE-2025-71139 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-71144 https://www.cve.org/CVERecord?id=CVE-2025-71144 Référence CVE CVE-2025-71152 https://www.cve.org/CVERecord?id=CVE-2025-71152 Référence CVE CVE-2025-71155 https://www.cve.org/CVERecord?id=CVE-2025-71155 Référence CVE CVE-2026-23112 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68358 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68749 https://www.cve.org/CVERecord?id=CVE-2025-68749 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68817 https://www.cve.org/CVERecord?id=CVE-2025-68817 Référence CVE CVE-2025-68823 https://www.cve.org/CVERecord?id=CVE-2025-68823 Référence CVE CVE-2025-71088 https://www.cve.org/CVERecord?id=CVE-2025-71088 Référence CVE CVE-2025-71090 https://www.cve.org/CVERecord?id=CVE-2025-71090 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71134 https://www.cve.org/CVERecord?id=CVE-2025-71134 Référence CVE CVE-2025-71139 https://www.cve.org/CVERecord?id=CVE-2025-71139 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-71144 https://www.cve.org/CVERecord?id=CVE-2025-71144 Référence CVE CVE-2025-71152 https://www.cve.org/CVERecord?id=CVE-2025-71152 Référence CVE CVE-2025-71155 https://www.cve.org/CVERecord?id=CVE-2025-71155 Référence CVE CVE-2025-71160 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68358 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68749 https://www.cve.org/CVERecord?id=CVE-2025-68749 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68817 https://www.cve.org/CVERecord?id=CVE-2025-68817 Référence CVE CVE-2025-68823 https://www.cve.org/CVERecord?id=CVE-2025-68823 Référence CVE CVE-2025-71088 https://www.cve.org/CVERecord?id=CVE-2025-71088 Référence CVE CVE-2025-71090 https://www.cve.org/CVERecord?id=CVE-2025-71090 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71134 https://www.cve.org/CVERecord?id=CVE-2025-71134 Référence CVE CVE-2025-71139 https://www.cve.org/CVERecord?id=CVE-2025-71139 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-71144 https://www.cve.org/CVERecord?id=CVE-2025-71144 Référence CVE CVE-2025-71152 https://www.cve.org/CVERecord?id=CVE-2025-71152 Référence CVE CVE-2025-71155 https://www.cve.org/CVERecord?id=CVE-2025-71155 Référence CVE CVE-2025-71160 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-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-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=

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

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-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=

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

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-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=

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

d?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-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-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=

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

d?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-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-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=

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

d?id=CVE-2025-71111 Référence CVE CVE-2025-71112 https://www.cve.org/CVERecord?id=CVE-2025-71112 Référence CVE CVE-2025-71113 https://www.cve.org/CVERecord?id=CVE-2025-71113 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-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=

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

d?id=CVE-2025-71111 Référence CVE CVE-2025-71112 https://www.cve.org/CVERecord?id=CVE-2025-71112 Référence CVE CVE-2025-71113 https://www.cve.org/CVERecord?id=CVE-2025-71113 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-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=

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

d?id=CVE-2025-71111 Référence CVE CVE-2025-71112 https://www.cve.org/CVERecord?id=CVE-2025-71112 Référence CVE CVE-2025-71113 https://www.cve.org/CVERecord?id=CVE-2025-71113 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-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=

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

d?id=CVE-2025-71111 Référence CVE CVE-2025-71112 https://www.cve.org/CVERecord?id=CVE-2025-71112 Référence CVE CVE-2025-71113 https://www.cve.org/CVERecord?id=CVE-2025-71113 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-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=

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

d?id=CVE-2025-71112 Référence CVE CVE-2025-71113 https://www.cve.org/CVERecord?id=CVE-2025-71113 Référence CVE CVE-2025-71114 https://www.cve.org/CVERecord?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=

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

d?id=CVE-2025-71112 Référence CVE CVE-2025-71113 https://www.cve.org/CVERecord?id=CVE-2025-71113 Référence CVE CVE-2025-71114 https://www.cve.org/CVERecord?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=

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

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-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=

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

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-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-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=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。wifi: mac80211は、ブロードキャストアドレス以外の宛先へのBeaconフレームを破棄します。Beaconフレームはブロードキャストアドレスに送信される必要があり、IEEE Std 802.11-2020の11.1.3.1（「BeaconフレームのAddress 1フィールドはブロードキャストアドレスに設定されなければならない」）に準じています。ユニキャストのBeaconフレームは、接続されたSTAの一つに対して何かを実行させる（例えばCSAを用いて別のチャネルに移動させる）標的攻撃に利用される可能性があります。そのため、受信側ではこれを厳密にフィルタリングし、予期しないアドレスに送信されるすべてのBeaconフレームを破棄することが望ましいです。この対応は、Beacon保護が使用される場合にさらに重要です。mac80211の現行実装では、Frame ControlフィールドのProtected Frameビットが0の場合、ユニキャストのBeaconフレームを正しく破棄します。しかし、このビットが1に設定されている場合、BIGTKの設定確認ロジックは正しく機能しません。ドライバーにProtected Frameビット1のユニキャストBeaconを破棄するロジックがない場合、これらのフレームは保護されていないにもかかわらずmac80211の処理で有効なBeaconフレームとして受け入れられ、Beacon保護が回避される恐れがあります。このコーナーケースをカバーするためにBeacon保護のチェックロジックを拡張することも可能ですが、A1フィールドがユニキャストアドレスの場合にすべてのBeaconフレームを破棄する、より汎用的なチェックによって追加の変更なく対処可能です。非ブロードキャストアドレスに送信された受信Beaconフレームを破棄することで、これらの問題をすべて解決します。

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: < 5.7, 5.10.248 ≤ 5.10.*, 5.15.198 ≤ 5.15.*, 6.1.160 ≤ 6.1.*, 6.6.120 ≤ 6.6.*, 6.12.65 ≤ 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. Limit untrusted access and use least privilege 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-2465
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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-71127 to remediation: access.redhat.com/CVE-2025-71127.
    Before
    remediation: access.redhat.com/CVE-2025-71127
    After
    remediation: access.redhat.com/CVE-2025-71127
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    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 216 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 168 more · Fixed: bpftool-0:4.18.0-553.163.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.163.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.163.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.163.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.163.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.163.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.163.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.163.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.163.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.163.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.163.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.163.1.el8_10.src as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.163.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-abi-stablelists-0:4.18.0-553.163.1.el8_10.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.163.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.163.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.163.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.163.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.163.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.163.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.163.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.163.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.163.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.163.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.163.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.163.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.163.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.163.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.163.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.163.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); and 120 more
    Red Hat Product Security ↗
  4. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2025-71127 to remediation: access.redhat.com/CVE-2025-71127.
    Before
    remediation: access.redhat.com/CVE-2025-71127
    After
    remediation: access.redhat.com/CVE-2025-71127
    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-2465↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update 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-71127 · cve.blacktree.nl