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

net/sched: Enforce that teql can only be used as root qdisc

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 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:Medium, lowered one band.downgradedsince 17 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.16% 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 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.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.8-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.

1 current
CVE-2026-23074 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Linux kernel: Use-after-free in teql queueing discipline can lead to privilege escalation
604 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • kernel-0:2.6.32-754.59.1.el6.i686 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION)
  • kernel-0:2.6.32-754.59.1.el6.s390x as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION)
  • kernel-0:2.6.32-754.59.1.el6.src as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION)
  • kernel-0:2.6.32-754.59.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION)
  • kernel-abi-whitelists-0:2.6.32-754.59.1.el6.noarch as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION)
  • kernel-debug-0:2.6.32-754.59.1.el6.i686 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION)
  • kernel-debug-0:2.6.32-754.59.1.el6.s390x as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION)
  • kernel-debug-0:2.6.32-754.59.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION)
  • kernel-debug-debuginfo-0:2.6.32-754.59.1.el6.i686 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION)
  • kernel-debug-debuginfo-0:2.6.32-754.59.1.el6.s390x as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION)
  • kernel-debug-debuginfo-0:2.6.32-754.59.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION)
  • kernel-debug-devel-0:2.6.32-754.59.1.el6.i686 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION)
