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

net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 30 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 severityMediumOperational priority:Low, 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: No default targetRemediation target: Normal maintenance

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 30 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.85-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.12-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.

3 current
CVE-2026-43035 · CSAF 2.0 · revision 20 · interimSUSE Product Security TeamCVE-2026-43035
234 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak When building netlink messages, tc_chain_fill_node() never initializes the tcm_info field of struct tcmsg. Since the allocation is not zeroed, kernel heap memory is leaked to userspace through this 4-byte field. The fix simply zeroes tcm_info alongside the other fields that are already initialized.
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: net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak When building netlink messages, tc_chain_fill_node() never initializes the tcm_info field of struct tcmsg. Since the allocation is not zeroed, kernel heap memory is leaked to userspace through this 4-byte field. The fix simply zeroes tcm_info alongside the other fields that are already initialized.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-082556 · CSAF 2.0 · revision 7 · interimSiemens ProductCERTSSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5
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.5
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5
Summary
In the Linux kernel, the following vulnerability has been resolved: net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak When building netlink messages, tc_chain_fill_node() never initializes the tcm_info field of struct tcmsg. Since the allocation is not zeroed, kernel heap memory is leaked to userspace through this 4-byte field. The fix simply zeroes tcm_info alongside the other fields that are already initialized.
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-26634

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak When building netlink messages, tc_chain_fill_node() never initializes the tcm_info field of struct tcmsg. Since the allocation is not zeroed, kernel heap memory is leaked to userspace through this 4-byte field. The fix simply zeroes tcm_info alongside the other fields that are already initialized.

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
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 30 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: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak When building netlink messages, tc_chain_fill_node() never initializes the tcm_info field of struct tcmsg. Since the allocation is not zeroed, kernel heap memory is leaked to userspace through this 4-byte field. The fix simply zeroes tcm_info alongside the other fields that are already initialized.

What

In the Linux kernel, the following vulnerability has been resolved: net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak When building netlink messages, tc_chain_fill_node() never initializes the tcm_info field of struct tcmsg. Since the allocation is not zeroed, kernel heap memory is leaked to userspace through this 4-byte field. The fix simply zeroes tcm_info alongside the other fields that are already initialized.

Why

The product uses or accesses a resource that has not been initialized.

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: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak When building netlink messages, tc_chain_fill_node() never initializes the tcm_info field of struct tcmsg. Since the allocation is not zeroed, kernel heap memory is leaked to userspace through this 4-byte field. The fix simply zeroes tcm_info alongside the other fields that are already initialized.

Why

The product uses or accesses a resource that has not been initialized.

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 → Use of Uninitialized Resource → 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-908 ↗

CWE-908: Use of Uninitialized Resource. The product uses or accesses a resource that has not been initialized.

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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-908
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-26634Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak When building netlink messages, tc_chain_fill_node() never initializes the tcm_info field of struct tcmsg. Since the allocation is not zeroed, kernel heap memory is leaked to userspace through this 4-byte field. The fix simply zeroes tcm_info alongside the other fields that are already initialized.

Official EUVD record ↗
BSI · German · WID-SEC-2026-1346Linux Kernel: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Root-Rechte zu erlangen, um Sicherheitsmechanismen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder Auswirkungen unbestimmter Art zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260506Security Bulletin 06 May 2026

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

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

