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

xfrm: esp: avoid in-place decrypt on shared skb frags

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 2.47% 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.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

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: Within 30 daysRemediation target: Within 180 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 30 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.86-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-3Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.4-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.

5 current
CVE-2026-43284 · CSAF 2.0 · revision 54 · interimSUSE Product Security TeamCVE-2026-43284
128 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
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid in-place decrypt on shared skb frags MSG_SPLICE_PAGES can attach pages from a pipe directly to an skb. TCP marks such skbs with SKBFL_SHARED_FRAG after skb_splice_from_iter(), so later paths that may modify packet data can first make a private copy. The IPv4/IPv6 datagram append paths did not set this flag when splicing pages into UDP skbs. That leaves an ESP-in-UDP packet made from shared pipe pages looking like an ordinary uncloned nonlinear skb. ESP input then takes the no-COW fast path for uncloned skbs without a frag_list and decrypts in place over data that is not owned privately by the skb. Mark IPv4/IPv6 datagram splice frags with SKBFL_SHARED_FRAG, matching TCP. Also make ESP input fall back to skb_cow_data() when the flag is present, so ESP does not decrypt externally backed frags in place. Private nonlinear skb frags still use the existing fast path. This intentionally does not change ESP output. In esp_output_head(), the path that appends the ESP trailer to existing skb tailroom without calling skb_cow_data() is not reachable for nonlinear skbs: skb_tailroom() returns zero when skb->data_len is nonzero, while ESP tailen is positive. Thus ESP output will either use the separate destination-frag path or fall back to skb_cow_data().
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.

  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6 < V3.1.7
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6 < V3.1.7
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6 < V3.1.7
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6 < V3.1.7
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6 < V3.1.7
Summary
In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid in-place decrypt on shared skb frags MSG_SPLICE_PAGES can attach pages from a pipe directly to an skb. TCP marks such skbs with SKBFL_SHARED_FRAG after skb_splice_from_iter(), so later paths that may modify packet data can first make a private copy. The IPv4/IPv6 datagram append paths did not set this flag when splicing pages into UDP skbs. That leaves an ESP-in-UDP packet made from shared pipe pages looking like an ordinary uncloned nonlinear skb. ESP input then takes the no-COW fast path for uncloned skbs without a frag_list and decrypts in place over data that is not owned privately by the skb. Mark IPv4/IPv6 datagram splice frags with SKBFL_SHARED_FRAG, matching TCP. Also make ESP input fall back to skb_cow_data() when the flag is present, so ESP does not decrypt externally backed frags in place. Private nonlinear skb frags still use the existing fast path. This intentionally does not change ESP output. In esp_output_head(), the path that appends the ESP trailer to existing skb tailroom without calling skb_cow_data() is not reachable for nonlinear skbs: skb_tailroom() returns zero when skb->data_len is nonzero, while ESP tailen is positive. Thus ESP output will either use the separate destination-frag path or fall back to skb_cow_data().
Remediation
Update to V3.1.7 or later version
CVE-2026-43284 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: "Dirty Frag" ESP XFRM variant is a new universal Local Privilege Escalation (LPE) vulnerability in the Linux kernel
1 known affected

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

  • openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
Summary
A flaw was found in the Linux kernel's xfrm-ESP and RxRPC subsystems. Unsafe in-place cryptographic processing of shared socket buffer fragments allows a low-privileged local attacker to corrupt page-cache contents of readable files, including sensitive system files, and gain root privileges. The xfrm-ESP variant requires unprivileged user or network namespace creation, while the RxRPC variant depends on the rxrpc module being available on the target system.
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.
SSA-082556 · CSAF 2.0 · revision 7 · interimSiemens ProductCERTSSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5
Summary
In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid in-place decrypt on shared skb frags MSG_SPLICE_PAGES can attach pages from a pipe directly to an skb. TCP marks such skbs with SKBFL_SHARED_FRAG after skb_splice_from_iter(), so later paths that may modify packet data can first make a private copy. The IPv4/IPv6 datagram append paths did not set this flag when splicing pages into UDP skbs. That leaves an ESP-in-UDP packet made from shared pipe pages looking like an ordinary uncloned nonlinear skb. ESP input then takes the no-COW fast path for uncloned skbs without a frag_list and decrypts in place over data that is not owned privately by the skb. Mark IPv4/IPv6 datagram splice frags with SKBFL_SHARED_FRAG, matching TCP. Also make ESP input fall back to skb_cow_data() when the flag is present, so ESP does not decrypt externally backed frags in place. Private nonlinear skb frags still use the existing fast path. This intentionally does not change ESP output. In esp_output_head(), the path that appends the ESP trailer to existing skb tailroom without calling skb_cow_data() is not reachable for nonlinear skbs: skb_tailroom() returns zero when skb->data_len is nonzero, while ESP tailen is positive. Thus ESP output will either use the separate destination-frag path or fall back to skb_cow_data().
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SA26P010 · CSAF 2.0 · revision 2 · finalABB Product Security Incident Response Team (PSIRT)CVE-2026-43284
3 known affected

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

  • B&R Industrial Automation GmbH Linux for B&R <=12
  • B&R Industrial Automation GmbH APROL <APROL-AutoYaST-DVD- V4.4-010.10.260602
  • B&R Industrial Automation GmbH X20EDS410 /all
Summary
In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid in-place decrypt on shared skb frags MSG_SPLICE_PAGES can attach pages from a pipe directly to an skb. TCP marks such skbs with SKBFL_SHARED_FRAG after skb_splice_from_iter(), so later paths that may modify packet data can first make a private copy. The IPv4/IPv6 datagram append paths did not set this flag when splicing pages into UDP skbs. That leaves an ESP-in-UDP packet made from shared pipe pages looking like an ordinary uncloned nonlinear skb. ESP input then takes the no-COW fast path for uncloned skbs without a frag_list and decrypts in place over data that is not owned privately by the skb. Mark IPv4/IPv6 datagram splice frags with SKBFL_SHARED_FRAG, matching TCP. Also make ESP input fall back to skb_cow_data() when the flag is present, so ESP does not decrypt external-ly backed frags in place. Private nonlinear skb frags still use the existing fast path. This intentionally does not change ESP output. In esp_output_head(), the path that appends the ESP trailer to existing skb tailroom without calling skb_cow_data() is not reachable for nonlinear skbs: skb_tailroom() returns zero when skb->data_len is nonzero, while ESP tailen is positive. Thus ESP output will either use the separate destination-frag path or fall back to skb_cow_data().
Remediation
For affected products, software updates should be installed upon availability. Product Patch version - APROL : APROL-AutoYaST-DVD- V4.4-010.10.260602 Until remediated software versions are available, customers are required to conduct a risk assessment of their affected systems and to implement the mitigation measures and workarounds specified in this advisory.
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-28535

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid in-place decrypt on shared skb frags MSG_SPLICE_PAGES can attach pages from a pipe directly to an skb. TCP marks such skbs with SKBFL_SHARED_FRAG after skb_splice_from_iter(), so later paths that may modify packet data can first make a private copy. The IPv4/IPv6 datagram append paths did not set this flag when splicing pages into UDP skbs. That leaves an ESP-in-UDP packet made from shared pipe pages looking like an ordinary uncloned nonlinear skb. ESP input then takes the no-COW fast path for uncloned skbs without a frag_list and decrypts in place over data that is not owned privately by the skb. Mark IPv4/IPv6 datagram splice frags with SKBFL_SHARED_FRAG, matching TCP. Also make ESP input fall back to skb_cow_data() when the flag is present, so ESP does not decrypt externally backed frags in place. Private nonlinear skb frags still use the existing fast path. This intentionally does not change ESP output. In esp_output_head(), the path that appends the ESP trailer to existing skb tailroom without calling skb_cow_data() is not reachable for nonlinear skbs: skb_tailroom() returns zero when skb->data_len is nonzero, while ESP tailen is positive. Thus ESP output will either use the separate destination-frag path or fall back to skb_cow_data().

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
8.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 with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 30 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid in-place decrypt on shared skb frags MSG_SPLICE_PAGES can attach pages from a pipe directly to an skb. TCP marks such skbs with SKBFL_SHARED_FRAG after skb_splice_from_iter(), so later paths that may modify packet data can first make a private copy. The IPv4/IPv6 datagram append paths did not set this flag when splicing pages into UDP skbs. That leaves an ESP-in-UDP packet made from shared pipe pages looking like an ordinary uncloned nonlinear skb. ESP input then takes the no-COW fast path for uncloned skbs without a frag_list and decrypts in place over data that is not owned privately by the skb. Mark IPv4/IPv6 datagram splice frags with SKBFL_SHARED_FRAG, matching TCP. Also make ESP input fall back to skb_cow_data() when the flag is present, so ESP does not decrypt externally backed frags in place. Private nonlinear skb frags still use the existing fast path. This intentionally does not change ESP output. In esp_output_head(), the path that appends the ESP trailer to existing skb tailroom without calling skb_cow_data() is not reachable for nonlinear skbs: skb_tailroom() returns zero when skb->data_len is nonzero, while ESP tailen is positive. Thus ESP output will either use the separate destination-frag path or fall back to skb_cow_data().

What

In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid in-place decrypt on shared skb frags MSG_SPLICE_PAGES can attach pages from a pipe directly to an skb. TCP marks such skbs with SKBFL_SHARED_FRAG after skb_splice_from_iter(), so later paths that may modify packet data can first make a private copy. The IPv4/IPv6 datagram append paths did not set this flag when splicing pages into UDP skbs. That leaves an ESP-in-UDP packet made from shared pipe pages looking like an ordinary uncloned nonlinear skb. ESP input then takes the no-COW fast path for uncloned skbs without a frag_list and decrypts in place over data that is not owned privately by the skb. Mark IPv4/IPv6 datagram splice frags with SKBFL_SHARED_FRAG, matching TCP. Also make ESP input fall back to skb_cow_data() when the flag is present, so ESP does not decrypt externally backed frags in place. Private nonlinear skb frags still use the existing fast path. This intentionally does not change ESP output. In esp_output_head(), the path that appends the ESP trailer to existing skb tailroom without calling skb_cow_data() is not reachable for nonlinear skbs: skb_tailroom() returns zero when skb->data_len is nonzero, while ESP tailen is positive. Thus ESP output will either use the separate destination-frag path or fall back to skb_cow_data().

