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

netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator

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 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published 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 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.85-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.14-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.14-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-43085 · CSAF 2.0 · revision 16 · interimSUSE Product Security TeamCVE-2026-43085
326 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator When batching multiple NFLOG messages (inst->qlen > 1), __nfulnl_send() appends an NLMSG_DONE terminator with sizeof(struct nfgenmsg) payload via nlmsg_put(), but never initializes the nfgenmsg bytes. The nlmsg_put() helper only zeroes alignment padding after the payload, not the payload itself, so four bytes of stale kernel heap data are leaked to userspace in the NLMSG_DONE message body. Use nfnl_msg_put() to build the NLMSG_DONE terminator, which initializes the nfgenmsg payload via nfnl_fill_hdr(), consistent with how __build_packet_message() already constructs NFULNL_MSG_PACKET headers.
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: netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator When batching multiple NFLOG messages (inst->qlen > 1), __nfulnl_send() appends an NLMSG_DONE terminator with sizeof(struct nfgenmsg) payload via nlmsg_put(), but never initializes the nfgenmsg bytes. The nlmsg_put() helper only zeroes alignment padding after the payload, not the payload itself, so four bytes of stale kernel heap data are leaked to userspace in the NLMSG_DONE message body. Use nfnl_msg_put() to build the NLMSG_DONE terminator, which initializes the nfgenmsg payload via nfnl_fill_hdr(), consistent with how __build_packet_message() already constructs NFULNL_MSG_PACKET headers.
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-27580

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator When batching multiple NFLOG messages (inst->qlen > 1), __nfulnl_send() appends an NLMSG_DONE terminator with sizeof(struct nfgenmsg) payload via nlmsg_put(), but never initializes the nfgenmsg bytes. The nlmsg_put() helper only zeroes alignment padding after the payload, not the payload itself, so four bytes of stale kernel heap data are leaked to userspace in the NLMSG_DONE message body. Use nfnl_msg_put() to build the NLMSG_DONE terminator, which initializes the nfgenmsg payload via nfnl_fill_hdr(), consistent with how __build_packet_message() already constructs NFULNL_MSG_PACKET headers.

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 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator When batching multiple NFLOG messages (inst->qlen > 1), __nfulnl_send() appends an NLMSG_DONE terminator with sizeof(struct nfgenmsg) payload via nlmsg_put(), but never initializes the nfgenmsg bytes. The nlmsg_put() helper only zeroes alignment padding after the payload, not the payload itself, so four bytes of stale kernel heap data are leaked to userspace in the NLMSG_DONE message body. Use nfnl_msg_put() to build the NLMSG_DONE terminator, which initializes the nfgenmsg payload via nfnl_fill_hdr(), consistent with how __build_packet_message() already constructs NFULNL_MSG_PACKET headers.

What

In the Linux kernel, the following vulnerability has been resolved: netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator When batching multiple NFLOG messages (inst->qlen > 1), __nfulnl_send() appends an NLMSG_DONE terminator with sizeof(struct nfgenmsg) payload via nlmsg_put(), but never initializes the nfgenmsg bytes. The nlmsg_put() helper only zeroes alignment padding after the payload, not the payload itself, so four bytes of stale kernel heap data are leaked to userspace in the NLMSG_DONE message body. Use nfnl_msg_put() to build the NLMSG_DONE terminator, which initializes the nfgenmsg payload via nfnl_fill_hdr(), consistent with how __build_packet_message() already constructs NFULNL_MSG_PACKET headers.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through 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: netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator When batching multiple NFLOG messages (inst->qlen > 1), __nfulnl_send() appends an NLMSG_DONE terminator with sizeof(struct nfgenmsg) payload via nlmsg_put(), but never initializes the nfgenmsg bytes. The nlmsg_put() helper only zeroes alignment padding after the payload, not the payload itself, so four bytes of stale kernel heap data are leaked to userspace in the NLMSG_DONE message body. Use nfnl_msg_put() to build the NLMSG_DONE terminator, which initializes the nfgenmsg payload via nfnl_fill_hdr(), consistent with how __build_packet_message() already constructs NFULNL_MSG_PACKET headers.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through 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 → vulnerable operation → 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.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV: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.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-27580Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator When batching multiple NFLOG messages (inst->qlen > 1), __nfulnl_send() appends an NLMSG_DONE terminator with sizeof(struct nfgenmsg) payload via nlmsg_put(), but never initializes the nfgenmsg bytes. The nlmsg_put() helper only zeroes alignment padding after the payload, not the payload itself, so four bytes of stale kernel heap data are leaked to userspace in the NLMSG_DONE message body. Use nfnl_msg_put() to build the NLMSG_DONE terminator, which initializes the nfgenmsg payload via nfnl_fill_hdr(), consistent with how __build_packet_message() already constructs NFULNL_MSG_PACKET headers.

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

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder potentiell beliebigen Programmcode auszuführen.

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

