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

bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • 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.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 267 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.

25 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 21 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.101-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1~deb12u1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 7 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

2 current
CVE-2026-53078 · CSAF 2.0 · revision 17 · interimSUSE Product Security TeamCVE-2026-53078
234 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 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
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • 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
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops When a BPF sock_ops program accesses ctx fields with dst_reg == src_reg, the SOCK_OPS_GET_SK() and SOCK_OPS_GET_FIELD() macros fail to zero the destination register in the !fullsock / !locked_tcp_sock path. Both macros borrow a temporary register to check is_fullsock / is_locked_tcp_sock when dst_reg == src_reg, because dst_reg holds the ctx pointer. When the check is false (e.g., TCP_NEW_SYN_RECV state with a request_sock), dst_reg should be zeroed but is not, leaving the stale ctx pointer: - SOCK_OPS_GET_SK: dst_reg retains the ctx pointer, passes NULL checks as PTR_TO_SOCKET_OR_NULL, and can be used as a bogus socket pointer, leading to stack-out-of-bounds access in helpers like bpf_skc_to_tcp6_sock(). - SOCK_OPS_GET_FIELD: dst_reg retains the ctx pointer which the verifier believes is a SCALAR_VALUE, leaking a kernel pointer. Fix both macros by: - Changing JMP_A(1) to JMP_A(2) in the fullsock path to skip the added instruction. - Adding BPF_MOV64_IMM(si->dst_reg, 0) after the temp register restore in the !fullsock path, placed after the restore because dst_reg == src_reg means we need src_reg intact to read ctx->temp.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-53078 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops
246 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's Berkeley Packet Filter (BPF) socket operations (sock_ops) program. When a BPF sock_ops program accesses context fields with the same destination and source registers, certain macros fail to properly clear the destination register. This can lead to a stack-out-of-bounds access, potentially allowing an attacker to execute arbitrary code or cause a denial of service. Additionally, it can result in a kernel pointer leak, disclosing sensitive information.
Remediation
Affected
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-38946

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops When a BPF sock_ops program accesses ctx fields with dst_reg == src_reg, the SOCK_OPS_GET_SK() and SOCK_OPS_GET_FIELD() macros fail to zero the destination register in the !fullsock / !locked_tcp_sock path. Both macros borrow a temporary register to check is_fullsock / is_locked_tcp_sock when dst_reg == src_reg, because dst_reg holds the ctx pointer. When the check is false (e.g., TCP_NEW_SYN_RECV state with a request_sock), dst_reg should be zeroed but is not, leaving the stale ctx pointer: - SOCK_OPS_GET_SK: dst_reg retains the ctx pointer, passes NULL checks as PTR_TO_SOCKET_OR_NULL, and can be used as a bogus socket pointer, leading to stack-out-of-bounds access in helpers like bpf_skc_to_tcp6_sock(). - SOCK_OPS_GET_FIELD: dst_reg retains the ctx pointer which the verifier believes is a SCALAR_VALUE, leaking a kernel pointer. Fix both macros by: - Changing JMP_A(1) to JMP_A(2) in the fullsock path to skip the added instruction. - Adding BPF_MOV64_IMM(si->dst_reg, 0) after the temp register restore in the !fullsock path, placed after the restore because dst_reg == src_reg means we need src_reg intact to read ctx->temp.

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 267 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: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops When a BPF sock_ops program accesses ctx fields with dst_reg == src_reg, the SOCK_OPS_GET_SK() and SOCK_OPS_GET_FIELD() macros fail to zero the destination register in the !fullsock / !locked_tcp_sock path. Both macros borrow a temporary register to check is_fullsock / is_locked_tcp_sock when dst_reg == src_reg, because dst_reg holds the ctx pointer. When the check is false (e.g., TCP_NEW_SYN_RECV state with a request_sock), dst_reg should be zeroed but is not, leaving the stale ctx pointer: - SOCK_OPS_GET_SK: dst_reg retains the ctx pointer, passes NULL checks as PTR_TO_SOCKET_OR_NULL, and can be used as a bogus socket pointer, leading to stack-out-of-bounds access in helpers like bpf_skc_to_tcp6_sock(). - SOCK_OPS_GET_FIELD: dst_reg retains the ctx pointer which the verifier believes is a SCALAR_VALUE, leaking a kernel pointer. Fix both macros by: - Changing JMP_A(1) to JMP_A(2) in the fullsock path to skip the added instruction. - Adding BPF_MOV64_IMM(si->dst_reg, 0) after the temp register restore in the !fullsock path, placed after the restore because dst_reg == src_reg means we need src_reg intact to read ctx->temp.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops When a BPF sock_ops program accesses ctx fields with dst_reg == src_reg, the SOCK_OPS_GET_SK() and SOCK_OPS_GET_FIELD() macros fail to zero the destination register in the !fullsock / !locked_tcp_sock path. Both macros borrow a temporary register to check is_fullsock / is_locked_tcp_sock when dst_reg == src_reg, because dst_reg holds the ctx pointer. When the check is false (e.g., TCP_NEW_SYN_RECV state with a request_sock), dst_reg should be zeroed but is not, leaving the stale ctx pointer: - SOCK_OPS_GET_SK: dst_reg retains the ctx pointer, passes NULL checks as PTR_TO_SOCKET_OR_NULL, and can be used as a bogus socket pointer, leading to stack-out-of-bounds access in helpers like bpf_skc_to_tcp6_sock(). - SOCK_OPS_GET_FIELD: dst_reg retains the ctx pointer which the verifier believes is a SCALAR_VALUE, leaking a kernel pointer. Fix both macros by: - Changing JMP_A(1) to JMP_A(2) in the fullsock path to skip the added instruction. - Adding BPF_MOV64_IMM(si->dst_reg, 0) after the temp register restore in the !fullsock path, placed after the restore because dst_reg == src_reg means we need src_reg intact to read ctx->temp.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops When a BPF sock_ops program accesses ctx fields with dst_reg == src_reg, the SOCK_OPS_GET_SK() and SOCK_OPS_GET_FIELD() macros fail to zero the destination register in the !fullsock / !locked_tcp_sock path. Both macros borrow a temporary register to check is_fullsock / is_locked_tcp_sock when dst_reg == src_reg, because dst_reg holds the ctx pointer. When the check is false (e.g., TCP_NEW_SYN_RECV state with a request_sock), dst_reg should be zeroed but is not, leaving the stale ctx pointer: - SOCK_OPS_GET_SK: dst_reg retains the ctx pointer, passes NULL checks as PTR_TO_SOCKET_OR_NULL, and can be used as a bogus socket pointer, leading to stack-out-of-bounds access in helpers like bpf_skc_to_tcp6_sock(). - SOCK_OPS_GET_FIELD: dst_reg retains the ctx pointer which the verifier believes is a SCALAR_VALUE, leaking a kernel pointer. Fix both macros by: - Changing JMP_A(1) to JMP_A(2) in the fullsock path to skip the added instruction. - Adding BPF_MOV64_IMM(si->dst_reg, 0) after the temp register restore in the !fullsock path, placed after the restore because dst_reg == src_reg means we need src_reg intact to read ctx->temp.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

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