Why

Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.

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: xfrm: esp: avoid in-place decrypt on shared skb frags MSG_SPLICE_PAGES can attach pages from a pipe directly to an skb. TCP marks such skbs with SKBFL_SHARED_FRAG after skb_splice_from_iter(), so later paths that may modify packet data can first make a private copy. The IPv4/IPv6 datagram append paths did not set this flag when splicing pages into UDP skbs. That leaves an ESP-in-UDP packet made from shared pipe pages looking like an ordinary uncloned nonlinear skb. ESP input then takes the no-COW fast path for uncloned skbs without a frag_list and decrypts in place over data that is not owned privately by the skb. Mark IPv4/IPv6 datagram splice frags with SKBFL_SHARED_FRAG, matching TCP. Also make ESP input fall back to skb_cow_data() when the flag is present, so ESP does not decrypt externally backed frags in place. Private nonlinear skb frags still use the existing fast path. This intentionally does not change ESP output. In esp_output_head(), the path that appends the ESP trailer to existing skb tailroom without calling skb_cow_data() is not reachable for nonlinear skbs: skb_tailroom() returns zero when skb->data_len is nonzero, while ESP tailen is positive. Thus ESP output will either use the separate destination-frag path or fall back to skb_cow_data().

Why

Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.

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.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
local access → Write-what-where 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
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-123 ↗

CWE-123: Write-what-where Condition. Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.

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:C/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.SChangedScope: The attack can affect a component governed by a different security 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-123Public exploit reference
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-28535Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid in-place decrypt on shared skb frags MSG_SPLICE_PAGES can attach pages from a pipe directly to an skb. TCP marks such skbs with SKBFL_SHARED_FRAG after skb_splice_from_iter(), so later paths that may modify packet data can first make a private copy. The IPv4/IPv6 datagram append paths did not set this flag when splicing pages into UDP skbs. That leaves an ESP-in-UDP packet made from shared pipe pages looking like an ordinary uncloned nonlinear skb. ESP input then takes the no-COW fast path for uncloned skbs without a frag_list and decrypts in place over data that is not owned privately by the skb. Mark IPv4/IPv6 datagram splice frags with SKBFL_SHARED_FRAG, matching TCP. Also make ESP input fall back to skb_cow_data() when the flag is present, so ESP does not decrypt externally backed frags in place. Private nonlinear skb frags still use the existing fast path. This intentionally does not change ESP output. In esp_output_head(), the path that appends the ESP trailer to existing skb tailroom without calling skb_cow_data() is not reachable for nonlinear skbs: skb_tailroom() returns zero when skb->data_len is nonzero, while ESP tailen is positive. Thus ESP output will either use the separate destination-frag path or fall back to skb_cow_data().

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-2437Oracle Communications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-1430Linux Kernel (Dirty Frag): Mehrere Schwachstellen ermöglichen Erlangen von Administratorrechten

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Administratorrechte zu erlangen.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV26-524Mitel security advisory (AV26-524)

On May 28, 2026, Mitel published a security advisory to address vulnerabilities in the following products:

Official advisory ↗
Canadian Centre for Cyber Security · English · AV26-509[Control Systems] Moxa security advisory (AV26-509)

On May 26, 2026, Moxa published a security advisory to address vulnerabilities in the following products:

Official advisory ↗
Canadian Centre for Cyber Security · English · AL26-011AL26-011 - Vulnerabilities affecting Linux - CVE-2026-43284 and CVE-2026-43500

An Alert is used to raise awareness of a recently identified cyber threat that may impact cyber information assets, and to provide additional detection and mitigation advice to recipients. The Canadian Centre for Cyber Security (Cyber Centre) is also available to provide additional assistance regarding the content of this Alert upon request.

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

