Full vulnerability report · 2026

CVE-2026-52974High confidence

net: tls: fix strparser anchor skb leak on offload RX setup failure

Linux · Linux

7.5HighCVSS 3.1

Recommended action

Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 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

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.
The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
EPSS is 0.68% for the current model date.

Compensating controls

Validate the affected product branch and deploy the verified fixed release.
Restrict the affected network interface to trusted sources where business-safe.
Monitor vendor guidance and exploitation sources for a material change.

Verification

Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.

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.

Canonical Ubuntu Security: 20 affected package states with no published fix

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 release	Source package	Vendor state	Fixed version	Evidence
Debian trixietrixie · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.94-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.1.176-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`7.0.10-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`7.0.10-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, 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 feed`	Canonical 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-52974 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2026-52974

76 known affected

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

kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP7

Summary: In the Linux kernel, the following vulnerability has been resolved: net: tls: fix strparser anchor skb leak on offload RX setup failure When tls_set_device_offload_rx() fails at tls_dev_add(), the error path calls tls_sw_free_resources_rx() to clean up the SW context that was initialized by tls_set_sw_offload(). This function calls tls_sw_release_resources_rx() (which stops the strparser via tls_strp_stop()) and tls_sw_free_ctx_rx() (which kfrees the context), but never frees the anchor skb that was allocated by alloc_skb(0) in tls_strp_init(). Note that tls_sw_free_resources_rx() is exclusively used for this "failed to start offload" code path, there's no other caller. The leak did not exist before commit 84c61fe1a75b ("tls: rx: do not use the standard strparser"), because the standard strparser doesn't try to pre-allocate an skb. The normal close path in tls_sk_proto_close() handles cleanup by calling tls_sw_strparser_done() (which calls tls_strp_done()) after dropping the socket lock, because tls_strp_done() does cancel_work_sync() and the strparser work handler takes the socket lock.
Remediation: To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

Recommended actionPatch only the product branches with a verified fix

Fix availability varies by product

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net: tls: fix strparser anchor skb leak on offload RX setup failure When tls_set_device_offload_rx() fails at tls_dev_add(), the error path calls tls_sw_free_resources_rx() to clean up the SW context that was initialized by tls_set_sw_offload(). This function calls tls_sw_release_resources_rx() (which stops the strparser via tls_strp_stop()) and tls_sw_free_ctx_rx() (which kfrees the context), but never frees the anchor skb that was allocated by alloc_skb(0) in tls_strp_init(). Note that tls_sw_free_resources_rx() is exclusively used for this "failed to start offload" code path, there's no other caller. The leak did not exist before commit 84c61fe1a75b ("tls: rx: do not use the standard strparser"), because the standard strparser doesn't try to pre-allocate an skb. The normal close path in tls_sk_proto_close() handles cleanup by calling tls_sw_strparser_done() (which calls tls_strp_done()) after dropping the socket lock, because tls_strp_done() does cancel_work_sync() and the strparser work handler takes the socket lock.

What

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 a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: a network path → Missing Release of Memory after Effective Lifetime → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Network
Privileges required: None: unauthenticated exploitation is possible
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:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

NetworkUnauthenticatedCWE-401

Official authority intelligence

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

ENISA EUVD · EUVD-2026-38842Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

BSI · German · WID-SEC-2026-2077Linux Kernel: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗

Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

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

Official advisory ↗

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

d?id=CVE-2026-52963 Référence CVE CVE-2026-52964 https://www.cve.org/CVERecord?id=CVE-2026-52964 Référence CVE CVE-2026-52965 https://www.cve.org/CVERecord?id=CVE-2026-52965 Référence CVE CVE-2026-52967 https://www.cve.org/CVERecord?id=CVE-2026-52967 Référence CVE CVE-2026-52968 https://www.cve.org/CVERecord?id=CVE-2026-52968 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52970 https://www.cve.org/CVERecord?id=CVE-2026-52970 Référence CVE CVE-2026-52971 https://www.cve.org/CVERecord?id=CVE-2026-52971 Référence CVE CVE-2026-52973 https://www.cve.org/CVERecord?id=CVE-2026-52973 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=CVE-2026-52975 Référence CVE CVE-2026-52976 https://www.cve.org/CVERecord?id=CVE-2026-52976 Référence CVE CVE-2026-52977 https://www.cve.org/CVERecord?id=CVE-2026-52977 Référence CVE CVE-2026-52978 https://www.cve.org/CVERecord?id=CVE-2026-52978 Référence CVE CVE-2026-52979 https://www.cve.org/CVERecord?id=CVE-2026-52979 Référence CVE CVE-2026-52980 https://www.cve.org/CVERecord?id=CVE-2026-52980 Référence CVE CVE-2026-52981 https://www.cve.org/CVERecord?id=CVE-2026-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

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

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1091Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-52930 Référence CVE CVE-2026-52937 https://www.cve.org/CVERecord?id=CVE-2026-52937 Référence CVE CVE-2026-52941 https://www.cve.org/CVERecord?id=CVE-2026-52941 Référence CVE CVE-2026-52942 https://www.cve.org/CVERecord?id=CVE-2026-52942 Référence CVE CVE-2026-52947 https://www.cve.org/CVERecord?id=CVE-2026-52947 Référence CVE CVE-2026-52956 https://www.cve.org/CVERecord?id=CVE-2026-52956 Référence CVE CVE-2026-52967 https://www.cve.org/CVERecord?id=CVE-2026-52967 Référence CVE CVE-2026-52970 https://www.cve.org/CVERecord?id=CVE-2026-52970 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=CVE-2026-52972 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52988 https://www.cve.org/CVERecord?id=CVE-2026-52988 Référence CVE CVE-2026-52991 https://www.cve.org/CVERecord?id=CVE-2026-52991 Référence CVE CVE-2026-52998 https://www.cve.org/CVERecord?id=CVE-2026-52998 Référence CVE CVE-2026-52999 https://www.cve.org/CVERecord?id=CVE-2026-52999 Référence CVE CVE-2026-53000 https://www.cve.org/CVERecord?id=CVE-2026-53000 Référence CVE CVE-2026-53002 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-52956 Référence CVE CVE-2026-52958 https://www.cve.org/CVERecord?id=CVE-2026-52958 Référence CVE CVE-2026-52959 https://www.cve.org/CVERecord?id=CVE-2026-52959 Référence CVE CVE-2026-52963 https://www.cve.org/CVERecord?id=CVE-2026-52963 Référence CVE CVE-2026-52964 https://www.cve.org/CVERecord?id=CVE-2026-52964 Référence CVE CVE-2026-52967 https://www.cve.org/CVERecord?id=CVE-2026-52967 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52970 https://www.cve.org/CVERecord?id=CVE-2026-52970 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=CVE-2026-52972 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52976 https://www.cve.org/CVERecord?id=CVE-2026-52976 Référence CVE CVE-2026-52981 https://www.cve.org/CVERecord?id=CVE-2026-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52988 https://www.cve.org/CVERecord?id=CVE-2026-52988 Référence CVE CVE-2026-52989 https://www.cve.org/CVERecord?id=CVE-2026-52989 Référence CVE CVE-2026-52995 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

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

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0866Multiples vulnérabilités dans Microsoft Azure Linux

u 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52936 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52958 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52963 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52967 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52968 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52969 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52970 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52972 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52974 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52975 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52977 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52981 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52982 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52984 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52985 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52986 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52989 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linu

Official advisory ↗

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

d?id=CVE-2026-52957 Référence CVE CVE-2026-52958 https://www.cve.org/CVERecord?id=CVE-2026-52958 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52963 https://www.cve.org/CVERecord?id=CVE-2026-52963 Référence CVE CVE-2026-52967 https://www.cve.org/CVERecord?id=CVE-2026-52967 Référence CVE CVE-2026-52968 https://www.cve.org/CVERecord?id=CVE-2026-52968 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52970 https://www.cve.org/CVERecord?id=CVE-2026-52970 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=CVE-2026-52972 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=CVE-2026-52975 Référence CVE CVE-2026-52977 https://www.cve.org/CVERecord?id=CVE-2026-52977 Référence CVE CVE-2026-52981 https://www.cve.org/CVERecord?id=CVE-2026-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52985 https://www.cve.org/CVERecord?id=CVE-2026-52985 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52989 https://www.cve.org/CVERecord?id=

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2026-023773LinuxのLinux Kernelにおける有効期限後のメモリの解放の欠如に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました：net: tls: オフロードRXセットアップ失敗時のstrparserアンカーskbリークの修正。tls_set_device_offload_rx()がtls_dev_add()で失敗すると、エラー処理経路はtls_sw_free_resources_rx()を呼び出し、tls_set_sw_offload()で初期化されたソフトウェアコンテキストをクリーンアップします。この関数はtls_sw_release_resources_rx()（tls_strp_stop()を介してstrparserを停止）およびtls_sw_free_ctx_rx()（コンテキストをkfree）を呼び出しますが、tls_strp_init()内でalloc_skb(0)により割り当てられたアンカーskbを解放しません。なお、tls_sw_free_resources_rx()はこの「オフロード開始失敗」の経路でのみ使用されており、他に呼び出し元は存在しません。このリークは、標準のstrparserがskbの事前割り当てを行わないため、commit 84c61fe1a75b（「tls: rx: 標準strparserを使用しない」）以前には存在しませんでした。通常のクローズ経路であるtls_sk_proto_close()は、ソケットロックを解放した後にtls_sw_strparser_done()（tls_strp_done()を呼び出す）を使ってクリーンアップします。これはtls_strp_done()がcancel_work_sync()を実行し、strparserのワークハンドラがソケットロックを取得するためです。

Official advisory ↗

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: kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7
kernel-source as component of SUSE Linux Enterprise Module for Legacy 15 SP7
reiserfs-kmp-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7
kernel-default as component of SUSE Linux Enterprise Module for Public Cloud 15 SP7
kernel-source as component of SUSE Linux Enterprise Module for Public Cloud 15 SP7
cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
gfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-default-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-macros as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-source as component of SUSE Linux Enterprise Server 15 SP6-LTSS
ocfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
reiserfs-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
and 46 more
Fixed: Linux: < 6.0, 6.1.175 ≤ 6.1.*, 6.6.141 ≤ 6.6.*, 6.12.91 ≤ 6.12.*, 6.18.33 ≤ 6.18.*, 7.0.10 ≤ 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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Evidence and provenance

Published 24 Jun 2026 · Last source change 5 Aug 2026, 12:32 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-38842

Product sourceVendor CSAF · SUSE Product Security Team

Remediation sourceVendor CSAF · SUSE Product Security Team

CWE sourceNIST NVD

NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2026-06-24CVE published

2026-08-05Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-38842↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

net: tls: fix strparser anchor skb leak on offload RX setup failure

Published severity in operational context

Evidence used

Compensating controls

Verification

Remediation availability differs by product scope

Release-specific package status

Authoritative vendor CSAF and VEX advisories

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

ENISA European Vulnerability Database

EUVD-2026-38842

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication