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

exit: prevent preemption of oopsing TASK_DEAD task

Linux · Linux

7.8HighCVSS 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 25 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:Medium, lowered one band.downgradedsince 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.17% 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: As exposure requiresRemediation target: Within 365 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 25 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.88-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.7-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.7-1Debian Security Tracker ↗Source updated 7 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.

2 current
CVE-2026-46173 · CSAF 2.0 · revision 36 · interimSUSE Product Security TeamCVE-2026-46173
17 known affected

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

  • SUSE Linux Micro Extras 6.2:kernel-obs-build
  • SUSE Linux Micro Extras 6.2:kernel-syms
  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
Summary
In the Linux kernel, the following vulnerability has been resolved: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resulting in various kinds of memory corruption. (This does not just affect "recursively oopsing" tasks; it is enough to oops once during task exit, for example in a file_operations::release handler)
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resulting in various kinds of memory corruption. (This does not just affect "recursively oopsing" tasks; it is enough to oops once during task exit, for example in a file_operations::release handler)
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-32800

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resulting in various kinds of memory corruption. (This does not just affect "recursively oopsing" tasks; it is enough to oops once during task exit, for example in a file_operations::release handler)

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
7.8 · CVSS 3.1
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 25 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: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resulting in various kinds of memory corruption. (This does not just affect "recursively oopsing" tasks; it is enough to oops once during task exit, for example in a file_operations::release handler)

What

In the Linux kernel, the following vulnerability has been resolved: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resulting in various kinds of memory corruption. (This does not just affect "recursively oopsing" tasks; it is enough to oops once during task exit, for example in a file_operations::release handler)

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through local access may attempt exploitation with low privileges. 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: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resulting in various kinds of memory corruption. (This does not just affect "recursively oopsing" tasks; it is enough to oops once during task exit, for example in a file_operations::release handler)

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through local access may attempt exploitation with low privileges. 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
local access → Out-of-bounds Write → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
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-787 ↗

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-787
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-32800Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resulting in various kinds of memory corruption. (This does not just affect "recursively oopsing" tasks; it is enough to oops once during task exit, for example in a file_operations::release handler)

Official EUVD record ↗
BSI · German · WID-SEC-2026-3623IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen, einen Denial-of-Service-Zustand auszulösen oder Cross-Site-Scripting-Angriffe durchzuführen.

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

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

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