d?id=CVE-2026-43065 Référence CVE CVE-2026-43066 https://www.cve.org/CVERecord?id=CVE-2026-43066 Référence CVE CVE-2026-43068 https://www.cve.org/CVERecord?id=CVE-2026-43068 Référence CVE CVE-2026-43069 https://www.cve.org/CVERecord?id=CVE-2026-43069 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43075 https://www.cve.org/CVERecord?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43098 https://www.cve.org/CVERecord?id=CVE-2026-43098 Référence CVE CVE-2026-43099 https://www.cve.org/CVERecord?id=CVE-2026-43099 Référence CVE CVE-2026-43103 https://www.cve.org/CVERecord?id=CVE-2026-43103 Référence CVE CVE-2026-43104 https://www.cve.org/CVERecord?id=CVE-2026-43104 Référence CVE CVE-2026-43105 https://www.cve.org/CVERecord?id=CVE-2026-43105 Référence CVE CVE-2026-43110 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-43068 Référence CVE CVE-2026-43069 https://www.cve.org/CVERecord?id=CVE-2026-43069 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43075 https://www.cve.org/CVERecord?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43098 https://www.cve.org/CVERecord?id=CVE-2026-43098 Référence CVE CVE-2026-43099 https://www.cve.org/CVERecord?id=CVE-2026-43099 Référence CVE CVE-2026-43103 https://www.cve.org/CVERecord?id=CVE-2026-43103 Référence CVE CVE-2026-43104 https://www.cve.org/CVERecord?id=CVE-2026-43104 Référence CVE CVE-2026-43105 https://www.cve.org/CVERecord?id=CVE-2026-43105 Référence CVE CVE-2026-43110 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-43074 Référence CVE CVE-2026-43075 https://www.cve.org/CVERecord?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 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=CVE-2026-43081 Référence CVE CVE-2026-43082 https://www.cve.org/CVERecord?id=CVE-2026-43082 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43084 https://www.cve.org/CVERecord?id=CVE-2026-43084 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43086 https://www.cve.org/CVERecord?id=CVE-2026-43086 Référence CVE CVE-2026-43088 https://www.cve.org/CVERecord?id=CVE-2026-43088 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43091 https://www.cve.org/CVERecord?id=CVE-2026-43091 Référence CVE CVE-2026-43092 https://www.cve.org/CVERecord?id=CVE-2026-43092 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43098 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-43065 Référence CVE CVE-2026-43066 https://www.cve.org/CVERecord?id=CVE-2026-43066 Référence CVE CVE-2026-43068 https://www.cve.org/CVERecord?id=CVE-2026-43068 Référence CVE CVE-2026-43069 https://www.cve.org/CVERecord?id=CVE-2026-43069 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43075 https://www.cve.org/CVERecord?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43098 https://www.cve.org/CVERecord?id=CVE-2026-43098 Référence CVE CVE-2026-43099 https://www.cve.org/CVERecord?id=CVE-2026-43099 Référence CVE CVE-2026-43103 https://www.cve.org/CVERecord?id=CVE-2026-43103 Référence CVE CVE-2026-43104 https://www.cve.org/CVERecord?id=CVE-2026-43104 Référence CVE CVE-2026-43105 https://www.cve.org/CVERecord?id=CVE-2026-43105 Référence CVE CVE-2026-43110 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-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=CVE-2026-43081 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43086 https://www.cve.org/CVERecord?id=CVE-2026-43086 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43090 https://www.cve.org/CVERecord?id=CVE-2026-43090 Référence CVE CVE-2026-43092 https://www.cve.org/CVERecord?id=CVE-2026-43092 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43101 https://www.cve.org/CVERecord?id=CVE-2026-43101 Référence CVE CVE-2026-43107 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-43074 Référence CVE CVE-2026-43075 https://www.cve.org/CVERecord?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 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=CVE-2026-43081 Référence CVE CVE-2026-43082 https://www.cve.org/CVERecord?id=CVE-2026-43082 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43084 https://www.cve.org/CVERecord?id=CVE-2026-43084 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43086 https://www.cve.org/CVERecord?id=CVE-2026-43086 Référence CVE CVE-2026-43088 https://www.cve.org/CVERecord?id=CVE-2026-43088 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43091 https://www.cve.org/CVERecord?id=CVE-2026-43091 Référence CVE CVE-2026-43092 https://www.cve.org/CVERecord?id=CVE-2026-43092 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43098 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-43061 Référence CVE CVE-2026-43062 https://www.cve.org/CVERecord?id=CVE-2026-43062 Référence CVE CVE-2026-43064 https://www.cve.org/CVERecord?id=CVE-2026-43064 Référence CVE CVE-2026-43069 https://www.cve.org/CVERecord?id=CVE-2026-43069 Référence CVE CVE-2026-43072 https://www.cve.org/CVERecord?id=CVE-2026-43072 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=CVE-2026-43081 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43086 https://www.cve.org/CVERecord?id=CVE-2026-43086 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43090 https://www.cve.org/CVERecord?id=CVE-2026-43090 Référence CVE CVE-2026-43092 https://www.cve.org/CVERecord?id=CVE-2026-43092 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43098 https://www.cve.org/CVERecord?id=CVE-2026-43098 Référence CVE CVE-2026-43101 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-43074 Référence CVE CVE-2026-43075 https://www.cve.org/CVERecord?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 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=CVE-2026-43081 Référence CVE CVE-2026-43082 https://www.cve.org/CVERecord?id=CVE-2026-43082 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43084 https://www.cve.org/CVERecord?id=CVE-2026-43084 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43086 https://www.cve.org/CVERecord?id=CVE-2026-43086 Référence CVE CVE-2026-43088 https://www.cve.org/CVERecord?id=CVE-2026-43088 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43091 https://www.cve.org/CVERecord?id=CVE-2026-43091 Référence CVE CVE-2026-43092 https://www.cve.org/CVERecord?id=CVE-2026-43092 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43098 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43065 Référence CVE CVE-2026-43066 https://www.cve.org/CVERecord?id=CVE-2026-43066 Référence CVE CVE-2026-43068 https://www.cve.org/CVERecord?id=CVE-2026-43068 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 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=CVE-2026-43081 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43086 https://www.cve.org/CVERecord?id=CVE-2026-43086 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43101 https://www.cve.org/CVERecord?id=CVE-2026-43101 Référence CVE CVE-2026-43107 https://www.cve.org/CVERecord?id=CVE-2026-43107 Référence CVE CVE-2026-43109 https://www.cve.org/CVERecord?id=CVE-2026-43109 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43052 Référence CVE CVE-2026-43058 https://www.cve.org/CVERecord?id=CVE-2026-43058 Référence CVE CVE-2026-43064 https://www.cve.org/CVERecord?id=CVE-2026-43064 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43072 https://www.cve.org/CVERecord?id=CVE-2026-43072 Référence CVE CVE-2026-43075 https://www.cve.org/CVERecord?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43098 https://www.cve.org/CVERecord?id=CVE-2026-43098 Référence CVE CVE-2026-43099 https://www.cve.org/CVERecord?id=CVE-2026-43099 Référence CVE CVE-2026-43103 https://www.cve.org/CVERecord?id=CVE-2026-43103 Référence CVE CVE-2026-43104 https://www.cve.org/CVERecord?id=CVE-2026-43104 Référence CVE CVE-2026-43105 https://www.cve.org/CVERecord?id=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。netfilterのnfnetlink_logにおいて、NLMSG_DONE終端子でnfgenmsgを初期化する必要があります。複数のNFLOGメッセージをバッチ処理する際（inst-qlen 1）、__nfulnl_send()はnlmsg_put()を介してsizeof(struct nfgenmsg)分のペイロードを持つNLMSG_DONE終端子を追加しますが、nfgenmsgのバイトを初期化していません。nlmsg_put()ヘルパーはペイロード後のアラインメントパディングのみをゼロにしますが、ペイロード自体はゼロにしません。このため、NLMSG_DONEメッセージ本文にカーネルヒープの古いデータ4バイトがユーザースペースに漏洩してしまいます。この問題は、nfnl_msg_put()を使用してNLMSG_DONE終端子を構築し、nfnl_fill_hdr()経由でnfgenmsgペイロードを初期化することで修正されました。これは、__build_packet_message()がすでにNFULNL_MSG_PACKETヘッダーを構築している方法と一貫しています。

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: < 2.6.23, 5.10.258 ≤ 5.10.*, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.136 ≤ 6.6.*, 6.12.83 ≤ 6.12.*, 6.18.24 ≤ 6.18.*, 6.19.14 ≤ 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 6 May 2026 · Last source change 8 Sept 2026, 08:48 UTC · CWE not yet assigned

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-27580
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < 296f18e1c3a87c915a92ed27832d5040a22d1072; 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < 9e2182865de781c41ab16b7985e9d26dcefea867; 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < 57cc509d82b46150a11dcecc8b25eaa177eda34d; 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < 368c22aea490f6f50df831b4f9e3623787686c5b; 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < d1399632ba255d2e02c757af5d9f5d9279ce168c; 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < d552bcfca323d175664d7444989b04f55666978a; 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < 15d209bccf9273b4a8b4e579ba0e92d065b6ec8c; 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < 1f3083aec8836213da441270cdb1ab612dd82cf4 · Fixed: < 2.6.23; 5.10.258 ≤ 5.10.*; 5.15.209 ≤ 5.15.*; 6.1.175 ≤ 6.1.*; 6.6.136 ≤ 6.6.*; 6.12.83 ≤ 6.12.*; 6.18.24 ≤ 6.18.*; 6.19.14 ≤ 6.19.*
    After
    Linux: 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < 296f18e1c3a87c915a92ed27832d5040a22d1072, 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < 9e2182865de781c41ab16b7985e9d26dcefea867, 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < 57cc509d82b46150a11dcecc8b25eaa177eda34d, 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < 368c22aea490f6f50df831b4f9e3623787686c5b, 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < d1399632ba255d2e02c757af5d9f5d9279ce168c, 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < d552bcfca323d175664d7444989b04f55666978a, 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < 15d209bccf9273b4a8b4e579ba0e92d065b6ec8c, 29c5d4afba51c71cfeadd3f74f3c42e064483fb0 < 1f3083aec8836213da441270cdb1ab612dd82cf4, 2.6.23 · Fixed: Linux: < 2.6.23, 5.10.258 ≤ 5.10.*, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.136 ≤ 6.6.*, 6.12.83 ≤ 6.12.*, 6.18.24 ≤ 6.18.*, 6.19.14 ≤ 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-27580↗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-43085 · cve.blacktree.nl