02

Exploit reality and attack path

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

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

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

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

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

Likely attack path
local access → Out-of-bounds Read → 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-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

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

Official authority intelligence

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

ENISA EUVD · EUVD-2026-38946Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops When a BPF sock_ops program accesses ctx fields with dst_reg == src_reg, the SOCK_OPS_GET_SK() and SOCK_OPS_GET_FIELD() macros fail to zero the destination register in the !fullsock / !locked_tcp_sock path. Both macros borrow a temporary register to check is_fullsock / is_locked_tcp_sock when dst_reg == src_reg, because dst_reg holds the ctx pointer. When the check is false (e.g., TCP_NEW_SYN_RECV state with a request_sock), dst_reg should be zeroed but is not, leaving the stale ctx pointer: - SOCK_OPS_GET_SK: dst_reg retains the ctx pointer, passes NULL checks as PTR_TO_SOCKET_OR_NULL, and can be used as a bogus socket pointer, leading to stack-out-of-bounds access in helpers like bpf_skc_to_tcp6_sock(). - SOCK_OPS_GET_FIELD: dst_reg retains the ctx pointer which the verifier believes is a SCALAR_VALUE, leaking a kernel pointer. Fix both macros by: - Changing JMP_A(1) to JMP_A(2) in the fullsock path to skip the added instruction. - Adding BPF_MOV64_IMM(si->dst_reg, 0) after the temp register restore in the !fullsock path, placed after the restore because dst_reg == src_reg means we need src_reg intact to read ctx->temp.

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-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=CVE-2026-53072 Référence CVE CVE-2026-53073 https://www.cve.org/CVERecord?id=CVE-2026-53073 Référence CVE CVE-2026-53074 https://www.cve.org/CVERecord?id=CVE-2026-53074 Référence CVE CVE-2026-53075 https://www.cve.org/CVERecord?id=CVE-2026-53075 Référence CVE CVE-2026-53076 https://www.cve.org/CVERecord?id=CVE-2026-53076 Référence CVE CVE-2026-53077 https://www.cve.org/CVERecord?id=CVE-2026-53077 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53079 https://www.cve.org/CVERecord?id=CVE-2026-53079 Référence CVE CVE-2026-53080 https://www.cve.org/CVERecord?id=CVE-2026-53080 Référence CVE CVE-2026-53081 https://www.cve.org/CVERecord?id=CVE-2026-53081 Référence CVE CVE-2026-53082 https://www.cve.org/CVERecord?id=CVE-2026-53082 Référence CVE CVE-2026-53083 https://www.cve.org/CVERecord?id=CVE-2026-53083 Référence CVE CVE-2026-53084 https://www.cve.org/CVERecord?id=CVE-2026-53084 Référence CVE CVE-2026-53085 https://www.cve.org/CVERecord?id=CVE-2026-53085 Référence CVE CVE-2026-53086 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-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=CVE-2026-53072 Référence CVE CVE-2026-53073 https://www.cve.org/CVERecord?id=CVE-2026-53073 Référence CVE CVE-2026-53074 https://www.cve.org/CVERecord?id=CVE-2026-53074 Référence CVE CVE-2026-53075 https://www.cve.org/CVERecord?id=CVE-2026-53075 Référence CVE CVE-2026-53076 https://www.cve.org/CVERecord?id=CVE-2026-53076 Référence CVE CVE-2026-53077 https://www.cve.org/CVERecord?id=CVE-2026-53077 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53079 https://www.cve.org/CVERecord?id=CVE-2026-53079 Référence CVE CVE-2026-53080 https://www.cve.org/CVERecord?id=CVE-2026-53080 Référence CVE CVE-2026-53081 https://www.cve.org/CVERecord?id=CVE-2026-53081 Référence CVE CVE-2026-53082 https://www.cve.org/CVERecord?id=CVE-2026-53082 Référence CVE CVE-2026-53083 https://www.cve.org/CVERecord?id=CVE-2026-53083 Référence CVE CVE-2026-53084 https://www.cve.org/CVERecord?id=CVE-2026-53084 Référence CVE CVE-2026-53085 https://www.cve.org/CVERecord?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53005 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53009 https://www.cve.org/CVERecord?id=CVE-2026-53009 Référence CVE CVE-2026-53024 https://www.cve.org/CVERecord?id=CVE-2026-53024 Référence CVE CVE-2026-53025 https://www.cve.org/CVERecord?id=CVE-2026-53025 Référence CVE CVE-2026-53043 https://www.cve.org/CVERecord?id=CVE-2026-53043 Référence CVE CVE-2026-53045 https://www.cve.org/CVERecord?id=CVE-2026-53045 Référence CVE CVE-2026-53053 https://www.cve.org/CVERecord?id=CVE-2026-53053 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53109 https://www.cve.org/CVERecord?id=CVE-2026-53109 Référence CVE CVE-2026-53118 https://www.cve.org/CVERecord?id=CVE-2026-53118 Référence CVE CVE-2026-53120 https://www.cve.org/CVERecord?id=CVE-2026-53120 Référence CVE CVE-2026-53129 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-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=CVE-2026-53072 Référence CVE CVE-2026-53073 https://www.cve.org/CVERecord?id=CVE-2026-53073 Référence CVE CVE-2026-53074 https://www.cve.org/CVERecord?id=CVE-2026-53074 Référence CVE CVE-2026-53075 https://www.cve.org/CVERecord?id=CVE-2026-53075 Référence CVE CVE-2026-53076 https://www.cve.org/CVERecord?id=CVE-2026-53076 Référence CVE CVE-2026-53077 https://www.cve.org/CVERecord?id=CVE-2026-53077 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53079 https://www.cve.org/CVERecord?id=CVE-2026-53079 Référence CVE CVE-2026-53080 https://www.cve.org/CVERecord?id=CVE-2026-53080 Référence CVE CVE-2026-53081 https://www.cve.org/CVERecord?id=CVE-2026-53081 Référence CVE CVE-2026-53082 https://www.cve.org/CVERecord?id=CVE-2026-53082 Référence CVE CVE-2026-53083 https://www.cve.org/CVERecord?id=CVE-2026-53083 Référence CVE CVE-2026-53084 https://www.cve.org/CVERecord?id=CVE-2026-53084 Référence CVE CVE-2026-53085 https://www.cve.org/CVERecord?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=

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

