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

af_unix: Fix UAF read of tail->len in unix_stream_data_wait()

Linux · Linux

8.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 21 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 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.13% 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 21 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 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.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-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-64109 · CSAF 2.0 · revision 14 · interimSUSE Product Security TeamCVE-2026-64109
257 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1
Summary
In the Linux kernel, the following vulnerability has been resolved: af_unix: Fix UAF read of tail->len in unix_stream_data_wait() unix_stream_data_wait() does skb_peek_tail(&sk->sk_receive_queue) without holding any lock that prevents SKBs on that queue from being dequeued and freed. This has been the case since commit 79f632c71bea ("unix/stream: fix peeking with an offset larger than data in queue"). The first consequence of this is that the pointer comparison `tail != last` can be false even if `last` semantically refers to an already-freed SKB while `tail` is a new SKB allocated at the same address; which can cause unix_stream_data_wait() to wrongly keep blocking after new data has arrived, but only in a weird scenario where a peeking recv() and a normal recv() on the same socket are racing, which is probably not a real problem. But since commit 2b514574f7e8 ("net: af_unix: implement splice for stream af_unix sockets"), `tail` is actually dereferenced, which can cause UAF in the following race scenario (where test_setup() runs single-threaded, and afterwards, test_thread1() and test_thread2() run concurrently in two threads: ``` static int socks[2]; void test_setup(void) { socketpair(AF_UNIX, SOCK_STREAM, 0, socks); send(socks[1], "A", 1, 0); int peekoff = 1; setsockopt(socks[0], SOL_SOCKET, SO_PEEK_OFF, &peekoff, sizeof(peekoff)); } void test_thread1(void) { char dummy; recv(socks[0], &dummy, 1, MSG_PEEK); } void test_thread2(void) { char dummy; recv(socks[0], &dummy, 1, 0); shutdown(socks[1], SHUT_WR); } ``` when racing like this: ``` thread1 thread2 unix_stream_read_generic mutex_lock(&u->iolock) skb_peek(&sk->sk_receive_queue) skb_peek_next(skb, &sk->sk_receive_queue) mutex_unlock(&u->iolock) unix_stream_read_generic unix_state_lock(sk) skb_peek(&sk->sk_receive_queue) unix_state_unlock(sk) unix_stream_data_wait unix_state_lock(sk) tail = skb_peek_tail(&sk->sk_receive_queue) spin_lock(&sk->sk_receive_queue.lock) __skb_unlink(skb, &sk->sk_receive_queue) spin_unlock(&sk->sk_receive_queue.lock) consume_skb(skb) [frees the SKB] `tail != last`: false `tail`: true `tail->len != last_len` ***UAF*** ``` Fix the UAF by removing the read of tail->len; checking tail->len would only make sense if SKBs in the receive queue of a UNIX socket could grow, which can no longer happen. Kuniyuki explained: > When commit 869e7c62486e ("net: af_unix: implement stream sendpage > support") added sendpage() support, data could be appended to the last > skb in the receiver's queue. > > That's why we needed to check if the length of the last skb was changed > while waiting for new data in unix_stream_data_wait(). > > However, commit a0dbf5f818f9 ("af_unix: Support MSG_SPLICE_PAGES") and > commit 57d44a354a43 ("unix: Convert unix_stream_sendpage() to use > MSG_SPLICE_PAGES") refactored sendmsg(), and now data is always added > to a new skb. That means this fix is not suitable for kernels before 6.5.
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-45794

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
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 21 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: af_unix: Fix UAF read of tail->len in unix_stream_data_wait() unix_stream_data_wait() does skb_peek_tail(&sk->sk_receive_queue) without holding any lock that prevents SKBs on that queue from being dequeued and freed. This has been the case since commit 79f632c71bea ("unix/stream: fix peeking with an offset larger than data in queue"). The first consequence of this is that the pointer comparison `tail != last` can be false even if `last` semantically refers to an already-freed SKB while `tail` is a new SKB allocated at the same address; which can cause unix_stream_data_wait() to wrongly keep blocking after new data has arrived, but only in a weird scenario where a peeking recv() and a normal recv() on the same socket are racing, which is probably not a real problem. But since commit 2b514574f7e8 ("net: af_unix: implement splice for stream af_unix sockets"), `tail` is actually dereferenced, which can cause UAF in the following race scenario (where test_setup() runs single-threaded, and afterwards, test_thread1() and test_thread2() run concurrently in two threads: ``` static int socks[2]; void test_setup(void) { socketpair(AF_UNIX, SOCK_STREAM, 0, socks); send(socks[1], "A", 1, 0); int peekoff = 1; setsockopt(socks[0], SOL_SOCKET, SO_PEEK_OFF, &peekoff, sizeof(peekoff)); } void test_thread1(void) { char dummy; recv(socks[0], &dummy, 1, MSG_PEEK); } void test_thread2(void) { char dummy; recv(socks[0], &dummy, 1, 0); shutdown(socks[1], SHUT_WR); } ``` when racing like this: ``` thread1 thread2 unix_stream_read_generic mutex_lock(&u->iolock) skb_peek(&sk->sk_receive_queue) skb_peek_next(skb, &sk->sk_receive_queue) mutex_unlock(&u->iolock) unix_stream_read_generic unix_state_lock(sk) skb_peek(&sk->sk_receive_queue) unix_state_unlock(sk) unix_stream_data_wait unix_state_lock(sk) tail = skb_peek_tail(&sk->sk_receive_queue) spin_lock(&sk->sk_receive_queue.lock) __skb_unlink(skb, &sk->sk_receive_queue) spin_unlock(&sk->sk_receive_queue.lock) consume_skb(skb) [frees the SKB] `tail != last`: false `tail`: true `tail->len != last_len` ***UAF*** ``` Fix the UAF by removing the read of tail->len; checking tail->len would only make sense if SKBs in the receive queue of a UNIX socket could grow, which can no longer happen. Kuniyuki explained: > When commit 869e7c62486e ("net: af_unix: implement stream sendpage > support") added sendpage() support, data could be appended to the last > skb in the receiver's queue. > > That's why we needed to check if the length of the last skb was changed > while waiting for new data in unix_stream_data_wait(). > > However, commit a0dbf5f818f9 ("af_unix: Support MSG_SPLICE_PAGES") and > commit 57d44a354a43 ("unix: Convert unix_stream_sendpage() to use > MSG_SPLICE_PAGES") refactored sendmsg(), and now data is always added > to a new skb. That means this fix is not suitable for kernels before 6.5.

What

In the Linux kernel, the following vulnerability has been resolved: af_unix: Fix UAF read of tail->len in unix_stream_data_wait() unix_stream_data_wait() does skb_peek_tail(&sk->sk_receive_queue) without holding any lock that prevents SKBs on that queue from being dequeued and freed. This has been the case since commit 79f632c71bea ("unix/stream: fix peeking with an offset larger than data in queue"). The first consequence of this is that the pointer comparison `tail != last` can be false even if `last` semantically refers to an already-freed SKB while `tail` is a new SKB allocated at the same address; which can cause unix_stream_data_wait() to wrongly keep blocking after new data has arrived, but only in a weird scenario where a peeking recv() and a normal recv() on the same socket are racing, which is probably not a real problem. But since commit 2b514574f7e8 ("net: af_unix: implement splice for stream af_unix sockets"), `tail` is actually dereferenced, which can cause UAF in the following race scenario (where test_setup() runs single-threaded, and afterwards, test_thread1() and test_thread2() run concurrently in two threads: ``` static int socks[2]; void test_setup(void) { socketpair(AF_UNIX, SOCK_STREAM, 0, socks); send(socks[1], "A", 1, 0); int peekoff = 1; setsockopt(socks[0], SOL_SOCKET, SO_PEEK_OFF, &peekoff, sizeof(peekoff)); } void test_thread1(void) { char dummy; recv(socks[0], &dummy, 1, MSG_PEEK); } void test_thread2(void) { char dummy; recv(socks[0], &dummy, 1, 0); shutdown(socks[1], SHUT_WR); } ``` when racing like this: ``` thread1 thread2 unix_stream_read_generic mutex_lock(&u->iolock) skb_peek(&sk->sk_receive_queue) skb_peek_next(skb, &sk->sk_receive_queue) mutex_unlock(&u->iolock) unix_stream_read_generic unix_state_lock(sk) skb_peek(&sk->sk_receive_queue) unix_state_unlock(sk) unix_stream_data_wait unix_state_lock(sk) tail = skb_peek_tail(&sk->sk_receive_queue) spin_lock(&sk->sk_receive_queue.lock) __skb_unlink(skb, &sk->sk_receive_queue) spin_unlock(&sk->sk_receive_queue.lock) consume_skb(skb) [frees the SKB] `tail != last`: false `tail`: true `tail->len != last_len` ***UAF*** ``` Fix the UAF by removing the read of tail->len; checking tail->len would only make sense if SKBs in the receive queue of a UNIX socket could grow, which can no longer happen. Kuniyuki explained: > When commit 869e7c62486e ("net: af_unix: implement stream sendpage > support") added sendpage() support, data could be appended to the last > skb in the receiver's queue. > > That's why we needed to check if the length of the last skb was changed > while waiting for new data in unix_stream_data_wait(). > > However, commit a0dbf5f818f9 ("af_unix: Support MSG_SPLICE_PAGES") and > commit 57d44a354a43 ("unix: Convert unix_stream_sendpage() to use > MSG_SPLICE_PAGES") refactored sendmsg(), and now data is always added > to a new skb. That means this fix is not suitable for kernels before 6.5.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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: af_unix: Fix UAF read of tail->len in unix_stream_data_wait() unix_stream_data_wait() does skb_peek_tail(&sk->sk_receive_queue) without holding any lock that prevents SKBs on that queue from being dequeued and freed. This has been the case since commit 79f632c71bea ("unix/stream: fix peeking with an offset larger than data in queue"). The first consequence of this is that the pointer comparison `tail != last` can be false even if `last` semantically refers to an already-freed SKB while `tail` is a new SKB allocated at the same address; which can cause unix_stream_data_wait() to wrongly keep blocking after new data has arrived, but only in a weird scenario where a peeking recv() and a normal recv() on the same socket are racing, which is probably not a real problem. But since commit 2b514574f7e8 ("net: af_unix: implement splice for stream af_unix sockets"), `tail` is actually dereferenced, which can cause UAF in the following race scenario (where test_setup() runs single-threaded, and afterwards, test_thread1() and test_thread2() run concurrently in two threads: ``` static int socks[2]; void test_setup(void) { socketpair(AF_UNIX, SOCK_STREAM, 0, socks); send(socks[1], "A", 1, 0); int peekoff = 1; setsockopt(socks[0], SOL_SOCKET, SO_PEEK_OFF, &peekoff, sizeof(peekoff)); } void test_thread1(void) { char dummy; recv(socks[0], &dummy, 1, MSG_PEEK); } void test_thread2(void) { char dummy; recv(socks[0], &dummy, 1, 0); shutdown(socks[1], SHUT_WR); } ``` when racing like this: ``` thread1 thread2 unix_stream_read_generic mutex_lock(&u->iolock) skb_peek(&sk->sk_receive_queue) skb_peek_next(skb, &sk->sk_receive_queue) mutex_unlock(&u->iolock) unix_stream_read_generic unix_state_lock(sk) skb_peek(&sk->sk_receive_queue) unix_state_unlock(sk) unix_stream_data_wait unix_state_lock(sk) tail = skb_peek_tail(&sk->sk_receive_queue) spin_lock(&sk->sk_receive_queue.lock) __skb_unlink(skb, &sk->sk_receive_queue) spin_unlock(&sk->sk_receive_queue.lock) consume_skb(skb) [frees the SKB] `tail != last`: false `tail`: true `tail->len != last_len` ***UAF*** ``` Fix the UAF by removing the read of tail->len; checking tail->len would only make sense if SKBs in the receive queue of a UNIX socket could grow, which can no longer happen. Kuniyuki explained: > When commit 869e7c62486e ("net: af_unix: implement stream sendpage > support") added sendpage() support, data could be appended to the last > skb in the receiver's queue. > > That's why we needed to check if the length of the last skb was changed > while waiting for new data in unix_stream_data_wait(). > > However, commit a0dbf5f818f9 ("af_unix: Support MSG_SPLICE_PAGES") and > commit 57d44a354a43 ("unix: Convert unix_stream_sendpage() to use > MSG_SPLICE_PAGES") refactored sendmsg(), and now data is always added > to a new skb. That means this fix is not suitable for kernels before 6.5.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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 → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-416
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 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-64100 Référence CVE CVE-2026-64101 https://www.cve.org/CVERecord?id=CVE-2026-64101 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64103 https://www.cve.org/CVERecord?id=CVE-2026-64103 Référence CVE CVE-2026-64104 https://www.cve.org/CVERecord?id=CVE-2026-64104 Référence CVE CVE-2026-64105 https://www.cve.org/CVERecord?id=CVE-2026-64105 Référence CVE CVE-2026-64106 https://www.cve.org/CVERecord?id=CVE-2026-64106 Référence CVE CVE-2026-64107 https://www.cve.org/CVERecord?id=CVE-2026-64107 Référence CVE CVE-2026-64108 https://www.cve.org/CVERecord?id=CVE-2026-64108 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64110 https://www.cve.org/CVERecord?id=CVE-2026-64110 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64089 Référence CVE CVE-2026-64093 https://www.cve.org/CVERecord?id=CVE-2026-64093 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=CVE-2026-64097 Référence CVE CVE-2026-64098 https://www.cve.org/CVERecord?id=CVE-2026-64098 Référence CVE CVE-2026-64099 https://www.cve.org/CVERecord?id=CVE-2026-64099 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64103 https://www.cve.org/CVERecord?id=CVE-2026-64103 Référence CVE CVE-2026-64104 https://www.cve.org/CVERecord?id=CVE-2026-64104 Référence CVE CVE-2026-64105 https://www.cve.org/CVERecord?id=CVE-2026-64105 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64121 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-64100 Référence CVE CVE-2026-64101 https://www.cve.org/CVERecord?id=CVE-2026-64101 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64103 https://www.cve.org/CVERecord?id=CVE-2026-64103 Référence CVE CVE-2026-64104 https://www.cve.org/CVERecord?id=CVE-2026-64104 Référence CVE CVE-2026-64105 https://www.cve.org/CVERecord?id=CVE-2026-64105 Référence CVE CVE-2026-64106 https://www.cve.org/CVERecord?id=CVE-2026-64106 Référence CVE CVE-2026-64107 https://www.cve.org/CVERecord?id=CVE-2026-64107 Référence CVE CVE-2026-64108 https://www.cve.org/CVERecord?id=CVE-2026-64108 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64110 https://www.cve.org/CVERecord?id=CVE-2026-64110 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 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-64007 Référence CVE CVE-2026-64010 https://www.cve.org/CVERecord?id=CVE-2026-64010 Référence CVE CVE-2026-64011 https://www.cve.org/CVERecord?id=CVE-2026-64011 Référence CVE CVE-2026-64015 https://www.cve.org/CVERecord?id=CVE-2026-64015 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64098 https://www.cve.org/CVERecord?id=CVE-2026-64098 Référence CVE CVE-2026-64103 https://www.cve.org/CVERecord?id=CVE-2026-64103 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64137 https://www.cve.org/CVERecord?id=CVE-2026-64137 Référence CVE CVE-2026-64164 https://www.cve.org/CVERecord?id=CVE-2026-64164 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64190 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=CVE-2026-64097 Référence CVE CVE-2026-64098 https://www.cve.org/CVERecord?id=CVE-2026-64098 Référence CVE CVE-2026-64099 https://www.cve.org/CVERecord?id=CVE-2026-64099 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 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-64093 Référence CVE CVE-2026-64096 https://www.cve.org/CVERecord?id=CVE-2026-64096 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=CVE-2026-64097 Référence CVE CVE-2026-64098 https://www.cve.org/CVERecord?id=CVE-2026-64098 Référence CVE CVE-2026-64099 https://www.cve.org/CVERecord?id=CVE-2026-64099 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64103 https://www.cve.org/CVERecord?id=CVE-2026-64103 Référence CVE CVE-2026-64106 https://www.cve.org/CVERecord?id=CVE-2026-64106 Référence CVE CVE-2026-64108 https://www.cve.org/CVERecord?id=CVE-2026-64108 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 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-64100 Référence CVE CVE-2026-64101 https://www.cve.org/CVERecord?id=CVE-2026-64101 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64103 https://www.cve.org/CVERecord?id=CVE-2026-64103 Référence CVE CVE-2026-64104 https://www.cve.org/CVERecord?id=CVE-2026-64104 Référence CVE CVE-2026-64105 https://www.cve.org/CVERecord?id=CVE-2026-64105 Référence CVE CVE-2026-64106 https://www.cve.org/CVERecord?id=CVE-2026-64106 Référence CVE CVE-2026-64107 https://www.cve.org/CVERecord?id=CVE-2026-64107 Référence CVE CVE-2026-64108 https://www.cve.org/CVERecord?id=CVE-2026-64108 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64110 https://www.cve.org/CVERecord?id=CVE-2026-64110 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=CVE-2026-64097 Référence CVE CVE-2026-64098 https://www.cve.org/CVERecord?id=CVE-2026-64098 Référence CVE CVE-2026-64099 https://www.cve.org/CVERecord?id=CVE-2026-64099 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 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-64100 Référence CVE CVE-2026-64101 https://www.cve.org/CVERecord?id=CVE-2026-64101 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64103 https://www.cve.org/CVERecord?id=CVE-2026-64103 Référence CVE CVE-2026-64104 https://www.cve.org/CVERecord?id=CVE-2026-64104 Référence CVE CVE-2026-64105 https://www.cve.org/CVERecord?id=CVE-2026-64105 Référence CVE CVE-2026-64106 https://www.cve.org/CVERecord?id=CVE-2026-64106 Référence CVE CVE-2026-64107 https://www.cve.org/CVERecord?id=CVE-2026-64107 Référence CVE CVE-2026-64108 https://www.cve.org/CVERecord?id=CVE-2026-64108 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64110 https://www.cve.org/CVERecord?id=CVE-2026-64110 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 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-64100 Référence CVE CVE-2026-64101 https://www.cve.org/CVERecord?id=CVE-2026-64101 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64103 https://www.cve.org/CVERecord?id=CVE-2026-64103 Référence CVE CVE-2026-64104 https://www.cve.org/CVERecord?id=CVE-2026-64104 Référence CVE CVE-2026-64105 https://www.cve.org/CVERecord?id=CVE-2026-64105 Référence CVE CVE-2026-64106 https://www.cve.org/CVERecord?id=CVE-2026-64106 Référence CVE CVE-2026-64107 https://www.cve.org/CVERecord?id=CVE-2026-64107 Référence CVE CVE-2026-64108 https://www.cve.org/CVERecord?id=CVE-2026-64108 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64110 https://www.cve.org/CVERecord?id=CVE-2026-64110 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 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-64100 Référence CVE CVE-2026-64101 https://www.cve.org/CVERecord?id=CVE-2026-64101 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64103 https://www.cve.org/CVERecord?id=CVE-2026-64103 Référence CVE CVE-2026-64104 https://www.cve.org/CVERecord?id=CVE-2026-64104 Référence CVE CVE-2026-64105 https://www.cve.org/CVERecord?id=CVE-2026-64105 Référence CVE CVE-2026-64106 https://www.cve.org/CVERecord?id=CVE-2026-64106 Référence CVE CVE-2026-64107 https://www.cve.org/CVERecord?id=CVE-2026-64107 Référence CVE CVE-2026-64108 https://www.cve.org/CVERecord?id=CVE-2026-64108 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64110 https://www.cve.org/CVERecord?id=CVE-2026-64110 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-028071LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおいて、次の脆弱性が修正されました。af_unix：unix_stream_data_wait()内のtail-＞lenのUse-After-Free（UAF）読み取りの修正です。unix_stream_data_wait()は、スケジューリングロックを持たずにskb_peek_tail(&sk-＞sk_receive_queue)を実行します。このため、そのキュー上のSKBがデキューされて解放されるのを防ぐことができません。この状態はコミット79f632c71bea（"unix/stream: fix peeking with an offset larger than data in queue"）以降ずっと続いています。その結果、ポインタ比較の`tail != last`が、`last`が既に解放されたSKBを指しているにもかかわらず、`tail`が同じアドレスに割り当てられた新しいSKBであった場合に偽となることがあります。これにより、unix_stream_data_wait()が新しいデータ到着後も不適切にブロックし続ける可能性がありますが、これは同じソケットに対してpeekしながらのrecv()と通常のrecv()が競合するという稀なシナリオでのみ発生し、おそらく実質的な問題にはなりません。とはいえ、コミット2b514574f7e8（"net: af_unix: implement splice for stream af_unix sockets"）以降では`tail`が実際に参照されるようになり、以下の競合シナリオにてUAFが発生する可能性があります。（test_setup()がシングルスレッドで実行され、その後test_thread1()とtest_thread2()が2つのスレッドで並行して実行される）:```cstatic int socks[2];void test_setup(void) { socketpair(AF_UNIX, SOCK_STREAM, 0, socks); send(socks[1], "A", 1, 0); int peekoff = 1; setsockopt(socks[0], SOL_SOCKET, SO_PEEK_OFF, &peekoff, sizeof(peekoff));}void test_thread1(void) { char dummy; recv(socks[0], &dummy, 1, MSG_PEEK);}void test_thread2(void) { char dummy; recv(socks[0], &dummy, 1, 0); shutdown(socks[1], SHUT_WR);}```競合時の動作例：``` thread1 thread2unix_stream_read_generic mutex_lock(&u-＞iolock) skb_peek(&sk-＞sk_receive_queue) skb_peek_next(skb, &sk-＞sk_receive_queue) mutex_unlock(&u-＞iolock) unix_stream_read_generic unix_state_lock(sk) skb_peek(&sk-＞sk_receive_queue) unix_state_unlock(sk) unix_stream_data_wait unix_state_lock(sk) tail = skb_peek_tail(&sk-＞sk_receive_queue) spin_lock(&sk-＞sk_receive_queue.lock) __skb_unlink(skb, &sk-＞sk_receive_queue) spin_unlock(&sk-＞sk_receive_queue.lock) consume_skb(skb) [SKBの解放] `tail != last`: false `tail`: true `tail-＞len != last_len`***UAF発生***```このUAFは、tail-＞lenの読み取りを削除することで修正されました。UNIXソケットの受信キュー内のSKBが拡大する可能性はもはやないため、tail-＞lenをチェックする必要がなくなったからです。Kuniyuki氏は以下のように説明しています。＞ コミット869e7c62486e（"net: af_unix: implement stream sendpage support"）でsendpage()サポートが追加された際、受信側キューの最後のskbにデータが追加される可能性がありました。＞ そのため、unix_stream_data_wait()で新しいデータを待つ間に、最後のskbの長さが変わったかをチェックする必要がありました。＞ しかし、コミットa0dbf5f818f9（"af_unix: Support MSG_SPLICE_PAGES"）とコミット57d44a354a43（"unix: Convert unix_stream_sendpage() to use MSG_SPLICE_PAGES"）でsendmsg()のリファクタリングが行われ、現在はデータは常に新しいskbに追加されることになりました。＞ したがって、この修正はカーネル6.5以前には適用されません。

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.2, 6.6.143 ≤ 6.6.*, 6.12.92 ≤ 6.12.*, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 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 19 Jul 2026 · Last source change 5 Aug 2026, 12:39 UTC · CWE-416 · Use After Free

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-45794
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1; 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; and 224 more · Fixed: cluster-md-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; dlm-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; gfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-64kb-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-64kb-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-base-5.14.21-150500.55.189.1.150500.6.87.4 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-docs-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-macros-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-obs-build-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-source-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-syms-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; ocfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; cluster-md-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; dlm-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; gfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-64kb-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-64kb-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-base-5.14.21-150500.55.189.1.150500.6.87.4 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-docs-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-macros-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-obs-build-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-source-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-syms-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; ocfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; and 134 more
    After
    kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1; 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; and 227 more
    SUSE Product Security Team ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1; 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; and 224 more · Fixed: cluster-md-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; dlm-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; gfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-64kb-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-64kb-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-base-5.14.21-150500.55.189.1.150500.6.87.4 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-docs-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-macros-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-obs-build-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-source-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-syms-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; ocfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; cluster-md-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; dlm-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; gfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-64kb-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-64kb-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-base-5.14.21-150500.55.189.1.150500.6.87.4 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-docs-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-macros-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-obs-build-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-source-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-syms-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; ocfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; and 137 more
    After
    kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1; 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; and 224 more · Fixed: cluster-md-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; dlm-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; gfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-64kb-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-64kb-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-base-5.14.21-150500.55.189.1.150500.6.87.4 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-docs-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-macros-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-obs-build-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-source-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-syms-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; ocfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; cluster-md-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; dlm-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; gfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-64kb-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-64kb-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-base-5.14.21-150500.55.189.1.150500.6.87.4 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-docs-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-macros-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-obs-build-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-source-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-syms-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; ocfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; and 134 more
    SUSE Product Security Team ↗
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-45794↗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.
Free version - for non-commercial use only.CVE-2026-64109 · cve.blacktree.nl