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

netfilter: ctnetlink: ensure safe access to master conntrack

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.10% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.14-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.14-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-43116 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2026-43116
318 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: ensure safe access to master conntrack Holding reference on the expectation is not sufficient, the master conntrack object can just go away, making exp->master invalid. To access exp->master safely: - Grab the nf_conntrack_expect_lock, this gets serialized with clean_from_lists() which also holds this lock when the master conntrack goes away. - Hold reference on master conntrack via nf_conntrack_find_get(). Not so easy since the master tuple to look up for the master conntrack is not available in the existing problematic paths. This patch goes for extending the nf_conntrack_expect_lock section to address this issue for simplicity, in the cases that are described below this is just slightly extending the lock section. The add expectation command already holds a reference to the master conntrack from ctnetlink_create_expect(). However, the delete expectation command needs to grab the spinlock before looking up for the expectation. Expand the existing spinlock section to address this to cover the expectation lookup. Note that, the nf_ct_expect_iterate_net() calls already grabs the spinlock while iterating over the expectation table, which is correct. The get expectation command needs to grab the spinlock to ensure master conntrack does not go away. This also expands the existing spinlock section to cover the expectation lookup too. I needed to move the netlink skb allocation out of the spinlock to keep it GFP_KERNEL. For the expectation events, the IPEXP_DESTROY event is already delivered under the spinlock, just move the delivery of IPEXP_NEW under the spinlock too because the master conntrack event cache is reached through exp->master. While at it, add lockdep notations to help identify what codepaths need to grab the spinlock.
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: ctnetlink: ensure safe access to master conntrack Holding reference on the expectation is not sufficient, the master conntrack object can just go away, making exp->master invalid. To access exp->master safely: - Grab the nf_conntrack_expect_lock, this gets serialized with clean_from_lists() which also holds this lock when the master conntrack goes away. - Hold reference on master conntrack via nf_conntrack_find_get(). Not so easy since the master tuple to look up for the master conntrack is not available in the existing problematic paths. This patch goes for extending the nf_conntrack_expect_lock section to address this issue for simplicity, in the cases that are described below this is just slightly extending the lock section. The add expectation command already holds a reference to the master conntrack from ctnetlink_create_expect(). However, the delete expectation command needs to grab the spinlock before looking up for the expectation. Expand the existing spinlock section to address this to cover the expectation lookup. Note that, the nf_ct_expect_iterate_net() calls already grabs the spinlock while iterating over the expectation table, which is correct. The get expectation command needs to grab the spinlock to ensure master conntrack does not go away. This also expands the existing spinlock section to cover the expectation lookup too. I needed to move the netlink skb allocation out of the spinlock to keep it GFP_KERNEL. For the expectation events, the IPEXP_DESTROY event is already delivered under the spinlock, just move the delivery of IPEXP_NEW under the spinlock too because the master conntrack event cache is reached through exp->master. While at it, add lockdep notations to help identify what codepaths need to grab the spinlock.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
CVE-2026-43116 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: netfilter: ctnetlink: ensure safe access to master conntrack
47 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the `netfilter: ctnetlink` component of the Linux kernel. This vulnerability occurs due to insufficient locking when accessing the master conntrack object, allowing it to become invalid while still being referenced. A local attacker could potentially exploit this race condition, leading to a system crash and a denial of service.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-27641

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: ensure safe access to master conntrack Holding reference on the expectation is not sufficient, the master conntrack object can just go away, making exp->master invalid. To access exp->master safely: - Grab the nf_conntrack_expect_lock, this gets serialized with clean_from_lists() which also holds this lock when the master conntrack goes away. - Hold reference on master conntrack via nf_conntrack_find_get(). Not so easy since the master tuple to look up for the master conntrack is not available in the existing problematic paths. This patch goes for extending the nf_conntrack_expect_lock section to address this issue for simplicity, in the cases that are described below this is just slightly extending the lock section. The add expectation command already holds a reference to the master conntrack from ctnetlink_create_expect(). However, the delete expectation command needs to grab the spinlock before looking up for the expectation. Expand the existing spinlock section to address this to cover the expectation lookup. Note that, the nf_ct_expect_iterate_net() calls already grabs the spinlock while iterating over the expectation table, which is correct. The get expectation command needs to grab the spinlock to ensure master conntrack does not go away. This also expands the existing spinlock section to cover the expectation lookup too. I needed to move the netlink skb allocation out of the spinlock to keep it GFP_KERNEL. For the expectation events, the IPEXP_DESTROY event is already delivered under the spinlock, just move the delivery of IPEXP_NEW under the spinlock too because the master conntrack event cache is reached through exp->master. While at it, add lockdep notations to help identify what codepaths need to grab the spinlock.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: ensure safe access to master conntrack Holding reference on the expectation is not sufficient, the master conntrack object can just go away, making exp->master invalid. To access exp->master safely: - Grab the nf_conntrack_expect_lock, this gets serialized with clean_from_lists() which also holds this lock when the master conntrack goes away. - Hold reference on master conntrack via nf_conntrack_find_get(). Not so easy since the master tuple to look up for the master conntrack is not available in the existing problematic paths. This patch goes for extending the nf_conntrack_expect_lock section to address this issue for simplicity, in the cases that are described below this is just slightly extending the lock section. The add expectation command already holds a reference to the master conntrack from ctnetlink_create_expect(). However, the delete expectation command needs to grab the spinlock before looking up for the expectation. Expand the existing spinlock section to address this to cover the expectation lookup. Note that, the nf_ct_expect_iterate_net() calls already grabs the spinlock while iterating over the expectation table, which is correct. The get expectation command needs to grab the spinlock to ensure master conntrack does not go away. This also expands the existing spinlock section to cover the expectation lookup too. I needed to move the netlink skb allocation out of the spinlock to keep it GFP_KERNEL. For the expectation events, the IPEXP_DESTROY event is already delivered under the spinlock, just move the delivery of IPEXP_NEW under the spinlock too because the master conntrack event cache is reached through exp->master. While at it, add lockdep notations to help identify what codepaths need to grab the spinlock.

