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

net/rds: handle zerocopy send cleanup before the message is queued

Linux · Linux

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

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

Authoritative vendor CSAF and VEX advisories

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

1 current
CVE-2026-43502 · CSAF 2.0 · revision 20 · interimSUSE Product Security TeamCVE-2026-43502
159 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
Summary
In the Linux kernel, the following vulnerability has been resolved: net/rds: handle zerocopy send cleanup before the message is queued A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket. The purge path currently infers zerocopy state from rm->m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue. Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages. This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-31275

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net/rds: handle zerocopy send cleanup before the message is queued A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket. The purge path currently infers zerocopy state from rm->m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue. Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages. This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path.

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net/rds: handle zerocopy send cleanup before the message is queued A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket. The purge path currently infers zerocopy state from rm->m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue. Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages. This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path.

What

In the Linux kernel, the following vulnerability has been resolved: net/rds: handle zerocopy send cleanup before the message is queued A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket. The purge path currently infers zerocopy state from rm->m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue. Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages. This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path.

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: net/rds: handle zerocopy send cleanup before the message is queued A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket. The purge path currently infers zerocopy state from rm->m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue. Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages. This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path.

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
local access → Missing Release of Memory after Effective Lifetime → 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-401 ↗

CWE-401: Missing Release of Memory after Effective Lifetime. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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-401Public 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-31275Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net/rds: handle zerocopy send cleanup before the message is queued A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket. The purge path currently infers zerocopy state from rm->m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue. Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages. This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path.

Official EUVD record ↗
BSI · German · WID-SEC-2026-1656Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um seine Privilegien zu eskalieren oder nicht näher spezifizierte Angriffe durchzuführen, darunter möglicherweise Denial-of-Service-Angriffe, Speicherbeschädigungen oder die Offenlegung von Informationen.

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

d?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-43490 https://www.cve.org/CVERecord?id=CVE-2026-43490 Référence CVE CVE-2026-43492 https://www.cve.org/CVERecord?id=CVE-2026-43492 Référence CVE CVE-2026-43495 https://www.cve.org/CVERecord?id=CVE-2026-43495 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 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-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43480 Référence CVE CVE-2026-43484 https://www.cve.org/CVERecord?id=CVE-2026-43484 Référence CVE CVE-2026-43490 https://www.cve.org/CVERecord?id=CVE-2026-43490 Référence CVE CVE-2026-43492 https://www.cve.org/CVERecord?id=CVE-2026-43492 Référence CVE CVE-2026-43495 https://www.cve.org/CVERecord?id=CVE-2026-43495 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 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-1231Multiples vulnérabilités dans le noyau Linux de SUSE

d?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=CVE-2026-43502 Référence CVE CVE-2026-45941 https://www.cve.org/CVERecord?id=CVE-2026-45941 Référence CVE CVE-2026-45968 https://www.cve.org/CVERecord?id=CVE-2026-45968 Référence CVE CVE-2026-46070 https://www.cve.org/CVERecord?id=CVE-2026-46070 Référence CVE CVE-2026-46107 https://www.cve.org/CVERecord?id=CVE-2026-46107 Référence CVE CVE-2026-46108 https://www.cve.org/CVERecord?id=CVE-2026-46108 Référence CVE CVE-2026-46128 https://www.cve.org/CVERecord?id=CVE-2026-46128 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-52910 https://www.cve.org/CVERecord?id=

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

d?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-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43490 https://www.cve.org/CVERecord?id=CVE-2026-43490 Référence CVE CVE-2026-43492 https://www.cve.org/CVERecord?id=CVE-2026-43492 Référence CVE CVE-2026-43495 https://www.cve.org/CVERecord?id=CVE-2026-43495 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 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-1093Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43475 Référence CVE CVE-2026-43476 https://www.cve.org/CVERecord?id=CVE-2026-43476 Référence CVE CVE-2026-43480 https://www.cve.org/CVERecord?id=CVE-2026-43480 Référence CVE CVE-2026-43484 https://www.cve.org/CVERecord?id=CVE-2026-43484 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 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=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43490 Référence CVE CVE-2026-43491 https://www.cve.org/CVERecord?id=CVE-2026-43491 Référence CVE CVE-2026-43492 https://www.cve.org/CVERecord?id=CVE-2026-43492 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43495 https://www.cve.org/CVERecord?id=CVE-2026-43495 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 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-0985Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43469 Référence CVE CVE-2026-43472 https://www.cve.org/CVERecord?id=CVE-2026-43472 Référence CVE CVE-2026-43473 https://www.cve.org/CVERecord?id=CVE-2026-43473 Référence CVE CVE-2026-43475 https://www.cve.org/CVERecord?id=CVE-2026-43475 Référence CVE CVE-2026-43476 https://www.cve.org/CVERecord?id=CVE-2026-43476 Référence CVE CVE-2026-43480 https://www.cve.org/CVERecord?id=CVE-2026-43480 Référence CVE CVE-2026-43484 https://www.cve.org/CVERecord?id=CVE-2026-43484 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 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=CVE-2026-45841 Référence CVE CVE-2026-45842 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-43468 Référence CVE CVE-2026-43469 https://www.cve.org/CVERecord?id=CVE-2026-43469 Référence CVE CVE-2026-43470 https://www.cve.org/CVERecord?id=CVE-2026-43470 Référence CVE CVE-2026-43471 https://www.cve.org/CVERecord?id=CVE-2026-43471 Référence CVE CVE-2026-43473 https://www.cve.org/CVERecord?id=CVE-2026-43473 Référence CVE CVE-2026-43491 https://www.cve.org/CVERecord?id=CVE-2026-43491 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=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 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=CVE-2026-45841 Référence CVE CVE-2026-45848 https://www.cve.org/CVERecord?id=CVE-2026-45848 Référence CVE CVE-2026-45857 https://www.cve.org/CVERecord?id=CVE-2026-45857 Référence CVE CVE-2026-45858 https://www.cve.org/CVERecord?id=CVE-2026-45858 Référence CVE CVE-2026-45861 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-43493 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43495 https://www.cve.org/CVERecord?id=CVE-2026-43495 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 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=

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