d?id=CVE-2026-31682 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31705 https://www.cve.org/CVERecord?id=CVE-2026-31705 Référence CVE CVE-2026-43011 https://www.cve.org/CVERecord?id=CVE-2026-43011 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-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43197 https://www.cve.org/CVERecord?id=CVE-2026-43197 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43378 https://www.cve.org/CVERecord?id=CVE-2026-43378 Référence CVE CVE-2026-43379 https://www.cve.org/CVERecord?id=CVE-2026-43379 Référence CVE CVE-2026-43383 https://www.cve.org/CVERecord?id=CVE-2026-43383 Référence CVE CVE-2026-43407 https://www.cve.org/CVERecord?id=CVE-2026-43407 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43465 https://www.cve.org/CVERecord?id=CVE-2026-43465 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43499 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-43213 Référence CVE CVE-2026-43226 https://www.cve.org/CVERecord?id=CVE-2026-43226 Référence CVE CVE-2026-43233 https://www.cve.org/CVERecord?id=CVE-2026-43233 Référence CVE CVE-2026-43238 https://www.cve.org/CVERecord?id=CVE-2026-43238 Référence CVE CVE-2026-43240 https://www.cve.org/CVERecord?id=CVE-2026-43240 Référence CVE CVE-2026-43248 https://www.cve.org/CVERecord?id=CVE-2026-43248 Référence CVE CVE-2026-43253 https://www.cve.org/CVERecord?id=CVE-2026-43253 Référence CVE CVE-2026-43260 https://www.cve.org/CVERecord?id=CVE-2026-43260 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=CVE-2026-43283 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43294 https://www.cve.org/CVERecord?id=CVE-2026-43294 Référence CVE CVE-2026-43298 https://www.cve.org/CVERecord?id=CVE-2026-43298 Référence CVE CVE-2026-43303 https://www.cve.org/CVERecord?id=CVE-2026-43303 Référence CVE CVE-2026-43304 https://www.cve.org/CVERecord?id=CVE-2026-43304 Référence CVE CVE-2026-43320 https://www.cve.org/CVERecord?id=CVE-2026-43320 Référence CVE CVE-2026-43336 https://www.cve.org/CVERecord?id=CVE-2026-43336 Référence CVE CVE-2026-43337 https://www.cve.org/CVERecord?id=CVE-2026-43337 Référence CVE CVE-2026-43339 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-43270 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-43275 https://www.cve.org/CVERecord?id=CVE-2026-43275 Référence CVE CVE-2026-43277 https://www.cve.org/CVERecord?id=CVE-2026-43277 Référence CVE CVE-2026-43278 https://www.cve.org/CVERecord?id=CVE-2026-43278 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43281 https://www.cve.org/CVERecord?id=CVE-2026-43281 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=CVE-2026-43283 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43287 https://www.cve.org/CVERecord?id=CVE-2026-43287 Référence CVE CVE-2026-43288 https://www.cve.org/CVERecord?id=CVE-2026-43288 Référence CVE CVE-2026-43289 https://www.cve.org/CVERecord?id=CVE-2026-43289 Référence CVE CVE-2026-43291 https://www.cve.org/CVERecord?id=CVE-2026-43291 Référence CVE CVE-2026-43295 https://www.cve.org/CVERecord?id=CVE-2026-43295 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43297 https://www.cve.org/CVERecord?id=CVE-2026-43297 Référence CVE CVE-2026-43300 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-43257 Référence CVE CVE-2026-43260 https://www.cve.org/CVERecord?id=CVE-2026-43260 Référence CVE CVE-2026-43264 https://www.cve.org/CVERecord?id=CVE-2026-43264 Référence CVE CVE-2026-43269 https://www.cve.org/CVERecord?id=CVE-2026-43269 Référence CVE CVE-2026-43270 https://www.cve.org/CVERecord?id=CVE-2026-43270 Référence CVE CVE-2026-43277 https://www.cve.org/CVERecord?id=CVE-2026-43277 Référence CVE CVE-2026-43278 https://www.cve.org/CVERecord?id=CVE-2026-43278 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=CVE-2026-43283 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43287 https://www.cve.org/CVERecord?id=CVE-2026-43287 Référence CVE CVE-2026-43291 https://www.cve.org/CVERecord?id=CVE-2026-43291 Référence CVE CVE-2026-43294 https://www.cve.org/CVERecord?id=CVE-2026-43294 Référence CVE CVE-2026-43295 https://www.cve.org/CVERecord?id=CVE-2026-43295 Référence CVE CVE-2026-43298 https://www.cve.org/CVERecord?id=CVE-2026-43298 Référence CVE CVE-2026-43300 https://www.cve.org/CVERecord?id=CVE-2026-43300 Référence CVE CVE-2026-43302 https://www.cve.org/CVERecord?id=CVE-2026-43302 Référence CVE CVE-2026-43303 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-43268 Référence CVE CVE-2026-43269 https://www.cve.org/CVERecord?id=CVE-2026-43269 Référence CVE CVE-2026-43270 https://www.cve.org/CVERecord?id=CVE-2026-43270 Référence CVE CVE-2026-43273 https://www.cve.org/CVERecord?id=CVE-2026-43273 Référence CVE CVE-2026-43275 https://www.cve.org/CVERecord?id=CVE-2026-43275 Référence CVE CVE-2026-43277 https://www.cve.org/CVERecord?id=CVE-2026-43277 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43281 https://www.cve.org/CVERecord?id=CVE-2026-43281 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=CVE-2026-43283 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43287 https://www.cve.org/CVERecord?id=CVE-2026-43287 Référence CVE CVE-2026-43289 https://www.cve.org/CVERecord?id=CVE-2026-43289 Référence CVE CVE-2026-43291 https://www.cve.org/CVERecord?id=CVE-2026-43291 Référence CVE CVE-2026-43295 https://www.cve.org/CVERecord?id=CVE-2026-43295 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43302 https://www.cve.org/CVERecord?id=CVE-2026-43302 Référence CVE CVE-2026-43304 https://www.cve.org/CVERecord?id=CVE-2026-43304 Référence CVE CVE-2026-43312 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43093 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43117 https://www.cve.org/CVERecord?id=CVE-2026-43117 Référence CVE CVE-2026-43120 https://www.cve.org/CVERecord?id=CVE-2026-43120 Référence CVE CVE-2026-43139 https://www.cve.org/CVERecord?id=CVE-2026-43139 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43233 https://www.cve.org/CVERecord?id=CVE-2026-43233 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43336 https://www.cve.org/CVERecord?id=CVE-2026-43336 Référence CVE CVE-2026-43366 https://www.cve.org/CVERecord?id=CVE-2026-43366 Référence CVE CVE-2026-43437 https://www.cve.org/CVERecord?id=CVE-2026-43437 Référence CVE CVE-2026-43456 https://www.cve.org/CVERecord?id=CVE-2026-43456 Référence CVE CVE-2026-43472 https://www.cve.org/CVERecord?id=CVE-2026-43472 Référence CVE CVE-2026-43492 https://www.cve.org/CVERecord?id=CVE-2026-43492 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=

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

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

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