What

In the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: ensure safe access to master conntrack Holding reference on the expectation is not sufficient, the master conntrack object can just go away, making exp->master invalid. To access exp->master safely: - Grab the nf_conntrack_expect_lock, this gets serialized with clean_from_lists() which also holds this lock when the master conntrack goes away. - Hold reference on master conntrack via nf_conntrack_find_get(). Not so easy since the master tuple to look up for the master conntrack is not available in the existing problematic paths. This patch goes for extending the nf_conntrack_expect_lock section to address this issue for simplicity, in the cases that are described below this is just slightly extending the lock section. The add expectation command already holds a reference to the master conntrack from ctnetlink_create_expect(). However, the delete expectation command needs to grab the spinlock before looking up for the expectation. Expand the existing spinlock section to address this to cover the expectation lookup. Note that, the nf_ct_expect_iterate_net() calls already grabs the spinlock while iterating over the expectation table, which is correct. The get expectation command needs to grab the spinlock to ensure master conntrack does not go away. This also expands the existing spinlock section to cover the expectation lookup too. I needed to move the netlink skb allocation out of the spinlock to keep it GFP_KERNEL. For the expectation events, the IPEXP_DESTROY event is already delivered under the spinlock, just move the delivery of IPEXP_NEW under the spinlock too because the master conntrack event cache is reached through exp->master. While at it, add lockdep notations to help identify what codepaths need to grab the spinlock.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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: ctnetlink: ensure safe access to master conntrack Holding reference on the expectation is not sufficient, the master conntrack object can just go away, making exp->master invalid. To access exp->master safely: - Grab the nf_conntrack_expect_lock, this gets serialized with clean_from_lists() which also holds this lock when the master conntrack goes away. - Hold reference on master conntrack via nf_conntrack_find_get(). Not so easy since the master tuple to look up for the master conntrack is not available in the existing problematic paths. This patch goes for extending the nf_conntrack_expect_lock section to address this issue for simplicity, in the cases that are described below this is just slightly extending the lock section. The add expectation command already holds a reference to the master conntrack from ctnetlink_create_expect(). However, the delete expectation command needs to grab the spinlock before looking up for the expectation. Expand the existing spinlock section to address this to cover the expectation lookup. Note that, the nf_ct_expect_iterate_net() calls already grabs the spinlock while iterating over the expectation table, which is correct. The get expectation command needs to grab the spinlock to ensure master conntrack does not go away. This also expands the existing spinlock section to cover the expectation lookup too. I needed to move the netlink skb allocation out of the spinlock to keep it GFP_KERNEL. For the expectation events, the IPEXP_DESTROY event is already delivered under the spinlock, just move the delivery of IPEXP_NEW under the spinlock too because the master conntrack event cache is reached through exp->master. While at it, add lockdep notations to help identify what codepaths need to grab the spinlock.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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 → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → 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-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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