LTS. Elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et un déni de service. 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é Debian LTS msg00035 du 18 août 2026 https://lists.debian.org/debian-lts-announce/2026/08/msg00035.html Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2026-45897 https://www.cve.org/CVERecord?id=CVE-2026-45897 Référence CVE CVE-2026-45901 https://www.cve.org/CVERecord?id=CVE-2026-45901 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-64205 https://www.cve.org/CVERecord?id=CVE-2026-64205 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64290 https://www.cve.org/CVERecord?id=CVE-2026-64290 Référence CVE CVE-2026-64561 https://www.cve.org/CVERecord?id=CVE-2026-64561 Référence CVE CVE-2026-64562 https://www.cve.org/CVERecord?id=CVE-2026-64562 Référence CVE CVE-2026-64563 https://www.cve.org/CVERecord?id=CVE-2026-64563 Référence CVE CVE-2026-64564 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-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=CVE-2026-53072 Référence CVE CVE-2026-53073 https://www.cve.org/CVERecord?id=CVE-2026-53073 Référence CVE CVE-2026-53074 https://www.cve.org/CVERecord?id=CVE-2026-53074 Référence CVE CVE-2026-53075 https://www.cve.org/CVERecord?id=CVE-2026-53075 Référence CVE CVE-2026-53076 https://www.cve.org/CVERecord?id=CVE-2026-53076 Référence CVE CVE-2026-53077 https://www.cve.org/CVERecord?id=CVE-2026-53077 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53079 https://www.cve.org/CVERecord?id=CVE-2026-53079 Référence CVE CVE-2026-53080 https://www.cve.org/CVERecord?id=CVE-2026-53080 Référence CVE CVE-2026-53081 https://www.cve.org/CVERecord?id=CVE-2026-53081 Référence CVE CVE-2026-53082 https://www.cve.org/CVERecord?id=CVE-2026-53082 Référence CVE CVE-2026-53083 https://www.cve.org/CVERecord?id=CVE-2026-53083 Référence CVE CVE-2026-53084 https://www.cve.org/CVERecord?id=CVE-2026-53084 Référence CVE CVE-2026-53085 https://www.cve.org/CVERecord?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=

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