d?id=CVE-2026-43198 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-43233 https://www.cve.org/CVERecord?id=CVE-2026-43233 Référence CVE CVE-2026-43234 https://www.cve.org/CVERecord?id=CVE-2026-43234 Référence CVE CVE-2026-43238 https://www.cve.org/CVERecord?id=CVE-2026-43238 Référence CVE CVE-2026-43239 https://www.cve.org/CVERecord?id=CVE-2026-43239 Référence CVE CVE-2026-43249 https://www.cve.org/CVERecord?id=CVE-2026-43249 Référence CVE CVE-2026-43252 https://www.cve.org/CVERecord?id=CVE-2026-43252 Référence CVE CVE-2026-43261 https://www.cve.org/CVERecord?id=CVE-2026-43261 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43303 https://www.cve.org/CVERecord?id=CVE-2026-43303 Référence CVE CVE-2026-43325 https://www.cve.org/CVERecord?id=CVE-2026-43325 Référence CVE CVE-2026-43333 https://www.cve.org/CVERecord?id=CVE-2026-43333 Référence CVE CVE-2026-43336 https://www.cve.org/CVERecord?id=CVE-2026-43336 Référence CVE CVE-2026-43338 https://www.cve.org/CVERecord?id=CVE-2026-43338 Référence CVE CVE-2026-43339 https://www.cve.org/CVERecord?id=CVE-2026-43339 Référence CVE CVE-2026-43341 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43027 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43128 https://www.cve.org/CVERecord?id=CVE-2026-43128 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43276 https://www.cve.org/CVERecord?id=CVE-2026-43276 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43329 https://www.cve.org/CVERecord?id=CVE-2026-43329 Référence CVE CVE-2026-43341 https://www.cve.org/CVERecord?id=CVE-2026-43341 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43269 Référence CVE CVE-2026-43270 https://www.cve.org/CVERecord?id=CVE-2026-43270 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-43275 https://www.cve.org/CVERecord?id=CVE-2026-43275 Référence CVE CVE-2026-43277 https://www.cve.org/CVERecord?id=CVE-2026-43277 Référence CVE CVE-2026-43278 https://www.cve.org/CVERecord?id=CVE-2026-43278 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=CVE-2026-43283 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43287 https://www.cve.org/CVERecord?id=CVE-2026-43287 Référence CVE CVE-2026-43288 https://www.cve.org/CVERecord?id=CVE-2026-43288 Référence CVE CVE-2026-43289 https://www.cve.org/CVERecord?id=CVE-2026-43289 Référence CVE CVE-2026-43291 https://www.cve.org/CVERecord?id=CVE-2026-43291 Référence CVE CVE-2026-43295 https://www.cve.org/CVERecord?id=CVE-2026-43295 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43297 https://www.cve.org/CVERecord?id=CVE-2026-43297 Référence CVE CVE-2026-43300 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43171 Référence CVE CVE-2026-43187 https://www.cve.org/CVERecord?id=CVE-2026-43187 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-43234 https://www.cve.org/CVERecord?id=CVE-2026-43234 Référence CVE CVE-2026-43239 https://www.cve.org/CVERecord?id=CVE-2026-43239 Référence CVE CVE-2026-43249 https://www.cve.org/CVERecord?id=CVE-2026-43249 Référence CVE CVE-2026-43252 https://www.cve.org/CVERecord?id=CVE-2026-43252 Référence CVE CVE-2026-43261 https://www.cve.org/CVERecord?id=CVE-2026-43261 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43325 https://www.cve.org/CVERecord?id=CVE-2026-43325 Référence CVE CVE-2026-43333 https://www.cve.org/CVERecord?id=CVE-2026-43333 Référence CVE CVE-2026-43338 https://www.cve.org/CVERecord?id=CVE-2026-43338 Référence CVE CVE-2026-43339 https://www.cve.org/CVERecord?id=CVE-2026-43339 Référence CVE CVE-2026-43341 https://www.cve.org/CVERecord?id=CVE-2026-43341 Référence CVE CVE-2026-43345 https://www.cve.org/CVERecord?id=CVE-2026-43345 Référence CVE CVE-2026-43359 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-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-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43128 https://www.cve.org/CVERecord?id=CVE-2026-43128 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-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43329 https://www.cve.org/CVERecord?id=CVE-2026-43329 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43269 Référence CVE CVE-2026-43270 https://www.cve.org/CVERecord?id=CVE-2026-43270 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-43275 https://www.cve.org/CVERecord?id=CVE-2026-43275 Référence CVE CVE-2026-43277 https://www.cve.org/CVERecord?id=CVE-2026-43277 Référence CVE CVE-2026-43278 https://www.cve.org/CVERecord?id=CVE-2026-43278 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=CVE-2026-43283 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43287 https://www.cve.org/CVERecord?id=CVE-2026-43287 Référence CVE CVE-2026-43288 https://www.cve.org/CVERecord?id=CVE-2026-43288 Référence CVE CVE-2026-43289 https://www.cve.org/CVERecord?id=CVE-2026-43289 Référence CVE CVE-2026-43291 https://www.cve.org/CVERecord?id=CVE-2026-43291 Référence CVE CVE-2026-43295 https://www.cve.org/CVERecord?id=CVE-2026-43295 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43297 https://www.cve.org/CVERecord?id=CVE-2026-43297 Référence CVE CVE-2026-43300 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-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-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-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43260 https://www.cve.org/CVERecord?id=CVE-2026-43260 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43330 https://www.cve.org/CVERecord?id=CVE-2026-43330 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-45898 https://www.cve.org/CVERecord?id=CVE-2026-45898 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-46054 https://www.cve.org/CVERecord?id=CVE-2026-46054 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46117 https://www.cve.org/CVERecord?id=

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

tin de sécurité Ubuntu USN-8462-1 du 22 juin 2026 https://ubuntu.com/security/notices/USN-8462-1 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46000 https://www.cve.org/CVERecord?id=CVE-2026-46000 Référence CVE CVE-2026-46028 https://www.cve.org/CVERecord?id=CVE-2026-46028 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=

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