Official authority intelligence

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

ENISA EUVD · EUVD-2026-27641Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: ensure safe access to master conntrack Holding reference on the expectation is not sufficient, the master conntrack object can just go away, making exp->master invalid. To access exp->master safely: - Grab the nf_conntrack_expect_lock, this gets serialized with clean_from_lists() which also holds this lock when the master conntrack goes away. - Hold reference on master conntrack via nf_conntrack_find_get(). Not so easy since the master tuple to look up for the master conntrack is not available in the existing problematic paths. This patch goes for extending the nf_conntrack_expect_lock section to address this issue for simplicity, in the cases that are described below this is just slightly extending the lock section. The add expectation command already holds a reference to the master conntrack from ctnetlink_create_expect(). However, the delete expectation command needs to grab the spinlock before looking up for the expectation. Expand the existing spinlock section to address this to cover the expectation lookup. Note that, the nf_ct_expect_iterate_net() calls already grabs the spinlock while iterating over the expectation table, which is correct. The get expectation command needs to grab the spinlock to ensure master conntrack does not go away. This also expands the existing spinlock section to cover the expectation lookup too. I needed to move the netlink skb allocation out of the spinlock to keep it GFP_KERNEL. For the expectation events, the IPEXP_DESTROY event is already delivered under the spinlock, just move the delivery of IPEXP_NEW under the spinlock too because the master conntrack event cache is reached through exp->master. While at it, add lockdep notations to help identify what codepaths need to grab the spinlock.

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

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

Official advisory ↗
BSI · German · WID-SEC-2026-3043IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um beliebigen Programmcode auszuführen.