ebian. Elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et un déni de service. 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é Debian msg00326 du 06 août 2026 https://lists.debian.org/debian-security-announce/2026/msg00326.html Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2026-45897 https://www.cve.org/CVERecord?id=CVE-2026-45897 Référence CVE CVE-2026-45901 https://www.cve.org/CVERecord?id=CVE-2026-45901 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-64205 https://www.cve.org/CVERecord?id=CVE-2026-64205 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64290 https://www.cve.org/CVERecord?id=CVE-2026-64290 Référence CVE CVE-2026-64561 https://www.cve.org/CVERecord?id=CVE-2026-64561 Référence CVE CVE-2026-64562 https://www.cve.org/CVERecord?id=CVE-2026-64562 Référence CVE CVE-2026-64563 https://www.cve.org/CVERecord?id=CVE-2026-64563 Référence CVE CVE-2026-64564 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-53036 Référence CVE CVE-2026-53039 https://www.cve.org/CVERecord?id=CVE-2026-53039 Référence CVE CVE-2026-53040 https://www.cve.org/CVERecord?id=CVE-2026-53040 Référence CVE CVE-2026-53041 https://www.cve.org/CVERecord?id=CVE-2026-53041 Référence CVE CVE-2026-53049 https://www.cve.org/CVERecord?id=CVE-2026-53049 Référence CVE CVE-2026-53050 https://www.cve.org/CVERecord?id=CVE-2026-53050 Référence CVE CVE-2026-53053 https://www.cve.org/CVERecord?id=CVE-2026-53053 Référence CVE CVE-2026-53060 https://www.cve.org/CVERecord?id=CVE-2026-53060 Référence CVE CVE-2026-53075 https://www.cve.org/CVERecord?id=CVE-2026-53075 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53081 https://www.cve.org/CVERecord?id=CVE-2026-53081 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-53103 https://www.cve.org/CVERecord?id=CVE-2026-53103 Référence CVE CVE-2026-53122 https://www.cve.org/CVERecord?id=CVE-2026-53122 Référence CVE CVE-2026-53133 https://www.cve.org/CVERecord?id=CVE-2026-53133 Référence CVE CVE-2026-53139 https://www.cve.org/CVERecord?id=CVE-2026-53139 Référence CVE CVE-2026-53156 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-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=CVE-2026-53072 Référence CVE CVE-2026-53073 https://www.cve.org/CVERecord?id=CVE-2026-53073 Référence CVE CVE-2026-53074 https://www.cve.org/CVERecord?id=CVE-2026-53074 Référence CVE CVE-2026-53075 https://www.cve.org/CVERecord?id=CVE-2026-53075 Référence CVE CVE-2026-53076 https://www.cve.org/CVERecord?id=CVE-2026-53076 Référence CVE CVE-2026-53077 https://www.cve.org/CVERecord?id=CVE-2026-53077 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53079 https://www.cve.org/CVERecord?id=CVE-2026-53079 Référence CVE CVE-2026-53080 https://www.cve.org/CVERecord?id=CVE-2026-53080 Référence CVE CVE-2026-53081 https://www.cve.org/CVERecord?id=CVE-2026-53081 Référence CVE CVE-2026-53082 https://www.cve.org/CVERecord?id=CVE-2026-53082 Référence CVE CVE-2026-53083 https://www.cve.org/CVERecord?id=CVE-2026-53083 Référence CVE CVE-2026-53084 https://www.cve.org/CVERecord?id=CVE-2026-53084 Référence CVE CVE-2026-53085 https://www.cve.org/CVERecord?id=CVE-2026-53085 Référence CVE CVE-2026-53086 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-53060 Référence CVE CVE-2026-53065 https://www.cve.org/CVERecord?id=CVE-2026-53065 Référence CVE CVE-2026-53066 https://www.cve.org/CVERecord?id=CVE-2026-53066 Référence CVE CVE-2026-53068 https://www.cve.org/CVERecord?id=CVE-2026-53068 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=CVE-2026-53072 Référence CVE CVE-2026-53073 https://www.cve.org/CVERecord?id=CVE-2026-53073 Référence CVE CVE-2026-53075 https://www.cve.org/CVERecord?id=CVE-2026-53075 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53080 https://www.cve.org/CVERecord?id=CVE-2026-53080 Référence CVE CVE-2026-53081 https://www.cve.org/CVERecord?id=CVE-2026-53081 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53098 https://www.cve.org/CVERecord?id=CVE-2026-53098 Référence CVE CVE-2026-53103 https://www.cve.org/CVERecord?id=CVE-2026-53103 Référence CVE CVE-2026-53112 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-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=CVE-2026-53072 Référence CVE CVE-2026-53073 https://www.cve.org/CVERecord?id=CVE-2026-53073 Référence CVE CVE-2026-53074 https://www.cve.org/CVERecord?id=CVE-2026-53074 Référence CVE CVE-2026-53075 https://www.cve.org/CVERecord?id=CVE-2026-53075 Référence CVE CVE-2026-53076 https://www.cve.org/CVERecord?id=CVE-2026-53076 Référence CVE CVE-2026-53077 https://www.cve.org/CVERecord?id=CVE-2026-53077 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53079 https://www.cve.org/CVERecord?id=CVE-2026-53079 Référence CVE CVE-2026-53080 https://www.cve.org/CVERecord?id=CVE-2026-53080 Référence CVE CVE-2026-53081 https://www.cve.org/CVERecord?id=CVE-2026-53081 Référence CVE CVE-2026-53082 https://www.cve.org/CVERecord?id=CVE-2026-53082 Référence CVE CVE-2026-53083 https://www.cve.org/CVERecord?id=CVE-2026-53083 Référence CVE CVE-2026-53084 https://www.cve.org/CVERecord?id=CVE-2026-53084 Référence CVE CVE-2026-53085 https://www.cve.org/CVERecord?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-024705LinuxのLinux Kernelにおける境界外読み取りに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。bpf: sock_opsにおける、同じレジスタのdst/srcの境界外読み取り（OOB）およびポインタリークの問題に対する修正です。BPFのsock_opsプログラムがdst_reg == src_regの場合にctxフィールドへアクセスすると、SOCK_OPS_GET_SK()およびSOCK_OPS_GET_FIELD()マクロが!fullsock／!locked_tcp_sockパスで宛先レジスタをゼロクリアしない不具合がありました。両マクロはdst_regがctxポインタを保持するため、dst_reg == src_regのときにis_fullsock／is_locked_tcp_sockチェックのため一時レジスタを借ります。このチェックが偽の場合（例：request_sockを持つTCP_NEW_SYN_RECV状態）、dst_regはゼロクリアされるべきですがされず、古いctxポインタが残ってしまいます。具体的には、- SOCK_OPS_GET_SKではdst_regがctxポインタのまま残り、PTR_TO_SOCKET_OR_NULLによるNULLチェックを通過し、偽のソケットポインタとして使われる可能性があるため、bpf_skc_to_tcp6_sock()などのヘルパーでスタックの境界外アクセスが発生します。- SOCK_OPS_GET_FIELDではdst_regがctxポインタのままであり、検証機がこれをSCALAR_VALUEとみなすことでカーネルポインタがリークします。これら両マクロの修正点は以下の通りです。- fullsockパスのJMP_A(1)をJMP_A(2)に変更し、追加命令をスキップするようにしました。- !fullsockパスで一時レジスタ復元後にBPF_MOV64_IMM(si-＞dst_reg, 0)を追加しました。dst_reg == src_regであるため、src_regはctx-＞temp読み取りに必要であり、復元後にゼロクリアを行っています。

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: < 5.9, 5.10.270 ≤ 5.10.*, 5.15.221 ≤ 5.15.*, 6.1.188 ≤ 6.1.*, 6.6.157 ≤ 6.6.*, 6.12.101 ≤ 6.12.*, 6.18.42 ≤ 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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 24 Jun 2026 · Last source change 14 Sept 2026, 11:58 UTC · CWE-125 · Out-of-bounds Read

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

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    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; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1; reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; 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; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4; and 202 more · Fixed: kernel-obs-build-6.12.0-160000.36.1 as component of SUSE Linux Micro Extras 6.2; kernel-syms-6.12.0-160000.36.1 as component of SUSE Linux Micro Extras 6.2
    After
    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; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1; reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; 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; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4; and 204 more
    SUSE Product Security Team ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    fd09af010788a884de1c39537c288830c3d305db < 2a2c98141e0a75f2d4a7d78b0316c88b3da784ac; fd09af010788a884de1c39537c288830c3d305db < 22400725de070b787cd6d806c5795370ab46d269; fd09af010788a884de1c39537c288830c3d305db < 18e3ffde1822f0b48b1753bf34aa97ce839df1d8; fd09af010788a884de1c39537c288830c3d305db < 10f86a2a5c91fc4c4d001960f1c21abe52545ef6; 48be3df15aa19c04eadf156c9129293c9a10389f; cd4644d904e1d153d516e73e2e127e7a2fe687e1; 6e0bc946cbeec538322820786b5fb5200a2216ab; a7e52f7f675046d9ffc5692d815fa67c82fcdbf5 · Fixed: < 5.9; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.0.10 ≤ 7.0.*; 7.1 ≤ *
    After
    Linux: fd09af010788a884de1c39537c288830c3d305db < db1200ec2c3ddf119d4d9ba67982063df06bbacb, fd09af010788a884de1c39537c288830c3d305db < 4c1c5efd9d1d74743d41ce4e1600501b4feb6827, fd09af010788a884de1c39537c288830c3d305db < 0e6b30657bbc771f38025c828d722b6162428508, fd09af010788a884de1c39537c288830c3d305db < 64eaf4ecda007140ddcdb28e00c48c9c69aaba39, fd09af010788a884de1c39537c288830c3d305db < 2a2c98141e0a75f2d4a7d78b0316c88b3da784ac, fd09af010788a884de1c39537c288830c3d305db < 22400725de070b787cd6d806c5795370ab46d269, fd09af010788a884de1c39537c288830c3d305db < 18e3ffde1822f0b48b1753bf34aa97ce839df1d8, fd09af010788a884de1c39537c288830c3d305db < 10f86a2a5c91fc4c4d001960f1c21abe52545ef6, 48be3df15aa19c04eadf156c9129293c9a10389f, cd4644d904e1d153d516e73e2e127e7a2fe687e1, 6e0bc946cbeec538322820786b5fb5200a2216ab, a7e52f7f675046d9ffc5692d815fa67c82fcdbf5, db7f8c57dbdd31f7e59f8dc8d1e1b38607a320ef, 5.7.18 < 5.8, 5.8.4 < 5.9, 5.4.61 < 5.5, 5.9 · Fixed: Linux: < 5.9, 5.10.270 ≤ 5.10.*, 5.15.221 ≤ 5.15.*, 6.1.188 ≤ 6.1.*, 6.6.157 ≤ 6.6.*, 6.12.101 ≤ 6.12.*, 6.18.42 ≤ 6.18.*, 7.0.10 ≤ 7.0.*, 7.1 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-38946↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-53078 · cve.blacktree.nl