d?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-43150 https://www.cve.org/CVERecord?id=CVE-2026-43150 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-43234 https://www.cve.org/CVERecord?id=CVE-2026-43234 Référence CVE CVE-2026-43249 https://www.cve.org/CVERecord?id=CVE-2026-43249 Référence CVE CVE-2026-43252 https://www.cve.org/CVERecord?id=CVE-2026-43252 Référence CVE CVE-2026-43261 https://www.cve.org/CVERecord?id=CVE-2026-43261 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43325 https://www.cve.org/CVERecord?id=CVE-2026-43325 Référence CVE CVE-2026-43333 https://www.cve.org/CVERecord?id=CVE-2026-43333 Référence CVE CVE-2026-43338 https://www.cve.org/CVERecord?id=CVE-2026-43338 Référence CVE CVE-2026-43341 https://www.cve.org/CVERecord?id=CVE-2026-43341 Référence CVE CVE-2026-43359 https://www.cve.org/CVERecord?id=CVE-2026-43359 Référence CVE CVE-2026-43360 https://www.cve.org/CVERecord?id=CVE-2026-43360 Référence CVE CVE-2026-43361 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-41240 Référence CVE CVE-2026-41242 https://www.cve.org/CVERecord?id=CVE-2026-41242 Référence CVE CVE-2026-41305 https://www.cve.org/CVERecord?id=CVE-2026-41305 Référence CVE CVE-2026-41680 https://www.cve.org/CVERecord?id=CVE-2026-41680 Référence CVE CVE-2026-41907 https://www.cve.org/CVERecord?id=CVE-2026-41907 Référence CVE CVE-2026-41988 https://www.cve.org/CVERecord?id=CVE-2026-41988 Référence CVE CVE-2026-42502 https://www.cve.org/CVERecord?id=CVE-2026-42502 Référence CVE CVE-2026-42506 https://www.cve.org/CVERecord?id=CVE-2026-42506 Référence CVE CVE-2026-42583 https://www.cve.org/CVERecord?id=CVE-2026-42583 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-44288 https://www.cve.org/CVERecord?id=CVE-2026-44288 Référence CVE CVE-2026-44289 https://www.cve.org/CVERecord?id=CVE-2026-44289 Référence CVE CVE-2026-44290 https://www.cve.org/CVERecord?id=CVE-2026-44290 Référence CVE CVE-2026-44291 https://www.cve.org/CVERecord?id=CVE-2026-44291 Référence CVE CVE-2026-44292 https://www.cve.org/CVERecord?id=CVE-2026-44292 Référence CVE CVE-2026-44293 https://www.cve.org/CVERecord?id=CVE-2026-44293 Référence CVE CVE-2026-44294 https://www.cve.org/CVERecord?id=CVE-2026-44294 Référence CVE CVE-2026-45740 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23394 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-31676 https://www.cve.org/CVERecord?id=CVE-2026-31676 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43362 https://www.cve.org/CVERecord?id=CVE-2026-43362 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46000 https://www.cve.org/CVERecord?id=CVE-2026-46000 Référence CVE CVE-2026-46028 https://www.cve.org/CVERecord?id=CVE-2026-46028 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43184 Référence CVE CVE-2026-43187 https://www.cve.org/CVERecord?id=CVE-2026-43187 Référence CVE CVE-2026-43197 https://www.cve.org/CVERecord?id=CVE-2026-43197 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-43234 https://www.cve.org/CVERecord?id=CVE-2026-43234 Référence CVE CVE-2026-43249 https://www.cve.org/CVERecord?id=CVE-2026-43249 Référence CVE CVE-2026-43252 https://www.cve.org/CVERecord?id=CVE-2026-43252 Référence CVE CVE-2026-43261 https://www.cve.org/CVERecord?id=CVE-2026-43261 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43325 https://www.cve.org/CVERecord?id=CVE-2026-43325 Référence CVE CVE-2026-43328 https://www.cve.org/CVERecord?id=CVE-2026-43328 Référence CVE CVE-2026-43332 https://www.cve.org/CVERecord?id=CVE-2026-43332 Référence CVE CVE-2026-43333 https://www.cve.org/CVERecord?id=CVE-2026-43333 Référence CVE CVE-2026-43338 https://www.cve.org/CVERecord?id=CVE-2026-43338 Référence CVE CVE-2026-43339 https://www.cve.org/CVERecord?id=CVE-2026-43339 Référence CVE CVE-2026-43341 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23394 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-31676 https://www.cve.org/CVERecord?id=CVE-2026-31676 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-44917 https://www.cve.org/CVERecord?id=CVE-2026-44917 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46000 https://www.cve.org/CVERecord?id=CVE-2026-46000 Référence CVE CVE-2026-46028 https://www.cve.org/CVERecord?id=CVE-2026-46028 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43013 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43054 https://www.cve.org/CVERecord?id=CVE-2026-43054 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43126 https://www.cve.org/CVERecord?id=CVE-2026-43126 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-43234 https://www.cve.org/CVERecord?id=CVE-2026-43234 Référence CVE CVE-2026-43252 https://www.cve.org/CVERecord?id=CVE-2026-43252 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43325 https://www.cve.org/CVERecord?id=CVE-2026-43325 Référence CVE CVE-2026-43328 https://www.cve.org/CVERecord?id=CVE-2026-43328 Référence CVE CVE-2026-43333 https://www.cve.org/CVERecord?id=CVE-2026-43333 Référence CVE CVE-2026-43338 https://www.cve.org/CVERecord?id=CVE-2026-43338 Référence CVE CVE-2026-43341 https://www.cve.org/CVERecord?id=CVE-2026-43341 Référence CVE CVE-2026-43359 https://www.cve.org/CVERecord?id=CVE-2026-43359 Référence CVE CVE-2026-43360 https://www.cve.org/CVERecord?id=CVE-2026-43360 Référence CVE CVE-2026-43361 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23394 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-31676 https://www.cve.org/CVERecord?id=CVE-2026-31676 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45966 https://www.cve.org/CVERecord?id=CVE-2026-45966 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46000 https://www.cve.org/CVERecord?id=CVE-2026-46000 Référence CVE CVE-2026-46028 https://www.cve.org/CVERecord?id=CVE-2026-46028 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans les produits Mitel. Elles permettent à un attaquant de provoquer une élévation de privilèges.

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