Summary
A flaw was found in the Linux kernel's networking component. A local attacker with low privileges could exploit a design issue in the teql queueing discipline, which is responsible for managing network traffic. By sending specially crafted network packets, an attacker could trigger a use-after-free (UAF) vulnerability, which is a type of memory corruption. This could lead to a system crash, or potentially allow the attacker to execute unauthorized code or gain elevated system access.
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.
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-5470

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net/sched: Enforce that teql can only be used as root qdisc Design intent of teql is that it is only supposed to be used as root qdisc. We need to check for that constraint. Although not important, I will describe the scenario that unearthed this issue for the curious. GangMin Kim <km.kim1503@gmail.com> managed to concot a scenario as follows: ROOT qdisc 1:0 (QFQ) ├── class 1:1 (weight=15, lmax=16384) netem with delay 6.4s └── class 1:2 (weight=1, lmax=1514) teql GangMin sends a packet which is enqueued to 1:1 (netem). Any invocation of dequeue by QFQ from this class will not return a packet until after 6.4s. In the meantime, a second packet is sent and it lands on 1:2. teql's enqueue will return success and this will activate class 1:2. Main issue is that teql only updates the parent visible qlen (sch->q.qlen) at dequeue. Since QFQ will only call dequeue if peek succeeds (and teql's peek always returns NULL), dequeue will never be called and thus the qlen will remain as 0. With that in mind, when GangMin updates 1:2's lmax value, the qfq_change_class calls qfq_deact_rm_from_agg. Since the child qdisc's qlen was not incremented, qfq fails to deactivate the class, but still frees its pointers from the aggregate. So when the first packet is rescheduled after 6.4 seconds (netem's delay), a dangling pointer is accessed causing GangMin's causing a UAF.

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 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: net/sched: Enforce that teql can only be used as root qdisc Design intent of teql is that it is only supposed to be used as root qdisc. We need to check for that constraint. Although not important, I will describe the scenario that unearthed this issue for the curious. GangMin Kim <km.kim1503@gmail.com> managed to concot a scenario as follows: ROOT qdisc 1:0 (QFQ) ├── class 1:1 (weight=15, lmax=16384) netem with delay 6.4s └── class 1:2 (weight=1, lmax=1514) teql GangMin sends a packet which is enqueued to 1:1 (netem). Any invocation of dequeue by QFQ from this class will not return a packet until after 6.4s. In the meantime, a second packet is sent and it lands on 1:2. teql's enqueue will return success and this will activate class 1:2. Main issue is that teql only updates the parent visible qlen (sch->q.qlen) at dequeue. Since QFQ will only call dequeue if peek succeeds (and teql's peek always returns NULL), dequeue will never be called and thus the qlen will remain as 0. With that in mind, when GangMin updates 1:2's lmax value, the qfq_change_class calls qfq_deact_rm_from_agg. Since the child qdisc's qlen was not incremented, qfq fails to deactivate the class, but still frees its pointers from the aggregate. So when the first packet is rescheduled after 6.4 seconds (netem's delay), a dangling pointer is accessed causing GangMin's causing a UAF.

What

In the Linux kernel, the following vulnerability has been resolved: net/sched: Enforce that teql can only be used as root qdisc Design intent of teql is that it is only supposed to be used as root qdisc. We need to check for that constraint. Although not important, I will describe the scenario that unearthed this issue for the curious. GangMin Kim <km.kim1503@gmail.com> managed to concot a scenario as follows: ROOT qdisc 1:0 (QFQ) ├── class 1:1 (weight=15, lmax=16384) netem with delay 6.4s └── class 1:2 (weight=1, lmax=1514) teql GangMin sends a packet which is enqueued to 1:1 (netem). Any invocation of dequeue by QFQ from this class will not return a packet until after 6.4s. In the meantime, a second packet is sent and it lands on 1:2. teql's enqueue will return success and this will activate class 1:2. Main issue is that teql only updates the parent visible qlen (sch->q.qlen) at dequeue. Since QFQ will only call dequeue if peek succeeds (and teql's peek always returns NULL), dequeue will never be called and thus the qlen will remain as 0. With that in mind, when GangMin updates 1:2's lmax value, the qfq_change_class calls qfq_deact_rm_from_agg. Since the child qdisc's qlen was not incremented, qfq fails to deactivate the class, but still frees its pointers from the aggregate. So when the first packet is rescheduled after 6.4 seconds (netem's delay), a dangling pointer is accessed causing GangMin's causing a UAF.

Why

The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

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: net/sched: Enforce that teql can only be used as root qdisc Design intent of teql is that it is only supposed to be used as root qdisc. We need to check for that constraint. Although not important, I will describe the scenario that unearthed this issue for the curious. GangMin Kim <km.kim1503@gmail.com> managed to concot a scenario as follows: ROOT qdisc 1:0 (QFQ) ├── class 1:1 (weight=15, lmax=16384) netem with delay 6.4s └── class 1:2 (weight=1, lmax=1514) teql GangMin sends a packet which is enqueued to 1:1 (netem). Any invocation of dequeue by QFQ from this class will not return a packet until after 6.4s. In the meantime, a second packet is sent and it lands on 1:2. teql's enqueue will return success and this will activate class 1:2. Main issue is that teql only updates the parent visible qlen (sch->q.qlen) at dequeue. Since QFQ will only call dequeue if peek succeeds (and teql's peek always returns NULL), dequeue will never be called and thus the qlen will remain as 0. With that in mind, when GangMin updates 1:2's lmax value, the qfq_change_class calls qfq_deact_rm_from_agg. Since the child qdisc's qlen was not incremented, qfq fails to deactivate the class, but still frees its pointers from the aggregate. So when the first packet is rescheduled after 6.4 seconds (netem's delay), a dangling pointer is accessed causing GangMin's causing a UAF.

Why

The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

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 → Expired Pointer Dereference → 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-825 ↗

CWE-825: Expired Pointer Dereference. The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

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-825
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-5470Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net/sched: Enforce that teql can only be used as root qdisc Design intent of teql is that it is only supposed to be used as root qdisc. We need to check for that constraint. Although not important, I will describe the scenario that unearthed this issue for the curious. GangMin Kim <km.kim1503@gmail.com> managed to concot a scenario as follows: ROOT qdisc 1:0 (QFQ) ├── class 1:1 (weight=15, lmax=16384) netem with delay 6.4s └── class 1:2 (weight=1, lmax=1514) teql GangMin sends a packet which is enqueued to 1:1 (netem). Any invocation of dequeue by QFQ from this class will not return a packet until after 6.4s. In the meantime, a second packet is sent and it lands on 1:2. teql's enqueue will return success and this will activate class 1:2. Main issue is that teql only updates the parent visible qlen (sch->q.qlen) at dequeue. Since QFQ will only call dequeue if peek succeeds (and teql's peek always returns NULL), dequeue will never be called and thus the qlen will remain as 0. With that in mind, when GangMin updates 1:2's lmax value, the qfq_change_class calls qfq_deact_rm_from_agg. Since the child qdisc's qlen was not incremented, qfq fails to deactivate the class, but still frees its pointers from the aggregate. So when the first packet is rescheduled after 6.4 seconds (netem's delay), a dangling pointer is accessed causing GangMin's causing a UAF.

Official EUVD record ↗
BSI · German · WID-SEC-2026-0324Linux 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-20260211Security Bulletin 11 Feb 2026

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

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

d?id=CVE-2026-23049 Référence CVE CVE-2026-23056 https://www.cve.org/CVERecord?id=CVE-2026-23056 Référence CVE CVE-2026-23058 https://www.cve.org/CVERecord?id=CVE-2026-23058 Référence CVE CVE-2026-23060 https://www.cve.org/CVERecord?id=CVE-2026-23060 Référence CVE CVE-2026-23061 https://www.cve.org/CVERecord?id=CVE-2026-23061 Référence CVE CVE-2026-23063 https://www.cve.org/CVERecord?id=CVE-2026-23063 Référence CVE CVE-2026-23064 https://www.cve.org/CVERecord?id=CVE-2026-23064 Référence CVE CVE-2026-23071 https://www.cve.org/CVERecord?id=CVE-2026-23071 Référence CVE CVE-2026-23073 https://www.cve.org/CVERecord?id=CVE-2026-23073 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23075 https://www.cve.org/CVERecord?id=CVE-2026-23075 Référence CVE CVE-2026-23076 https://www.cve.org/CVERecord?id=CVE-2026-23076 Référence CVE CVE-2026-23078 https://www.cve.org/CVERecord?id=CVE-2026-23078 Référence CVE CVE-2026-23080 https://www.cve.org/CVERecord?id=CVE-2026-23080 Référence CVE CVE-2026-23083 https://www.cve.org/CVERecord?id=CVE-2026-23083 Référence CVE CVE-2026-23084 https://www.cve.org/CVERecord?id=CVE-2026-23084 Référence CVE CVE-2026-23085 https://www.cve.org/CVERecord?id=CVE-2026-23085 Référence CVE CVE-2026-23087 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-2026-23049 Référence CVE CVE-2026-23056 https://www.cve.org/CVERecord?id=CVE-2026-23056 Référence CVE CVE-2026-23058 https://www.cve.org/CVERecord?id=CVE-2026-23058 Référence CVE CVE-2026-23060 https://www.cve.org/CVERecord?id=CVE-2026-23060 Référence CVE CVE-2026-23061 https://www.cve.org/CVERecord?id=CVE-2026-23061 Référence CVE CVE-2026-23063 https://www.cve.org/CVERecord?id=CVE-2026-23063 Référence CVE CVE-2026-23064 https://www.cve.org/CVERecord?id=CVE-2026-23064 Référence CVE CVE-2026-23071 https://www.cve.org/CVERecord?id=CVE-2026-23071 Référence CVE CVE-2026-23073 https://www.cve.org/CVERecord?id=CVE-2026-23073 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23075 https://www.cve.org/CVERecord?id=CVE-2026-23075 Référence CVE CVE-2026-23076 https://www.cve.org/CVERecord?id=CVE-2026-23076 Référence CVE CVE-2026-23078 https://www.cve.org/CVERecord?id=CVE-2026-23078 Référence CVE CVE-2026-23080 https://www.cve.org/CVERecord?id=CVE-2026-23080 Référence CVE CVE-2026-23083 https://www.cve.org/CVERecord?id=CVE-2026-23083 Référence CVE CVE-2026-23084 https://www.cve.org/CVERecord?id=CVE-2026-23084 Référence CVE CVE-2026-23085 https://www.cve.org/CVERecord?id=CVE-2026-23085 Référence CVE CVE-2026-23087 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0539Multiples vulnérabilités dans Juniper Networks Secure Analytics

De multiples vulnérabilités ont été découvertes dans Juniper Networks Secure Analytics. Elles permettent à un attaquant de provoquer un déni de service à distance et un problème de sécurité non spécifié par l'éditeur.

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

d?id=CVE-2025-71144 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71148 https://www.cve.org/CVERecord?id=CVE-2025-71148 Référence CVE CVE-2025-71149 https://www.cve.org/CVERecord?id=CVE-2025-71149 Référence CVE CVE-2025-71150 https://www.cve.org/CVERecord?id=CVE-2025-71150 Référence CVE CVE-2025-71151 https://www.cve.org/CVERecord?id=CVE-2025-71151 Référence CVE CVE-2025-71153 https://www.cve.org/CVERecord?id=CVE-2025-71153 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2026-23060 https://www.cve.org/CVERecord?id=CVE-2026-23060 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23209 https://www.cve.org/CVERecord?id=CVE-2026-23209 Référence CVE CVE-2026-23268 https://www.cve.org/CVERecord?id=CVE-2026-23268 Référence CVE CVE-2026-23269 https://www.cve.org/CVERecord?id=CVE-2026-23269 Référence CVE CVE-2026-23403 https://www.cve.org/CVERecord?id=CVE-2026-23403 Référence CVE CVE-2026-23404 https://www.cve.org/CVERecord?id=CVE-2026-23404 Référence CVE CVE-2026-23405 https://www.cve.org/CVERecord?id=CVE-2026-23405 Référence CVE CVE-2026-23406 https://www.cve.org/CVERecord?id=CVE-2026-23406 Référence CVE CVE-2026-23407 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71239 Référence CVE CVE-2025-71268 https://www.cve.org/CVERecord?id=CVE-2025-71268 Référence CVE CVE-2025-71269 https://www.cve.org/CVERecord?id=CVE-2025-71269 Référence CVE CVE-2026-22999 https://www.cve.org/CVERecord?id=CVE-2026-22999 Référence CVE CVE-2026-23030 https://www.cve.org/CVERecord?id=CVE-2026-23030 Référence CVE CVE-2026-23047 https://www.cve.org/CVERecord?id=CVE-2026-23047 Référence CVE CVE-2026-23054 https://www.cve.org/CVERecord?id=CVE-2026-23054 Référence CVE CVE-2026-23069 https://www.cve.org/CVERecord?id=CVE-2026-23069 Référence CVE CVE-2026-23072 https://www.cve.org/CVERecord?id=CVE-2026-23072 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23088 https://www.cve.org/CVERecord?id=CVE-2026-23088 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 Référence CVE CVE-2026-23120 https://www.cve.org/CVERecord?id=CVE-2026-23120 Référence CVE CVE-2026-23125 https://www.cve.org/CVERecord?id=CVE-2026-23125 Référence CVE CVE-2026-23136 https://www.cve.org/CVERecord?id=CVE-2026-23136 Référence CVE CVE-2026-23138 https://www.cve.org/CVERecord?id=CVE-2026-23138 Référence CVE CVE-2026-23140 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-2026-23049 Référence CVE CVE-2026-23056 https://www.cve.org/CVERecord?id=CVE-2026-23056 Référence CVE CVE-2026-23058 https://www.cve.org/CVERecord?id=CVE-2026-23058 Référence CVE CVE-2026-23060 https://www.cve.org/CVERecord?id=CVE-2026-23060 Référence CVE CVE-2026-23061 https://www.cve.org/CVERecord?id=CVE-2026-23061 Référence CVE CVE-2026-23063 https://www.cve.org/CVERecord?id=CVE-2026-23063 Référence CVE CVE-2026-23064 https://www.cve.org/CVERecord?id=CVE-2026-23064 Référence CVE CVE-2026-23071 https://www.cve.org/CVERecord?id=CVE-2026-23071 Référence CVE CVE-2026-23073 https://www.cve.org/CVERecord?id=CVE-2026-23073 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23075 https://www.cve.org/CVERecord?id=CVE-2026-23075 Référence CVE CVE-2026-23076 https://www.cve.org/CVERecord?id=CVE-2026-23076 Référence CVE CVE-2026-23078 https://www.cve.org/CVERecord?id=CVE-2026-23078 Référence CVE CVE-2026-23080 https://www.cve.org/CVERecord?id=CVE-2026-23080 Référence CVE CVE-2026-23083 https://www.cve.org/CVERecord?id=CVE-2026-23083 Référence CVE CVE-2026-23084 https://www.cve.org/CVERecord?id=CVE-2026-23084 Référence CVE CVE-2026-23085 https://www.cve.org/CVERecord?id=CVE-2026-23085 Référence CVE CVE-2026-23087 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-2026-23049 Référence CVE CVE-2026-23056 https://www.cve.org/CVERecord?id=CVE-2026-23056 Référence CVE CVE-2026-23058 https://www.cve.org/CVERecord?id=CVE-2026-23058 Référence CVE CVE-2026-23060 https://www.cve.org/CVERecord?id=CVE-2026-23060 Référence CVE CVE-2026-23061 https://www.cve.org/CVERecord?id=CVE-2026-23061 Référence CVE CVE-2026-23063 https://www.cve.org/CVERecord?id=CVE-2026-23063 Référence CVE CVE-2026-23064 https://www.cve.org/CVERecord?id=CVE-2026-23064 Référence CVE CVE-2026-23071 https://www.cve.org/CVERecord?id=CVE-2026-23071 Référence CVE CVE-2026-23073 https://www.cve.org/CVERecord?id=CVE-2026-23073 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23075 https://www.cve.org/CVERecord?id=CVE-2026-23075 Référence CVE CVE-2026-23076 https://www.cve.org/CVERecord?id=CVE-2026-23076 Référence CVE CVE-2026-23078 https://www.cve.org/CVERecord?id=CVE-2026-23078 Référence CVE CVE-2026-23080 https://www.cve.org/CVERecord?id=CVE-2026-23080 Référence CVE CVE-2026-23083 https://www.cve.org/CVERecord?id=CVE-2026-23083 Référence CVE CVE-2026-23084 https://www.cve.org/CVERecord?id=CVE-2026-23084 Référence CVE CVE-2026-23085 https://www.cve.org/CVERecord?id=CVE-2026-23085 Référence CVE CVE-2026-23087 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

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

d?id=CVE-2026-23049 Référence CVE CVE-2026-23056 https://www.cve.org/CVERecord?id=CVE-2026-23056 Référence CVE CVE-2026-23058 https://www.cve.org/CVERecord?id=CVE-2026-23058 Référence CVE CVE-2026-23060 https://www.cve.org/CVERecord?id=CVE-2026-23060 Référence CVE CVE-2026-23061 https://www.cve.org/CVERecord?id=CVE-2026-23061 Référence CVE CVE-2026-23063 https://www.cve.org/CVERecord?id=CVE-2026-23063 Référence CVE CVE-2026-23064 https://www.cve.org/CVERecord?id=CVE-2026-23064 Référence CVE CVE-2026-23071 https://www.cve.org/CVERecord?id=CVE-2026-23071 Référence CVE CVE-2026-23073 https://www.cve.org/CVERecord?id=CVE-2026-23073 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23075 https://www.cve.org/CVERecord?id=CVE-2026-23075 Référence CVE CVE-2026-23076 https://www.cve.org/CVERecord?id=CVE-2026-23076 Référence CVE CVE-2026-23078 https://www.cve.org/CVERecord?id=CVE-2026-23078 Référence CVE CVE-2026-23080 https://www.cve.org/CVERecord?id=CVE-2026-23080 Référence CVE CVE-2026-23083 https://www.cve.org/CVERecord?id=CVE-2026-23083 Référence CVE CVE-2026-23084 https://www.cve.org/CVERecord?id=CVE-2026-23084 Référence CVE CVE-2026-23085 https://www.cve.org/CVERecord?id=CVE-2026-23085 Référence CVE CVE-2026-23087 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68813 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-2025-71066 Référence CVE CVE-2025-71085 https://www.cve.org/CVERecord?id=CVE-2025-71085 Référence CVE CVE-2025-71112 https://www.cve.org/CVERecord?id=CVE-2025-71112 Référence CVE CVE-2026-22999 https://www.cve.org/CVERecord?id=CVE-2026-22999 Référence CVE CVE-2026-23001 https://www.cve.org/CVERecord?id=CVE-2026-23001 Référence CVE CVE-2026-23004 https://www.cve.org/CVERecord?id=CVE-2026-23004 Référence CVE CVE-2026-23054 https://www.cve.org/CVERecord?id=CVE-2026-23054 Référence CVE CVE-2026-23060 https://www.cve.org/CVERecord?id=CVE-2026-23060 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23089 https://www.cve.org/CVERecord?id=CVE-2026-23089 Référence CVE CVE-2026-23191 https://www.cve.org/CVERecord?id=CVE-2026-23191 Référence CVE CVE-2026-23204 https://www.cve.org/CVERecord?id=CVE-2026-23204 Référence CVE CVE-2026-23209 https://www.cve.org/CVERecord?id=CVE-2026-23209 Référence CVE CVE-2026-23268 https://www.cve.org/CVERecord?id=CVE-2026-23268 Référence CVE CVE-2026-23269 https://www.cve.org/CVERecord?id=CVE-2026-23269 Gestion détaillée du document le 03 avril 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À

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

d?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-23019 https://www.cve.org/CVERecord?id=CVE-2026-23019 Référence CVE CVE-2026-23020 https://www.cve.org/CVERecord?id=CVE-2026-23020 Référence CVE CVE-2026-23021 https://www.cve.org/CVERecord?id=CVE-2026-23021 Référence CVE CVE-2026-23047 https://www.cve.org/CVERecord?id=CVE-2026-23047 Référence CVE CVE-2026-23060 https://www.cve.org/CVERecord?id=CVE-2026-23060 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 Référence CVE CVE-2026-23268 https://www.cve.org/CVERecord?id=CVE-2026-23268 Référence CVE CVE-2026-23269 https://www.cve.org/CVERecord?id=CVE-2026-23269 Gestion détaillée du document le 03 avril 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 s

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

Record?id=CVE-2025-8194 Référence CVE CVE-2025-8869 https://www.cve.org/CVERecord?id=CVE-2025-8869 Référence CVE CVE-2026-1188 https://www.cve.org/CVERecord?id=CVE-2026-1188 Référence CVE CVE-2026-21860 https://www.cve.org/CVERecord?id=CVE-2026-21860 Référence CVE CVE-2026-21925 https://www.cve.org/CVERecord?id=CVE-2026-21925 Référence CVE CVE-2026-21932 https://www.cve.org/CVERecord?id=CVE-2026-21932 Référence CVE CVE-2026-21933 https://www.cve.org/CVERecord?id=CVE-2026-21933 Référence CVE CVE-2026-21945 https://www.cve.org/CVERecord?id=CVE-2026-21945 Référence CVE CVE-2026-23001 https://www.cve.org/CVERecord?id=CVE-2026-23001 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23097 https://www.cve.org/CVERecord?id=CVE-2026-23097 Référence CVE CVE-2026-26007 https://www.cve.org/CVERecord?id=CVE-2026-26007 Référence CVE CVE-2026-27199 https://www.cve.org/CVERecord?id=CVE-2026-27199 Référence CVE CVE-2026-27205 https://www.cve.org/CVERecord?id=CVE-2026-27205 Gestion détaillée du document le 03 avril 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 l

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

d?id=CVE-2026-23062 Référence CVE CVE-2026-23063 https://www.cve.org/CVERecord?id=CVE-2026-23063 Référence CVE CVE-2026-23064 https://www.cve.org/CVERecord?id=CVE-2026-23064 Référence CVE CVE-2026-23065 https://www.cve.org/CVERecord?id=CVE-2026-23065 Référence CVE CVE-2026-23068 https://www.cve.org/CVERecord?id=CVE-2026-23068 Référence CVE CVE-2026-23069 https://www.cve.org/CVERecord?id=CVE-2026-23069 Référence CVE CVE-2026-23070 https://www.cve.org/CVERecord?id=CVE-2026-23070 Référence CVE CVE-2026-23071 https://www.cve.org/CVERecord?id=CVE-2026-23071 Référence CVE CVE-2026-23073 https://www.cve.org/CVERecord?id=CVE-2026-23073 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23076 https://www.cve.org/CVERecord?id=CVE-2026-23076 Référence CVE CVE-2026-23078 https://www.cve.org/CVERecord?id=CVE-2026-23078 Référence CVE CVE-2026-23080 https://www.cve.org/CVERecord?id=CVE-2026-23080 Référence CVE CVE-2026-23082 https://www.cve.org/CVERecord?id=CVE-2026-23082 Référence CVE CVE-2026-23083 https://www.cve.org/CVERecord?id=CVE-2026-23083 Référence CVE CVE-2026-23084 https://www.cve.org/CVERecord?id=CVE-2026-23084 Référence CVE CVE-2026-23085 https://www.cve.org/CVERecord?id=CVE-2026-23085 Référence CVE CVE-2026-23086 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23057 Référence CVE CVE-2026-23058 https://www.cve.org/CVERecord?id=CVE-2026-23058 Référence CVE CVE-2026-23060 https://www.cve.org/CVERecord?id=CVE-2026-23060 Référence CVE CVE-2026-23061 https://www.cve.org/CVERecord?id=CVE-2026-23061 Référence CVE CVE-2026-23063 https://www.cve.org/CVERecord?id=CVE-2026-23063 Référence CVE CVE-2026-23064 https://www.cve.org/CVERecord?id=CVE-2026-23064 Référence CVE CVE-2026-23068 https://www.cve.org/CVERecord?id=CVE-2026-23068 Référence CVE CVE-2026-23071 https://www.cve.org/CVERecord?id=CVE-2026-23071 Référence CVE CVE-2026-23073 https://www.cve.org/CVERecord?id=CVE-2026-23073 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23076 https://www.cve.org/CVERecord?id=CVE-2026-23076 Référence CVE CVE-2026-23078 https://www.cve.org/CVERecord?id=CVE-2026-23078 Référence CVE CVE-2026-23080 https://www.cve.org/CVERecord?id=CVE-2026-23080 Référence CVE CVE-2026-23082 https://www.cve.org/CVERecord?id=CVE-2026-23082 Référence CVE CVE-2026-23083 https://www.cve.org/CVERecord?id=CVE-2026-23083 Référence CVE CVE-2026-23084 https://www.cve.org/CVERecord?id=CVE-2026-23084 Référence CVE CVE-2026-23085 https://www.cve.org/CVERecord?id=CVE-2026-23085 Référence CVE CVE-2026-23086 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-2026-23060 Référence CVE CVE-2026-23061 https://www.cve.org/CVERecord?id=CVE-2026-23061 Référence CVE CVE-2026-23063 https://www.cve.org/CVERecord?id=CVE-2026-23063 Référence CVE CVE-2026-23064 https://www.cve.org/CVERecord?id=CVE-2026-23064 Référence CVE CVE-2026-23066 https://www.cve.org/CVERecord?id=CVE-2026-23066 Référence CVE CVE-2026-23068 https://www.cve.org/CVERecord?id=CVE-2026-23068 Référence CVE CVE-2026-23069 https://www.cve.org/CVERecord?id=CVE-2026-23069 Référence CVE CVE-2026-23071 https://www.cve.org/CVERecord?id=CVE-2026-23071 Référence CVE CVE-2026-23073 https://www.cve.org/CVERecord?id=CVE-2026-23073 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23075 https://www.cve.org/CVERecord?id=CVE-2026-23075 Référence CVE CVE-2026-23076 https://www.cve.org/CVERecord?id=CVE-2026-23076 Référence CVE CVE-2026-23078 https://www.cve.org/CVERecord?id=CVE-2026-23078 Référence CVE CVE-2026-23080 https://www.cve.org/CVERecord?id=CVE-2026-23080 Référence CVE CVE-2026-23083 https://www.cve.org/CVERecord?id=CVE-2026-23083 Référence CVE CVE-2026-23084 https://www.cve.org/CVERecord?id=CVE-2026-23084 Référence CVE CVE-2026-23085 https://www.cve.org/CVERecord?id=CVE-2026-23085 Référence CVE CVE-2026-23086 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-2026-23060 Référence CVE CVE-2026-23061 https://www.cve.org/CVERecord?id=CVE-2026-23061 Référence CVE CVE-2026-23063 https://www.cve.org/CVERecord?id=CVE-2026-23063 Référence CVE CVE-2026-23064 https://www.cve.org/CVERecord?id=CVE-2026-23064 Référence CVE CVE-2026-23066 https://www.cve.org/CVERecord?id=CVE-2026-23066 Référence CVE CVE-2026-23068 https://www.cve.org/CVERecord?id=CVE-2026-23068 Référence CVE CVE-2026-23069 https://www.cve.org/CVERecord?id=CVE-2026-23069 Référence CVE CVE-2026-23071 https://www.cve.org/CVERecord?id=CVE-2026-23071 Référence CVE CVE-2026-23073 https://www.cve.org/CVERecord?id=CVE-2026-23073 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23075 https://www.cve.org/CVERecord?id=CVE-2026-23075 Référence CVE CVE-2026-23076 https://www.cve.org/CVERecord?id=CVE-2026-23076 Référence CVE CVE-2026-23078 https://www.cve.org/CVERecord?id=CVE-2026-23078 Référence CVE CVE-2026-23080 https://www.cve.org/CVERecord?id=CVE-2026-23080 Référence CVE CVE-2026-23083 https://www.cve.org/CVERecord?id=CVE-2026-23083 Référence CVE CVE-2026-23084 https://www.cve.org/CVERecord?id=CVE-2026-23084 Référence CVE CVE-2026-23085 https://www.cve.org/CVERecord?id=CVE-2026-23085 Référence CVE CVE-2026-23086 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Elles permettent à un attaquant de provoquer un déni de service à distance, un contournement de la politique de sécurité et un problème de sécurité non spécifié par l'éditeur.

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

d?id=CVE-2025-40064 Référence CVE CVE-2025-40096 https://www.cve.org/CVERecord?id=CVE-2025-40096 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-40269 https://www.cve.org/CVERecord?id=CVE-2025-40269 Référence CVE CVE-2025-40271 https://www.cve.org/CVERecord?id=CVE-2025-40271 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40322 https://www.cve.org/CVERecord?id=CVE-2025-40322 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Gestion détaillée du document le 27 février 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-0225Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-22996 Référence CVE CVE-2026-22997 https://www.cve.org/CVERecord?id=CVE-2026-22997 Référence CVE CVE-2026-22999 https://www.cve.org/CVERecord?id=CVE-2026-22999 Référence CVE CVE-2026-23000 https://www.cve.org/CVERecord?id=CVE-2026-23000 Référence CVE CVE-2026-23001 https://www.cve.org/CVERecord?id=CVE-2026-23001 Référence CVE CVE-2026-23005 https://www.cve.org/CVERecord?id=CVE-2026-23005 Référence CVE CVE-2026-23006 https://www.cve.org/CVERecord?id=CVE-2026-23006 Référence CVE CVE-2026-23010 https://www.cve.org/CVERecord?id=CVE-2026-23010 Référence CVE CVE-2026-23011 https://www.cve.org/CVERecord?id=CVE-2026-23011 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23089 https://www.cve.org/CVERecord?id=CVE-2026-23089 Gestion détaillée du document le 27 février 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-0167Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-23058 Référence CVE CVE-2026-23060 https://www.cve.org/CVERecord?id=CVE-2026-23060 Référence CVE CVE-2026-23061 https://www.cve.org/CVERecord?id=CVE-2026-23061 Référence CVE CVE-2026-23063 https://www.cve.org/CVERecord?id=CVE-2026-23063 Référence CVE CVE-2026-23064 https://www.cve.org/CVERecord?id=CVE-2026-23064 Référence CVE CVE-2026-23068 https://www.cve.org/CVERecord?id=CVE-2026-23068 Référence CVE CVE-2026-23069 https://www.cve.org/CVERecord?id=CVE-2026-23069 Référence CVE CVE-2026-23071 https://www.cve.org/CVERecord?id=CVE-2026-23071 Référence CVE CVE-2026-23073 https://www.cve.org/CVERecord?id=CVE-2026-23073 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23075 https://www.cve.org/CVERecord?id=CVE-2026-23075 Référence CVE CVE-2026-23076 https://www.cve.org/CVERecord?id=CVE-2026-23076 Référence CVE CVE-2026-23078 https://www.cve.org/CVERecord?id=CVE-2026-23078 Référence CVE CVE-2026-23080 https://www.cve.org/CVERecord?id=CVE-2026-23080 Référence CVE CVE-2026-23083 https://www.cve.org/CVERecord?id=CVE-2026-23083 Référence CVE CVE-2026-23084 https://www.cve.org/CVERecord?id=CVE-2026-23084 Référence CVE CVE-2026-23085 https://www.cve.org/CVERecord?id=CVE-2026-23085 Référence CVE CVE-2026-23086 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-2026-23062 Référence CVE CVE-2026-23063 https://www.cve.org/CVERecord?id=CVE-2026-23063 Référence CVE CVE-2026-23064 https://www.cve.org/CVERecord?id=CVE-2026-23064 Référence CVE CVE-2026-23065 https://www.cve.org/CVERecord?id=CVE-2026-23065 Référence CVE CVE-2026-23068 https://www.cve.org/CVERecord?id=CVE-2026-23068 Référence CVE CVE-2026-23069 https://www.cve.org/CVERecord?id=CVE-2026-23069 Référence CVE CVE-2026-23071 https://www.cve.org/CVERecord?id=CVE-2026-23071 Référence CVE CVE-2026-23072 https://www.cve.org/CVERecord?id=CVE-2026-23072 Référence CVE CVE-2026-23073 https://www.cve.org/CVERecord?id=CVE-2026-23073 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23075 https://www.cve.org/CVERecord?id=CVE-2026-23075 Référence CVE CVE-2026-23076 https://www.cve.org/CVERecord?id=CVE-2026-23076 Référence CVE CVE-2026-23078 https://www.cve.org/CVERecord?id=CVE-2026-23078 Référence CVE CVE-2026-23080 https://www.cve.org/CVERecord?id=CVE-2026-23080 Référence CVE CVE-2026-23083 https://www.cve.org/CVERecord?id=CVE-2026-23083 Référence CVE CVE-2026-23084 https://www.cve.org/CVERecord?id=CVE-2026-23084 Référence CVE CVE-2026-23085 https://www.cve.org/CVERecord?id=CVE-2026-23085 Référence CVE CVE-2026-23086 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-008037LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました：net/schedにおいて、teqlはルートqdiscとしてのみ使用可能であることが強制されます。teqlの設計意図はルートqdiscとしてのみ使用されることであり、その制約をチェックする必要があります。重要度は高くありませんが、この問題を発見したシナリオを好奇心のある方のために説明します。GangMin Kim km.kim1503@gmail.com は以下のシナリオを作成しました。ルートqdisc 1:0 (QFQ) ├── クラス 1:1 (weight=15, lmax=16384) netem（遅延6.4秒） └── クラス 1:2 (weight=1, lmax=1514) teqlです。GangMinはパケットを送信し、それは1:1（netem）にエンクィューされます。QFQがこのクラスからdequeueを呼び出しても、6.4秒経過するまでパケットを返しません。その間に2つ目のパケットが送信され1:2に入ります。teqlのenqueueは成功を返し、それによってクラス1:2がアクティブになります。主な問題は、teqlが親の可視キュー長（sch-q.qlen）をdequeue時にのみ更新することにあります。QFQはpeekが成功したときにのみdequeueを呼び出します（teqlのpeekは常にNULLを返すため）、dequeueは呼び出されずqlenは常に0のままです。これにより、GangMinが1:2のlmax値を更新すると、qfq_change_classがqfq_deact_rm_from_aggを呼び出します。子qdiscのqlenが増加していなかったため、qfqはクラスの非アクティブ化に失敗しますが、それでもアグリゲートからのポインタは解放されます。したがって、最初のパケットが6.4秒後（netemの遅延後）に再スケジュールされる際に、不正なポインタがアクセスされ、GangMinにUAF（Use-After-Free）を引き起こします。

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
Linux: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 16ed73c1282d376b956bff23e5139add061767ba, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 4c7e8aa71c9232cba84c289b4b56cba80b280841, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 73d970ff0eddd874a84c953387c7f4464b705fc6, patch: 5.10.249, patch: 5.15.199, 2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ae810e6a8ac4fe25042e6825d2a401207a2e41fb, patch: 0, patch: 6.18.8, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < dad49a67c2d817bfec98e6e45121b351e3a0202c, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0686bedfed34155520f3f735cbf3210cb9044380, patch: 6.1.162, patch: 6.6.122, patch: 6.19, patch: 6.12.68, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 50da4b9d07a7a463e2cfb738f3ad4cff6b2c9c3b
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 4 Feb 2026 · Last source change 17 Sept 2026, 12:04 UTC · CWE-825 · Expired Pointer Dereference

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-5470
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceOther authority
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
    1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 73d970ff0eddd874a84c953387c7f4464b705fc6; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ae810e6a8ac4fe25042e6825d2a401207a2e41fb; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < dad49a67c2d817bfec98e6e45121b351e3a0202c; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0686bedfed34155520f3f735cbf3210cb9044380; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 4c7e8aa71c9232cba84c289b4b56cba80b280841; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 16ed73c1282d376b956bff23e5139add061767ba; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 50da4b9d07a7a463e2cfb738f3ad4cff6b2c9c3b; 2.6.12 · Fixed: < 2.6.12; 5.10.249 ≤ 5.10.*; 5.15.199 ≤ 5.15.*; 6.1.162 ≤ 6.1.*; 6.6.122 ≤ 6.6.*; 6.12.68 ≤ 6.12.*; 6.18.8 ≤ 6.18.*; 6.19 ≤ *
    After
    Linux: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 73d970ff0eddd874a84c953387c7f4464b705fc6, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ae810e6a8ac4fe25042e6825d2a401207a2e41fb, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < dad49a67c2d817bfec98e6e45121b351e3a0202c, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0686bedfed34155520f3f735cbf3210cb9044380, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 4c7e8aa71c9232cba84c289b4b56cba80b280841, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 16ed73c1282d376b956bff23e5139add061767ba, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 50da4b9d07a7a463e2cfb738f3ad4cff6b2c9c3b, 2.6.12 · Fixed: Linux: < 2.6.12, 5.10.249 ≤ 5.10.*, 5.15.199 ≤ 5.15.*, 6.1.162 ≤ 6.1.*, 6.6.122 ≤ 6.6.*, 6.12.68 ≤ 6.12.*, 6.18.8 ≤ 6.18.*, 6.19 ≤ *
    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-5470↗Vendor CSAF · Red Hat Product Security↗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-23074 · cve.blacktree.nl