d?id=CVE-2026-46164 Référence CVE CVE-2026-46165 https://www.cve.org/CVERecord?id=CVE-2026-46165 Référence CVE CVE-2026-46166 https://www.cve.org/CVERecord?id=CVE-2026-46166 Référence CVE CVE-2026-46167 https://www.cve.org/CVERecord?id=CVE-2026-46167 Référence CVE CVE-2026-46168 https://www.cve.org/CVERecord?id=CVE-2026-46168 Référence CVE CVE-2026-46169 https://www.cve.org/CVERecord?id=CVE-2026-46169 Référence CVE CVE-2026-46170 https://www.cve.org/CVERecord?id=CVE-2026-46170 Référence CVE CVE-2026-46171 https://www.cve.org/CVERecord?id=CVE-2026-46171 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46174 https://www.cve.org/CVERecord?id=CVE-2026-46174 Référence CVE CVE-2026-46175 https://www.cve.org/CVERecord?id=CVE-2026-46175 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46164 Référence CVE CVE-2026-46165 https://www.cve.org/CVERecord?id=CVE-2026-46165 Référence CVE CVE-2026-46166 https://www.cve.org/CVERecord?id=CVE-2026-46166 Référence CVE CVE-2026-46167 https://www.cve.org/CVERecord?id=CVE-2026-46167 Référence CVE CVE-2026-46168 https://www.cve.org/CVERecord?id=CVE-2026-46168 Référence CVE CVE-2026-46169 https://www.cve.org/CVERecord?id=CVE-2026-46169 Référence CVE CVE-2026-46170 https://www.cve.org/CVERecord?id=CVE-2026-46170 Référence CVE CVE-2026-46171 https://www.cve.org/CVERecord?id=CVE-2026-46171 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46174 https://www.cve.org/CVERecord?id=CVE-2026-46174 Référence CVE CVE-2026-46175 https://www.cve.org/CVERecord?id=CVE-2026-46175 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46164 Référence CVE CVE-2026-46165 https://www.cve.org/CVERecord?id=CVE-2026-46165 Référence CVE CVE-2026-46166 https://www.cve.org/CVERecord?id=CVE-2026-46166 Référence CVE CVE-2026-46167 https://www.cve.org/CVERecord?id=CVE-2026-46167 Référence CVE CVE-2026-46168 https://www.cve.org/CVERecord?id=CVE-2026-46168 Référence CVE CVE-2026-46169 https://www.cve.org/CVERecord?id=CVE-2026-46169 Référence CVE CVE-2026-46170 https://www.cve.org/CVERecord?id=CVE-2026-46170 Référence CVE CVE-2026-46171 https://www.cve.org/CVERecord?id=CVE-2026-46171 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46174 https://www.cve.org/CVERecord?id=CVE-2026-46174 Référence CVE CVE-2026-46175 https://www.cve.org/CVERecord?id=CVE-2026-46175 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46164 Référence CVE CVE-2026-46165 https://www.cve.org/CVERecord?id=CVE-2026-46165 Référence CVE CVE-2026-46166 https://www.cve.org/CVERecord?id=CVE-2026-46166 Référence CVE CVE-2026-46167 https://www.cve.org/CVERecord?id=CVE-2026-46167 Référence CVE CVE-2026-46168 https://www.cve.org/CVERecord?id=CVE-2026-46168 Référence CVE CVE-2026-46169 https://www.cve.org/CVERecord?id=CVE-2026-46169 Référence CVE CVE-2026-46170 https://www.cve.org/CVERecord?id=CVE-2026-46170 Référence CVE CVE-2026-46171 https://www.cve.org/CVERecord?id=CVE-2026-46171 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46174 https://www.cve.org/CVERecord?id=CVE-2026-46174 Référence CVE CVE-2026-46175 https://www.cve.org/CVERecord?id=CVE-2026-46175 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46116 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46160 https://www.cve.org/CVERecord?id=CVE-2026-46160 Référence CVE CVE-2026-46161 https://www.cve.org/CVERecord?id=CVE-2026-46161 Référence CVE CVE-2026-46162 https://www.cve.org/CVERecord?id=CVE-2026-46162 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46214 https://www.cve.org/CVERecord?id=CVE-2026-46214 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46164 Référence CVE CVE-2026-46165 https://www.cve.org/CVERecord?id=CVE-2026-46165 Référence CVE CVE-2026-46166 https://www.cve.org/CVERecord?id=CVE-2026-46166 Référence CVE CVE-2026-46167 https://www.cve.org/CVERecord?id=CVE-2026-46167 Référence CVE CVE-2026-46168 https://www.cve.org/CVERecord?id=CVE-2026-46168 Référence CVE CVE-2026-46169 https://www.cve.org/CVERecord?id=CVE-2026-46169 Référence CVE CVE-2026-46170 https://www.cve.org/CVERecord?id=CVE-2026-46170 Référence CVE CVE-2026-46171 https://www.cve.org/CVERecord?id=CVE-2026-46171 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46174 https://www.cve.org/CVERecord?id=CVE-2026-46174 Référence CVE CVE-2026-46175 https://www.cve.org/CVERecord?id=CVE-2026-46175 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46152 Référence CVE CVE-2026-46160 https://www.cve.org/CVERecord?id=CVE-2026-46160 Référence CVE CVE-2026-46161 https://www.cve.org/CVERecord?id=CVE-2026-46161 Référence CVE CVE-2026-46162 https://www.cve.org/CVERecord?id=CVE-2026-46162 Référence CVE CVE-2026-46163 https://www.cve.org/CVERecord?id=CVE-2026-46163 Référence CVE CVE-2026-46165 https://www.cve.org/CVERecord?id=CVE-2026-46165 Référence CVE CVE-2026-46166 https://www.cve.org/CVERecord?id=CVE-2026-46166 Référence CVE CVE-2026-46167 https://www.cve.org/CVERecord?id=CVE-2026-46167 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=CVE-2026-46187 Référence CVE CVE-2026-46190 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46164 Référence CVE CVE-2026-46165 https://www.cve.org/CVERecord?id=CVE-2026-46165 Référence CVE CVE-2026-46166 https://www.cve.org/CVERecord?id=CVE-2026-46166 Référence CVE CVE-2026-46167 https://www.cve.org/CVERecord?id=CVE-2026-46167 Référence CVE CVE-2026-46168 https://www.cve.org/CVERecord?id=CVE-2026-46168 Référence CVE CVE-2026-46169 https://www.cve.org/CVERecord?id=CVE-2026-46169 Référence CVE CVE-2026-46170 https://www.cve.org/CVERecord?id=CVE-2026-46170 Référence CVE CVE-2026-46171 https://www.cve.org/CVERecord?id=CVE-2026-46171 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46174 https://www.cve.org/CVERecord?id=CVE-2026-46174 Référence CVE CVE-2026-46175 https://www.cve.org/CVERecord?id=CVE-2026-46175 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46028 Référence CVE CVE-2026-46065 https://www.cve.org/CVERecord?id=CVE-2026-46065 Référence CVE CVE-2026-46069 https://www.cve.org/CVERecord?id=CVE-2026-46069 Référence CVE CVE-2026-46082 https://www.cve.org/CVERecord?id=CVE-2026-46082 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46133 https://www.cve.org/CVERecord?id=CVE-2026-46133 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46229 https://www.cve.org/CVERecord?id=CVE-2026-46229 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 Référence CVE CVE-2026-46254 https://www.cve.org/CVERecord?id=CVE-2026-46254 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43330 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46152 https://www.cve.org/CVERecord?id=CVE-2026-46152 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46316 https://www.cve.org/CVERecord?id=CVE-2026-46316 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53166 https://www.cve.org/CVERecord?id=CVE-2026-53166 Référence CVE CVE-2026-53266 https://www.cve.org/CVERecord?id=CVE-2026-53266 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46123 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46133 https://www.cve.org/CVERecord?id=CVE-2026-46133 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46157 https://www.cve.org/CVERecord?id=CVE-2026-46157 Référence CVE CVE-2026-46159 https://www.cve.org/CVERecord?id=CVE-2026-46159 Référence CVE CVE-2026-46160 https://www.cve.org/CVERecord?id=CVE-2026-46160 Référence CVE CVE-2026-46162 https://www.cve.org/CVERecord?id=CVE-2026-46162 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46214 https://www.cve.org/CVERecord?id=CVE-2026-46214 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46229 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46160 Référence CVE CVE-2026-46161 https://www.cve.org/CVERecord?id=CVE-2026-46161 Référence CVE CVE-2026-46163 https://www.cve.org/CVERecord?id=CVE-2026-46163 Référence CVE CVE-2026-46164 https://www.cve.org/CVERecord?id=CVE-2026-46164 Référence CVE CVE-2026-46165 https://www.cve.org/CVERecord?id=CVE-2026-46165 Référence CVE CVE-2026-46167 https://www.cve.org/CVERecord?id=CVE-2026-46167 Référence CVE CVE-2026-46168 https://www.cve.org/CVERecord?id=CVE-2026-46168 Référence CVE CVE-2026-46169 https://www.cve.org/CVERecord?id=CVE-2026-46169 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46177 https://www.cve.org/CVERecord?id=CVE-2026-46177 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46179 https://www.cve.org/CVERecord?id=CVE-2026-46179 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46184 https://www.cve.org/CVERecord?id=CVE-2026-46184 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46186 https://www.cve.org/CVERecord?id=CVE-2026-46186 Référence CVE CVE-2026-46187 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43501 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46152 https://www.cve.org/CVERecord?id=CVE-2026-46152 Référence CVE CVE-2026-46155 https://www.cve.org/CVERecord?id=CVE-2026-46155 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43198 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43329 https://www.cve.org/CVERecord?id=CVE-2026-43329 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46054 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46117 https://www.cve.org/CVERecord?id=CVE-2026-46117 Référence CVE CVE-2026-46125 https://www.cve.org/CVERecord?id=CVE-2026-46125 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46145 https://www.cve.org/CVERecord?id=CVE-2026-46145 Référence CVE CVE-2026-46152 https://www.cve.org/CVERecord?id=CVE-2026-46152 Référence CVE CVE-2026-46166 https://www.cve.org/CVERecord?id=CVE-2026-46166 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-4878 https://www.cve.org/CVERecord?id=CVE-2026-4878 Gestion détaillée du document le 26 juin 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