d?id=CVE-2026-31738 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43088 https://www.cve.org/CVERecord?id=CVE-2026-43088 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43126 https://www.cve.org/CVERecord?id=CVE-2026-43126 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43255 https://www.cve.org/CVERecord?id=CVE-2026-43255 Référence CVE CVE-2026-43264 https://www.cve.org/CVERecord?id=CVE-2026-43264 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43334 https://www.cve.org/CVERecord?id=CVE-2026-43334 Référence CVE CVE-2026-43437 https://www.cve.org/CVERecord?id=CVE-2026-43437 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Gestion détaillée du document le 29 mai 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des sys

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une élévation de privilèges et une atteinte à la confidentialité des données.

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

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

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provoquer une élévation de privilèges, un déni de service à distance et une atteinte à la confidentialité des données.

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une élévation de privilèges et une atteinte à la confidentialité des données.

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

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

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0558Multiples vulnérabilités dans Microsoft Azure Linux

mai 2026 Bulletin de sécurité Microsoft CVE-2026-43191 du 07 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43195 du 07 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43201 du 07 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43228 du 07 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43237 du 07 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43243 du 07 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43267 du 07 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43274 du 07 mai 2026 Bulletin de sécurité Microsoft CVE-2025-71299 du 09 mai 2026 Bulletin de sécurité Microsoft CVE-2025-71302 du 09 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43284 du 09 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43292 du 09 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43300 du 09 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43305 du 09 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43306 du 09 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43320 du 09 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43321 du 09 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43398 du 09 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43400 du 09 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43474 du 09 mai 2026 Une gestion de version détaillée se trouve à la fin de ce document. Risque Non spécif

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014917LinuxのLinux Kernelにおける任意の場所に任意の値を書き込み可能な状態に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。xfrm: esp: 共有されたskbフラグメント上でのインプレース復号を回避します。MSG_SPLICE_PAGESはパイプから直接ページをskbに接続できます。TCPはskb_splice_from_iter()後にそのようなskbをSKBFL_SHARED_FRAGでマークし、パケットデータを変更する可能性のある後続の経路がまずプライベートコピーを作成できるようにします。しかし、IPv4/IPv6のデータグラム追加経路はUDP skbにページをスプライスする際にこのフラグを設定していませんでした。これにより、共有パイプページから作成されたESP-in-UDPパケットは、普通のクローンされていない非線形skbのように見えました。ESP入力はフラグメントリストのないクローンされていないskbに対してNo-COW高速パスを使い、skbがプライベートに所有していないデータ上にインプレースで復号します。IPv4/IPv6のデータグラムスプライスフラグメントにSKBFL_SHARED_FRAGをTCPに合わせてマークします。また、ESP入力はこのフラグが存在する場合skb_cow_data()にフォールバックし、ESPが外部でサポートされているフラグメント上でインプレース復号しないようにします。プライベートな非線形skbフラグメントは従来の高速パスを引き続き使用します。この変更はESP出力に意図的に影響を与えません。esp_output_head()内では、skb_cow_data()を呼ばず既存のskbテールルームにESPトレーラを追加する経路は非線形skbに対して到達不能です。skb_tailroom()はskb-data_lenが非ゼロの場合ゼロを返し、ESPのtailenは正であるためです。したがって、ESP出力は別の宛先フラグメントパスを使用するかskb_cow_data()にフォールバックします。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-016978Linuxカーネルにおける複数の脆弱性

CERT/CCから本件に関するアドバイザリが公表されました。 VU#980487: Local privilege escalation in Linux Kernel (Dirty Frag) VU#260001: Linux kernel contains local privilege escalation vulnerability (Copy Fail)

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6787Linux Kernel 보안 업데이트 권고

Linux Kernel에서 발생하는 Write-what-where Condition 취약점(CVE-2026-43284) [1]~[7][11]

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 4.11, 5.10.255 ≤ 5.10.*, 5.15.205 ≤ 5.15.*, 5.15.206 ≤ 5.15.*, 6.1.171 ≤ 6.1.*, 6.1.172 ≤ 6.1.*, 6.6.138 ≤ 6.6.*, 6.12.87 ≤ 6.12.*, 6.18.28 ≤ 6.18.*, 7.0.5 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
Official vendor articles1 stored document

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

  • PSIRT | FortiGuard Labs →Original publisher ↗Searchable text snapshot · Captured 29 Sep 2026PSIRT Linux Kernel vulnerability Dirty Frag Summary Linux kernel is impacted by CVE-2026-43284 and CVE-2026-43500 which chained together create the Dirty Frag vulnerability. CVE-2026-43284 In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid in-place decrypt on shared skb frags MSG_SPLIC