d?id=CVE-2026-43014 Référence CVE CVE-2026-43015 https://www.cve.org/CVERecord?id=CVE-2026-43015 Référence CVE CVE-2026-43020 https://www.cve.org/CVERecord?id=CVE-2026-43020 Référence CVE CVE-2026-43024 https://www.cve.org/CVERecord?id=CVE-2026-43024 Référence CVE CVE-2026-43026 https://www.cve.org/CVERecord?id=CVE-2026-43026 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43050 https://www.cve.org/CVERecord?id=CVE-2026-43050 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=CVE-2026-43051 Référence CVE CVE-2026-43052 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43014 Référence CVE CVE-2026-43015 https://www.cve.org/CVERecord?id=CVE-2026-43015 Référence CVE CVE-2026-43020 https://www.cve.org/CVERecord?id=CVE-2026-43020 Référence CVE CVE-2026-43024 https://www.cve.org/CVERecord?id=CVE-2026-43024 Référence CVE CVE-2026-43026 https://www.cve.org/CVERecord?id=CVE-2026-43026 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43050 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-43020 Référence CVE CVE-2026-43023 https://www.cve.org/CVERecord?id=CVE-2026-43023 Référence CVE CVE-2026-43024 https://www.cve.org/CVERecord?id=CVE-2026-43024 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43026 https://www.cve.org/CVERecord?id=CVE-2026-43026 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43044 https://www.cve.org/CVERecord?id=CVE-2026-43044 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43049 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43014 Référence CVE CVE-2026-43015 https://www.cve.org/CVERecord?id=CVE-2026-43015 Référence CVE CVE-2026-43020 https://www.cve.org/CVERecord?id=CVE-2026-43020 Référence CVE CVE-2026-43024 https://www.cve.org/CVERecord?id=CVE-2026-43024 Référence CVE CVE-2026-43026 https://www.cve.org/CVERecord?id=CVE-2026-43026 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43050 https://www.cve.org/CVERecord?id=CVE-2026-43050 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=CVE-2026-43051 Référence CVE CVE-2026-43052 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-43015 Référence CVE CVE-2026-43016 https://www.cve.org/CVERecord?id=CVE-2026-43016 Référence CVE CVE-2026-43019 https://www.cve.org/CVERecord?id=CVE-2026-43019 Référence CVE CVE-2026-43022 https://www.cve.org/CVERecord?id=CVE-2026-43022 Référence CVE CVE-2026-43024 https://www.cve.org/CVERecord?id=CVE-2026-43024 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43034 https://www.cve.org/CVERecord?id=CVE-2026-43034 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43053 https://www.cve.org/CVERecord?id=CVE-2026-43053 Référence CVE CVE-2026-43057 https://www.cve.org/CVERecord?id=CVE-2026-43057 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43081 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-43020 Référence CVE CVE-2026-43023 https://www.cve.org/CVERecord?id=CVE-2026-43023 Référence CVE CVE-2026-43024 https://www.cve.org/CVERecord?id=CVE-2026-43024 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43026 https://www.cve.org/CVERecord?id=CVE-2026-43026 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43044 https://www.cve.org/CVERecord?id=CVE-2026-43044 Référence CVE CVE-2026-43046 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-43019 Référence CVE CVE-2026-43020 https://www.cve.org/CVERecord?id=CVE-2026-43020 Référence CVE CVE-2026-43022 https://www.cve.org/CVERecord?id=CVE-2026-43022 Référence CVE CVE-2026-43024 https://www.cve.org/CVERecord?id=CVE-2026-43024 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43034 https://www.cve.org/CVERecord?id=CVE-2026-43034 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=CVE-2026-43051 Référence CVE CVE-2026-43053 https://www.cve.org/CVERecord?id=CVE-2026-43053 Référence CVE CVE-2026-43057 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-43020 Référence CVE CVE-2026-43023 https://www.cve.org/CVERecord?id=CVE-2026-43023 Référence CVE CVE-2026-43024 https://www.cve.org/CVERecord?id=CVE-2026-43024 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43026 https://www.cve.org/CVERecord?id=CVE-2026-43026 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43044 https://www.cve.org/CVERecord?id=CVE-2026-43044 Référence CVE CVE-2026-43046 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-31677 Référence CVE CVE-2026-31680 https://www.cve.org/CVERecord?id=CVE-2026-31680 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31758 https://www.cve.org/CVERecord?id=CVE-2026-31758 Référence CVE CVE-2026-31771 https://www.cve.org/CVERecord?id=CVE-2026-31771 Référence CVE CVE-2026-31773 https://www.cve.org/CVERecord?id=CVE-2026-31773 Référence CVE CVE-2026-31781 https://www.cve.org/CVERecord?id=CVE-2026-31781 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=CVE-2026-43051 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=

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