Official advisory ↗
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-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-68358 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-71075 https://www.cve.org/CVERecord?id=CVE-2025-71075 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23306 https://www.cve.org/CVERecord?id=CVE-2026-23306 Référence CVE CVE-2026-23348 https://www.cve.org/CVERecord?id=CVE-2026-23348 Référence CVE CVE-2026-31418 https://www.cve.org/CVERecord?id=CVE-2026-31418 Référence CVE CVE-2026-31530 https://www.cve.org/CVERecord?id=CVE-2026-31530 Référence CVE CVE-2026-31531 https://www.cve.org/CVERecord?id=CVE-2026-31531 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43239 https://www.cve.org/CVERecord?id=CVE-2026-43239 Référence CVE CVE-2026-43271 https://www.cve.org/CVERecord?id=CVE-2026-43271 Référence CVE CVE-2026-43299 https://www.cve.org/CVERecord?id=CVE-2026-43299 Référence CVE CVE-2026-43331 https://www.cve.org/CVERecord?id=CVE-2026-43331 Référence CVE CVE-2026-43355 https://www.cve.org/CVERecord?id=CVE-2026-43355 Référence CVE CVE-2026-43363 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39964 Référence CVE CVE-2025-40022 https://www.cve.org/CVERecord?id=CVE-2025-40022 Référence CVE CVE-2025-40277 https://www.cve.org/CVERecord?id=CVE-2025-40277 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2026-23003 https://www.cve.org/CVERecord?id=CVE-2026-23003 Référence CVE CVE-2026-23443 https://www.cve.org/CVERecord?id=CVE-2026-23443 Référence CVE CVE-2026-23451 https://www.cve.org/CVERecord?id=CVE-2026-23451 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31502 https://www.cve.org/CVERecord?id=CVE-2026-31502 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43134 https://www.cve.org/CVERecord?id=CVE-2026-43134 Référence CVE CVE-2026-43257 https://www.cve.org/CVERecord?id=CVE-2026-43257 Référence CVE CVE-2026-43277 https://www.cve.org/CVERecord?id=CVE-2026-43277 Référence CVE CVE-2026-43363 https://www.cve.org/CVERecord?id=CVE-2026-43363 Référence CVE CVE-2026-43416 https://www.cve.org/CVERecord?id=CVE-2026-43416 Référence CVE CVE-2026-43456 https://www.cve.org/CVERecord?id=CVE-2026-43456 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31629 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 Référence CVE CVE-2026-31663 https://www.cve.org/CVERecord?id=CVE-2026-31663 Référence CVE CVE-2026-31759 https://www.cve.org/CVERecord?id=CVE-2026-31759 Référence CVE CVE-2026-43014 https://www.cve.org/CVERecord?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-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43109 https://www.cve.org/CVERecord?id=CVE-2026-43109 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-43213 https://www.cve.org/CVERecord?id=CVE-2026-43213 Référence CVE CVE-2026-43271 https://www.cve.org/CVERecord?id=CVE-2026-43271 Référence CVE CVE-2026-43273 https://www.cve.org/CVERecord?id=CVE-2026-43273 Référence CVE CVE-2026-43278 https://www.cve.org/CVERecord?id=CVE-2026-43278 Référence CVE CVE-2026-43319 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31663 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31771 https://www.cve.org/CVERecord?id=CVE-2026-31771 Référence CVE CVE-2026-43009 https://www.cve.org/CVERecord?id=CVE-2026-43009 Référence CVE CVE-2026-43029 https://www.cve.org/CVERecord?id=CVE-2026-43029 Référence CVE CVE-2026-43042 https://www.cve.org/CVERecord?id=CVE-2026-43042 Référence CVE CVE-2026-43048 https://www.cve.org/CVERecord?id=CVE-2026-43048 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43101 https://www.cve.org/CVERecord?id=CVE-2026-43101 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43126 https://www.cve.org/CVERecord?id=CVE-2026-43126 Référence CVE CVE-2026-43172 https://www.cve.org/CVERecord?id=CVE-2026-43172 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43213 https://www.cve.org/CVERecord?id=CVE-2026-43213 Référence CVE CVE-2026-43263 https://www.cve.org/CVERecord?id=CVE-2026-43263 Référence CVE CVE-2026-43303 https://www.cve.org/CVERecord?id=CVE-2026-43303 Référence CVE CVE-2026-43352 https://www.cve.org/CVERecord?id=CVE-2026-43352 Référence CVE CVE-2026-43353 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31629 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 Référence CVE CVE-2026-31663 https://www.cve.org/CVERecord?id=CVE-2026-31663 Référence CVE CVE-2026-31759 https://www.cve.org/CVERecord?id=CVE-2026-31759 Référence CVE CVE-2026-43014 https://www.cve.org/CVERecord?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-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43109 https://www.cve.org/CVERecord?id=CVE-2026-43109 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-43213 https://www.cve.org/CVERecord?id=CVE-2026-43213 Référence CVE CVE-2026-43271 https://www.cve.org/CVERecord?id=CVE-2026-43271 Référence CVE CVE-2026-43273 https://www.cve.org/CVERecord?id=CVE-2026-43273 Référence CVE CVE-2026-43278 https://www.cve.org/CVERecord?id=CVE-2026-43278 Référence CVE CVE-2026-43319 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52924 Référence CVE CVE-2024-46744 https://www.cve.org/CVERecord?id=CVE-2024-46744 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2025-21834 https://www.cve.org/CVERecord?id=CVE-2025-21834 Référence CVE CVE-2025-68211 https://www.cve.org/CVERecord?id=CVE-2025-68211 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2026-23003 https://www.cve.org/CVERecord?id=CVE-2026-23003 Référence CVE CVE-2026-43023 https://www.cve.org/CVERecord?id=CVE-2026-43023 Référence CVE CVE-2026-43114 https://www.cve.org/CVERecord?id=CVE-2026-43114 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43454 https://www.cve.org/CVERecord?id=CVE-2026-43454 Référence CVE CVE-2026-45970 https://www.cve.org/CVERecord?id=CVE-2026-45970 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46099 https://www.cve.org/CVERecord?id=CVE-2026-46099 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46145 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-42198 Référence CVE CVE-2026-42253 https://www.cve.org/CVERecord?id=CVE-2026-42253 Référence CVE CVE-2026-42402 https://www.cve.org/CVERecord?id=CVE-2026-42402 Référence CVE CVE-2026-42403 https://www.cve.org/CVERecord?id=CVE-2026-42403 Référence CVE CVE-2026-42404 https://www.cve.org/CVERecord?id=CVE-2026-42404 Référence CVE CVE-2026-42561 https://www.cve.org/CVERecord?id=CVE-2026-42561 Référence CVE CVE-2026-42588 https://www.cve.org/CVERecord?id=CVE-2026-42588 Référence CVE CVE-2026-43056 https://www.cve.org/CVERecord?id=CVE-2026-43056 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43869 https://www.cve.org/CVERecord?id=CVE-2026-43869 Référence CVE CVE-2026-44240 https://www.cve.org/CVERecord?id=CVE-2026-44240 Référence CVE CVE-2026-4427 https://www.cve.org/CVERecord?id=CVE-2026-4427 Référence CVE CVE-2026-44288 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2025-10263 Référence CVE CVE-2025-40026 https://www.cve.org/CVERecord?id=CVE-2025-40026 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-68211 https://www.cve.org/CVERecord?id=CVE-2025-68211 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2026-23199 https://www.cve.org/CVERecord?id=CVE-2026-23199 Référence CVE CVE-2026-23415 https://www.cve.org/CVERecord?id=CVE-2026-23415 Référence CVE CVE-2026-31692 https://www.cve.org/CVERecord?id=CVE-2026-31692 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43186 https://www.cve.org/CVERecord?id=CVE-2026-43186 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-52923 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-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=CVE-2026-43110 Référence CVE CVE-2026-43111 https://www.cve.org/CVERecord?id=CVE-2026-43111 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43113 https://www.cve.org/CVERecord?id=CVE-2026-43113 Référence CVE CVE-2026-43114 https://www.cve.org/CVERecord?id=CVE-2026-43114 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43117 https://www.cve.org/CVERecord?id=CVE-2026-43117 Référence CVE CVE-2026-43216 https://www.cve.org/CVERecord?id=CVE-2026-43216 Référence CVE CVE-2026-43219 https://www.cve.org/CVERecord?id=CVE-2026-43219 Référence CVE CVE-2026-43281 https://www.cve.org/CVERecord?id=CVE-2026-43281 Référence CVE CVE-2026-43303 https://www.cve.org/CVERecord?id=CVE-2026-43303 Référence CVE CVE-2026-43350 https://www.cve.org/CVERecord?id=CVE-2026-43350 Référence CVE CVE-2026-43355 https://www.cve.org/CVERecord?id=CVE-2026-43355 Référence CVE CVE-2026-43421 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23346 Référence CVE CVE-2026-23394 https://www.cve.org/CVERecord?id=CVE-2026-23394 Référence CVE CVE-2026-23469 https://www.cve.org/CVERecord?id=CVE-2026-23469 Référence CVE CVE-2026-31420 https://www.cve.org/CVERecord?id=CVE-2026-31420 Référence CVE CVE-2026-31486 https://www.cve.org/CVERecord?id=CVE-2026-31486 Référence CVE CVE-2026-31560 https://www.cve.org/CVERecord?id=CVE-2026-31560 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=CVE-2026-31613 Référence CVE CVE-2026-31663 https://www.cve.org/CVERecord?id=CVE-2026-31663 Référence CVE CVE-2026-31717 https://www.cve.org/CVERecord?id=CVE-2026-31717 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43219 https://www.cve.org/CVERecord?id=CVE-2026-43219 Référence CVE CVE-2026-43245 https://www.cve.org/CVERecord?id=CVE-2026-43245 Référence CVE CVE-2026-43303 https://www.cve.org/CVERecord?id=CVE-2026-43303 Référence CVE CVE-2026-43331 https://www.cve.org/CVERecord?id=CVE-2026-43331 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31787 Référence CVE CVE-2026-35385 https://www.cve.org/CVERecord?id=CVE-2026-35385 Référence CVE CVE-2026-39979 https://www.cve.org/CVERecord?id=CVE-2026-39979 Référence CVE CVE-2026-40164 https://www.cve.org/CVERecord?id=CVE-2026-40164 Référence CVE CVE-2026-41035 https://www.cve.org/CVERecord?id=CVE-2026-41035 Référence CVE CVE-2026-41326 https://www.cve.org/CVERecord?id=CVE-2026-41326 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-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43303 https://www.cve.org/CVERecord?id=CVE-2026-43303 Référence CVE CVE-2026-43329 https://www.cve.org/CVERecord?id=CVE-2026-43329 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46125 https://www.cve.org/CVERecord?id=CVE-2026-46125 Référence CVE CVE-2026-46152 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31532 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31607 https://www.cve.org/CVERecord?id=CVE-2026-31607 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=CVE-2026-31613 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 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-43056 https://www.cve.org/CVERecord?id=CVE-2026-43056 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-46054 https://www.cve.org/CVERecord?id=CVE-2026-46054 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Gestion détaillée du document le 12 juin 2026 Version initiale

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014965LinuxのLinux Kernelにおける競合状態に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が解決されました。netfilterのctnetlinkに関連し、マスターconntrackへの安全なアクセスを保証することが重要です。期待オブジェクトへの参照を保持するだけでは不十分であり、マスターconntrackオブジェクトが消失してexp-masterが無効になる可能性があります。exp-masterに安全にアクセスするためには、nf_conntrack_expect_lockを取得する必要があります。このロックは、マスターconntrackが消失する際に同時に保持されるclean_from_lists()と整合しています。また、nf_conntrack_find_get()を用いてマスターconntrackへの参照を保持する必要がありますが、既存の問題のあるパスではマスターconntrackを検索するためのマスタータプルが利用できず、容易ではありません。今回のパッチでは問題を単純化するためにnf_conntrack_expect_lockの範囲を拡張し、以下で説明するケースではロック範囲を若干拡大する形にしています。期待オブジェクトの追加コマンドは、すでにctnetlink_create_expect()からマスターconntrackへの参照を保持しています。しかし、期待オブジェクトの削除コマンドでは探索の前にスピンロックを取得する必要があり、期待オブジェクトの探索をカバーするために既存のスピンロック範囲を拡大しています。なお、nf_ct_expect_iterate_net()は期待オブジェクトテーブルを反復中にすでにスピンロックを取得しており、これは正しい動作です。期待オブジェクトの取得コマンドは、マスターconntrackが消失しないようにスピンロックを取得し、探索をカバーするために既存のスピンロック範囲を拡大しています。GFP_KERNELを維持するために、netlink skbの割り当てはスピンロックの外に移動しました。期待イベントについては、IPEXP_DESTROYイベントはすでにスピンロック下で配信されているため、マスターconntrackのイベントキャッシュがexp-masterを通じてアクセスされます。そのため、IPEXP_NEWの配信もスピンロック下に移動しました。加えて、ロックデバッグを支援するためにロック依存性注釈を追加し、どのコードパスがスピンロックを取得する必要があるかを識別しやすくしています。

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.16, 6.1.176 ≤ 6.1.*, 6.6.143 ≤ 6.6.*, 6.12.94 ≤ 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-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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-27641
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
    c1d10adb4a521de5760112853f42aaeefcec96eb < 9e1196d27ef496f404c76f7a9d03761142d991c4; c1d10adb4a521de5760112853f42aaeefcec96eb < 5e1c1d22268ae710c238342c8030c21daf298168; c1d10adb4a521de5760112853f42aaeefcec96eb < d52fa1fa7440676b8c238037a050ab008c22737f; c1d10adb4a521de5760112853f42aaeefcec96eb < f338ced0473849c9f6ed0b77ca99f1aab5826787; c1d10adb4a521de5760112853f42aaeefcec96eb < 497f99b26fffdc5635706d1b4811f1ed8ee21a5b; c1d10adb4a521de5760112853f42aaeefcec96eb < bffcaad9afdfe45d7fc777397d3b83c1e3ebffe5; 2.6.16 · Fixed: < 2.6.16; 6.1.176 ≤ 6.1.*; 6.6.143 ≤ 6.6.*; 6.12.94 ≤ 6.12.*; 6.18.24 ≤ 6.18.*; 6.19.14 ≤ 6.19.*; 7.0 ≤ *
    After
    Linux: c1d10adb4a521de5760112853f42aaeefcec96eb < 9e1196d27ef496f404c76f7a9d03761142d991c4, c1d10adb4a521de5760112853f42aaeefcec96eb < 5e1c1d22268ae710c238342c8030c21daf298168, c1d10adb4a521de5760112853f42aaeefcec96eb < d52fa1fa7440676b8c238037a050ab008c22737f, c1d10adb4a521de5760112853f42aaeefcec96eb < f338ced0473849c9f6ed0b77ca99f1aab5826787, c1d10adb4a521de5760112853f42aaeefcec96eb < 497f99b26fffdc5635706d1b4811f1ed8ee21a5b, c1d10adb4a521de5760112853f42aaeefcec96eb < bffcaad9afdfe45d7fc777397d3b83c1e3ebffe5, 2.6.16 · Fixed: Linux: < 2.6.16, 6.1.176 ≤ 6.1.*, 6.6.143 ≤ 6.6.*, 6.12.94 ≤ 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-27641↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor 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-43116 · cve.blacktree.nl