04

Evidence and provenance

Published 8 May 2026 · Last source change 8 Sept 2026, 08:48 UTC · CWE-123 · Write-what-where 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-28535
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
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. BlackTree coverageBlackTree article coverage changed from 1 BlackTree article to 2 BlackTree articles.
    Before
    1 BlackTree article
    After
    2 BlackTree articles
    BlackTree editorial ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from remediation: cert-portal.siemens.com/ssa-019113.html to remediation: cert-portal.siemens.com/ssa-019113.html.
    Before
    remediation: cert-portal.siemens.com/ssa-019113.html
    After
    remediation: cert-portal.siemens.com/ssa-019113.html
    Siemens ProductCERT ↗
  3. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Siemens ProductCERT ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    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
    After
    SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6 < V3.1.7; SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6 < V3.1.7; SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6 < V3.1.7; SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6 < V3.1.7; SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6 < V3.1.7
    Siemens ProductCERT ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    Fixed: kernel-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-211.7.el10nv.src as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-231.12.el10nv.src as a component of NVIDIA for RHEL 10; kernel-64k-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-core-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-core-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-core-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-core-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-debuginfo-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-debuginfo-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-core-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-core-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-extra-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-extra-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debuginfo-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debuginfo-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-core-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-core-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-extra-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-extra-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-abi-stablelists-0:6.12.0-211.7.el10nv.noarch as a component of NVIDIA for RHEL 10; kernel-abi-stablelists-0:6.12.0-231.12.el10nv.noarch as a component of NVIDIA for RHEL 10; and 3845 more
    After
    openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: kernel-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-211.7.el10nv.src as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-231.12.el10nv.src as a component of NVIDIA for RHEL 10; kernel-64k-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-core-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-core-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-core-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-core-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-debuginfo-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-debuginfo-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-core-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-core-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-extra-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-extra-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debuginfo-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debuginfo-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-core-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-core-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-extra-0:6.12.0-211.7.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-extra-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-abi-stablelists-0:6.12.0-211.7.el10nv.noarch as a component of NVIDIA for RHEL 10; kernel-abi-stablelists-0:6.12.0-231.12.el10nv.noarch as a component of NVIDIA for RHEL 10; and 3845 more
    Red Hat Product Security ↗
  6. BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.
    Before
    no BlackTree article
    After
    1 BlackTree article
    BlackTree editorial ↗
  7. Affected versionsThe structured affected or fixed version information changed.
    Before
    cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < a6cb440f274a22456ef3e86b457344f1678f38f9; cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < ab8b995323e5237041472d07e5055f5f7dcdf15b; cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < fe785bb3a8096dffcc4048a85cd0c83337eeecad; cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 5d55c7336f8032d434adcc5fab987ccc93a44aec; cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 8253aab4659ca16116b522203c2a6b18dccacea7; cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 50ed1e7873100f77abad20fd31c51029bc49cd03; cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < b54edf1e9a3fd3491bdcb82a21f8d21315271e0d; cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 71a1d9d985d26716f74d21f18ee8cac821b06e97 · Fixed: < 4.11; 5.10.255 ≤ 5.10.*; 5.15.205 ≤ 5.15.*; 5.15.206 ≤ 5.15.*; 6.1.171 ≤ 6.1.*; 6.1.172 ≤ 6.1.*; 6.6.138 ≤ 6.6.*; 6.12.87 ≤ 6.12.*
    After
    Linux: cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < a6cb440f274a22456ef3e86b457344f1678f38f9, cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < ab8b995323e5237041472d07e5055f5f7dcdf15b, cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < fe785bb3a8096dffcc4048a85cd0c83337eeecad, cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 5d55c7336f8032d434adcc5fab987ccc93a44aec, cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 8253aab4659ca16116b522203c2a6b18dccacea7, cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 50ed1e7873100f77abad20fd31c51029bc49cd03, cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < b54edf1e9a3fd3491bdcb82a21f8d21315271e0d, cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 71a1d9d985d26716f74d21f18ee8cac821b06e97, cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < 52646cbd00e765a6db9c3afe9535f26218276034, cac2661c53f35cbe651bef9b07026a5a05ab8ce0 < f4c50a4034e62ab75f1d5cdd191dd5f9c77fdff4, 4.11 · Fixed: Linux: < 4.11, 5.10.255 ≤ 5.10.*, 5.15.205 ≤ 5.15.*, 5.15.206 ≤ 5.15.*, 6.1.171 ≤ 6.1.*, 6.1.172 ≤ 6.1.*, 6.6.138 ≤ 6.6.*, 6.12.87 ≤ 6.12.*, 6.18.28 ≤ 6.18.*, 7.0.5 ≤ 7.0.*, 7.1 ≤ *
    CNA ↗
  8. Vendor guidanceAuthoritative vendor guidance changed: added remediation: br-cws-assets.de-fra-1.linodeobjects.com/SA26P010-0ea64434.pdf; removed remediation: nvd.nist.gov/CVE-2026-43284.
    Before
    remediation: nvd.nist.gov/CVE-2026-43284
    After
    remediation: br-cws-assets.de-fra-1.linodeobjects.com/SA26P010-0ea64434.pdf
    ABB Product Security Incident Response Team (PSIRT) ↗
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-28535↗Vendor CSAF · SUSE Product Security Team↗CISA Vulnrichment SSVC evidence↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Public exploit 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-43284 · cve.blacktree.nl