26-31495, CVE-2026-31496, CVE-2026-31503, CVE-2026-31504, CVE-2026-31507, CVE-2026-31508, CVE-2026-31515, CVE-2026-31518, CVE-2026-31521, CVE-2026-31533, CVE-2026-31546, CVE-2026-31555, CVE-2026-31563, CVE-2026-31565, CVE-2026-31628, CVE-2026-31634, CVE-2026-31649, CVE-2026-31651, CVE-2026-31658, CVE-2026-31664, CVE-2026-31665, CVE-2026-31669, CVE-2026-31670, CVE-2026-31671, CVE-2026-31674, CVE-2026-31680, CVE-2026-31682, CVE-2026-31737, CVE-2026-31752, CVE-2026-31761, CVE-2026-31768, CVE-2026-40355, CVE-2026-41989, CVE-2026-43011, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43033, CVE-2026-43035, CVE-2026-43038, CVE-2026-43040, CVE-2026-43057, CVE-2026-43284, CVE-2026-46174, CVE-2026-46300 et CVE-2026-46333. SIMATIC S7-PLCSIM Advanced toutes versions pour la vulnérabilité CVE-2026-54429 Résumé De multiples vulnérabilités ont été découvertes dans les produits Siemens. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une élévation de privilèges et un déni de service à distance. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Siemens SSA-019113 du 14 juillet 2026 https://ce

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

d?id=CVE-2026-43010 Référence CVE CVE-2026-43013 https://www.cve.org/CVERecord?id=CVE-2026-43013 Référence CVE CVE-2026-43022 https://www.cve.org/CVERecord?id=CVE-2026-43022 Référence CVE CVE-2026-43023 https://www.cve.org/CVERecord?id=CVE-2026-43023 Référence CVE CVE-2026-43024 https://www.cve.org/CVERecord?id=CVE-2026-43024 Référence CVE CVE-2026-43026 https://www.cve.org/CVERecord?id=CVE-2026-43026 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43034 https://www.cve.org/CVERecord?id=CVE-2026-43034 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43049 https://www.cve.org/CVERecord?id=CVE-2026-43049 Référence CVE CVE-2026-43052 https://www.cve.org/CVERecord?id=CVE-2026-43052 Référence CVE CVE-2026-43053 https://www.cve.org/CVERecord?id=CVE-2026-43053 Référence CVE CVE-2026-43054 https://www.cve.org/CVERecord?id=CVE-2026-43054 Référence CVE CVE-2026-43059 https://www.cve.org/CVERecord?id=CVE-2026-43059 Référence CVE CVE-2026-43065 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31759 Référence CVE CVE-2026-31767 https://www.cve.org/CVERecord?id=CVE-2026-31767 Référence CVE CVE-2026-31771 https://www.cve.org/CVERecord?id=CVE-2026-31771 Référence CVE CVE-2026-43013 https://www.cve.org/CVERecord?id=CVE-2026-43013 Référence CVE CVE-2026-43023 https://www.cve.org/CVERecord?id=CVE-2026-43023 Référence CVE CVE-2026-43024 https://www.cve.org/CVERecord?id=CVE-2026-43024 Référence CVE CVE-2026-43026 https://www.cve.org/CVERecord?id=CVE-2026-43026 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43049 https://www.cve.org/CVERecord?id=CVE-2026-43049 Référence CVE CVE-2026-43052 https://www.cve.org/CVERecord?id=CVE-2026-43052 Référence CVE CVE-2026-43053 https://www.cve.org/CVERecord?id=CVE-2026-43053 Référence CVE CVE-2026-43054 https://www.cve.org/CVERecord?id=CVE-2026-43054 Référence CVE CVE-2026-43059 https://www.cve.org/CVERecord?id=CVE-2026-43059 Référence CVE CVE-2026-43065 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43014 Référence CVE CVE-2026-43015 https://www.cve.org/CVERecord?id=CVE-2026-43015 Référence CVE CVE-2026-43020 https://www.cve.org/CVERecord?id=CVE-2026-43020 Référence CVE CVE-2026-43024 https://www.cve.org/CVERecord?id=CVE-2026-43024 Référence CVE CVE-2026-43026 https://www.cve.org/CVERecord?id=CVE-2026-43026 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43050 https://www.cve.org/CVERecord?id=CVE-2026-43050 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43023 Référence CVE CVE-2026-43024 https://www.cve.org/CVERecord?id=CVE-2026-43024 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43026 https://www.cve.org/CVERecord?id=CVE-2026-43026 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43050 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43023 Référence CVE CVE-2026-43024 https://www.cve.org/CVERecord?id=CVE-2026-43024 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43026 https://www.cve.org/CVERecord?id=CVE-2026-43026 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43032 https://www.cve.org/CVERecord?id=CVE-2026-43032 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43041 https://www.cve.org/CVERecord?id=CVE-2026-43041 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43046 https://www.cve.org/CVERecord?id=CVE-2026-43046 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43050 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014980LinuxのLinux Kernelにおける初期化されていないリソースの使用に関する脆弱性