mai 2026 Bulletin de sécurité Microsoft CVE-2026-46156 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46159 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46160 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46161 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46163 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46164 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46165 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46167 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46168 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46172 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46173 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46176 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46177 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46178 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46180 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46185 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46186 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46187 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46189 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46190 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46191 du 29 mai 2026 Bulletin de sécurité Mic

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-019323LinuxのLinux Kernelにおける境界外書き込みに関する脆弱性

Linuxカーネルにおいて、exit処理中にTASK_DEAD状態のタスクのプリエンプションを防止するための修正が行われました。終了処理中のタスクがoops発生時にプリエンプション可能な状態でdo_task_dead()を呼び出すことは許されておらず、これによりTASK_DEAD状態のタスクのスタック解放時にuse-after-freeやダブルフリー、メモリ破損が発生する可能性がありました。本脆弱性は、タスクの終了時に一度でもoopsが発生すると起こる可能性があります。

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.17, 6.1.175 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.88 ≤ 6.12.*, 6.18.30 ≤ 6.18.*, 7.0.7 ≤ 7.0.*, 7.1 ≤ *
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 28 May 2026 · Last source change 8 Sept 2026, 08:49 UTC · CWE-787 · Out-of-bounds Write

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-32800
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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. Affected versionsThe structured affected or fixed version information changed.
    Before
    7f80a2fd7db9a55894fd841915236aca611291b5 < 3d6fb8a7690c23e3213c4b008f64d89a44b98737; 7f80a2fd7db9a55894fd841915236aca611291b5 < 640b4c00fb0e2920327435f6176cbefc3c546165; 7f80a2fd7db9a55894fd841915236aca611291b5 < 7b2800ba5f5f77a8ee7f4cbadb19cf1264597a34; 7f80a2fd7db9a55894fd841915236aca611291b5 < 6f49f94f3b11fe8bff1bf2a054143789e76aaf17; 7f80a2fd7db9a55894fd841915236aca611291b5 < 9756b3db5db6c2f5eccb32dddbd88eb4c54f575e; 7f80a2fd7db9a55894fd841915236aca611291b5 < c1fa0bb633e4a6b11e83ffc57fa5abe8ebb87891; 5.17 · Fixed: < 5.17; 6.1.175 ≤ 6.1.*; 6.6.140 ≤ 6.6.*; 6.12.88 ≤ 6.12.*; 6.18.30 ≤ 6.18.*; 7.0.7 ≤ 7.0.*; 7.1 ≤ *
    After
    Linux: 7f80a2fd7db9a55894fd841915236aca611291b5 < 3d6fb8a7690c23e3213c4b008f64d89a44b98737, 7f80a2fd7db9a55894fd841915236aca611291b5 < 640b4c00fb0e2920327435f6176cbefc3c546165, 7f80a2fd7db9a55894fd841915236aca611291b5 < 7b2800ba5f5f77a8ee7f4cbadb19cf1264597a34, 7f80a2fd7db9a55894fd841915236aca611291b5 < 6f49f94f3b11fe8bff1bf2a054143789e76aaf17, 7f80a2fd7db9a55894fd841915236aca611291b5 < 9756b3db5db6c2f5eccb32dddbd88eb4c54f575e, 7f80a2fd7db9a55894fd841915236aca611291b5 < c1fa0bb633e4a6b11e83ffc57fa5abe8ebb87891, 5.17 · Fixed: Linux: < 5.17, 6.1.175 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.88 ≤ 6.12.*, 6.18.30 ≤ 6.18.*, 7.0.7 ≤ 7.0.*, 7.1 ≤ *
    CNA ↗
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-32800↗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-2026-46173 · cve.blacktree.nl