d?id=CVE-2026-43480 Référence CVE CVE-2026-43488 https://www.cve.org/CVERecord?id=CVE-2026-43488 Référence CVE CVE-2026-43491 https://www.cve.org/CVERecord?id=CVE-2026-43491 Référence CVE CVE-2026-43492 https://www.cve.org/CVERecord?id=CVE-2026-43492 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 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=CVE-2026-45841 Référence CVE CVE-2026-45848 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-43493 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43495 https://www.cve.org/CVERecord?id=CVE-2026-43495 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 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=

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

d?id=CVE-2026-43456 Référence CVE CVE-2026-43469 https://www.cve.org/CVERecord?id=CVE-2026-43469 Référence CVE CVE-2026-43470 https://www.cve.org/CVERecord?id=CVE-2026-43470 Référence CVE CVE-2026-43472 https://www.cve.org/CVERecord?id=CVE-2026-43472 Référence CVE CVE-2026-43483 https://www.cve.org/CVERecord?id=CVE-2026-43483 Référence CVE CVE-2026-43491 https://www.cve.org/CVERecord?id=CVE-2026-43491 Référence CVE CVE-2026-43492 https://www.cve.org/CVERecord?id=CVE-2026-43492 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 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=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45848 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-43421 Référence CVE CVE-2026-43492 https://www.cve.org/CVERecord?id=CVE-2026-43492 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43495 https://www.cve.org/CVERecord?id=CVE-2026-43495 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 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=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=

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

Linuxカーネルのnet/rdsにおいて、ゼロコピー送信のクリーンアップ処理に関する脆弱性が修正されました。ゼロコピー送信がユーザーページをピン留めした後に失敗した場合、メッセージがソケットキューに到達していなくても誤ったクリーンアップが行われる可能性がありました。修正では、メッセージの状態を正確に判定し、キューに入る前の失敗時にも適切にピン留めページの計数を減らして解放することで、この問題を解消しています。これにより、通常の処理経路を変更せずにクリーンアップの一貫性を保証します。

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.17, 5.10.258 ≤ 5.10.*, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.88 ≤ 6.12.*, 6.18.30 ≤ 6.18.*, 7.0.7 ≤ 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.
04

Evidence and provenance

Published 21 May 2026 · Last source change 15 Sept 2026, 03:56 UTC · CWE-401 · Missing Release of Memory after Effective Lifetime

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-31275
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. Public exploit evidencePublic exploit evidence changed from Public exploit reference to Public exploit reference.
    Before
    Public exploit reference
    After
    Public exploit reference
    CVE.org ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < e9aefdc5c53fe9aed108c14e3d155710a1bb14c9; 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 46662f7dc59475995609bf3e9d27eb36f4acf26f; 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 1e262db7675e27f42c3f3f47d6011855f4454f24; 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 21d70744e6d3bbf9293aa1ee6fba7c53ad75275e; 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 3abc8983b2bae3f487f77d9da5527d7d6b210d46; 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 14ef6fd18db2494098b21e0471bf27a1d8e9993e; 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 0f5c185fc79a59ee9991234dd6d2a3e5afa6e75b; 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 44b550d88b267320459d518c0743a241ab2108fa · Fixed: < 4.17; 5.10.258 ≤ 5.10.*; 5.15.209 ≤ 5.15.*; 6.1.175 ≤ 6.1.*; 6.6.140 ≤ 6.6.*; 6.12.88 ≤ 6.12.*; 6.18.30 ≤ 6.18.*; 7.0.7 ≤ 7.0.*
    After
    Linux: 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < e9aefdc5c53fe9aed108c14e3d155710a1bb14c9, 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 46662f7dc59475995609bf3e9d27eb36f4acf26f, 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 1e262db7675e27f42c3f3f47d6011855f4454f24, 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 21d70744e6d3bbf9293aa1ee6fba7c53ad75275e, 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 3abc8983b2bae3f487f77d9da5527d7d6b210d46, 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 14ef6fd18db2494098b21e0471bf27a1d8e9993e, 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 0f5c185fc79a59ee9991234dd6d2a3e5afa6e75b, 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 44b550d88b267320459d518c0743a241ab2108fa, 4.17 · Fixed: Linux: < 4.17, 5.10.258 ≤ 5.10.*, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.88 ≤ 6.12.*, 6.18.30 ≤ 6.18.*, 7.0.7 ≤ 7.0.*, 7.1 ≤ *
    CNA ↗
  3. Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.
    Before
    No public exploit
    After
    Public exploit reference
    github.com ↗
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-31275↗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↗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-43502 · cve.blacktree.nl