Linuxカーネルにおいて、次の脆弱性が修正されました。net:sched:cls_apiのtc_chain_fill_node関数でtcm_infoをゼロ初期化し、情報漏洩を防止する問題です。netlinkメッセージを構築する際、tc_chain_fill_node()はstruct tcmsgのtcm_infoフィールドを初期化していませんでした。割り当てメモリはゼロクリアされていなかったため、この4バイトのフィールドを通じてカーネルヒープメモリがユーザースペースに漏洩していました。修正では、すでに初期化されている他のフィールドとともにtcm_infoもゼロクリアするようにしています。

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: < 4.19, 5.10.253 ≤ 5.10.*, 5.15.203 ≤ 5.15.*, 6.1.168 ≤ 6.1.*, 6.6.134 ≤ 6.6.*, 6.12.81 ≤ 6.12.*, 6.18.22 ≤ 6.18.*, 6.19.12 ≤ 6.19.*, 7.0 ≤ *
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 1 May 2026 · Last source change 8 Sept 2026, 08:48 UTC · CWE-908 · Use of Uninitialized Resource

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-26634
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
    32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < 903c3405cfcc7700260e456ab66a5867586c9e69; 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < 71a3eda7e850ae844cb8993065f4e410c11a46ce; 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < 4ae5d23f51fb91d7d1140c6f1ba77ab0756054c3; 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < e35f5195cd44ff4053fbc5d71ea97681728a0099; 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < d6db08484c6cb3d4ad696246f9d288eceba2a078; 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < 906997ea3766c24fbbf9cc4bf17c047315bbd138; 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < 1091b3c174441a52fdbb92e2fe00338f9371a91c; 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < e6e3eb5ee89ac4c163d46429391c889a1bb5e404 · Fixed: < 4.19; 5.10.253 ≤ 5.10.*; 5.15.203 ≤ 5.15.*; 6.1.168 ≤ 6.1.*; 6.6.134 ≤ 6.6.*; 6.12.81 ≤ 6.12.*; 6.18.22 ≤ 6.18.*; 6.19.12 ≤ 6.19.*
    After
    Linux: 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < 903c3405cfcc7700260e456ab66a5867586c9e69, 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < 71a3eda7e850ae844cb8993065f4e410c11a46ce, 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < 4ae5d23f51fb91d7d1140c6f1ba77ab0756054c3, 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < e35f5195cd44ff4053fbc5d71ea97681728a0099, 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < d6db08484c6cb3d4ad696246f9d288eceba2a078, 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < 906997ea3766c24fbbf9cc4bf17c047315bbd138, 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < 1091b3c174441a52fdbb92e2fe00338f9371a91c, 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e < e6e3eb5ee89ac4c163d46429391c889a1bb5e404, 4.19 · Fixed: Linux: < 4.19, 5.10.253 ≤ 5.10.*, 5.15.203 ≤ 5.15.*, 6.1.168 ≤ 6.1.*, 6.6.134 ≤ 6.6.*, 6.12.81 ≤ 6.12.*, 6.18.22 ≤ 6.18.*, 6.19.12 ≤ 6.19.*, 7.0 ≤ *
    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-26634↗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-43035 · cve.blacktree.nl