BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-50865High confidence

tcp: fix a signed-integer-overflow bug in tcp_add_backlog()

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.53% for the current model date.

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

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

13 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 9 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.0.7-1Debian Security Tracker ↗Source updated 23 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.7-1Debian Security Tracker ↗Source updated 23 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.7-1Debian Security Tracker ↗Source updated 23 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.7-1Debian Security Tracker ↗Source updated 23 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-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 23 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-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 23 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-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 23 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-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 23 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-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 23 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 23 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 23 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 23 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 23 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-2022-50865 · CSAF 2.0 · revision 24 · interimSUSE Product Security TeamCVE-2022-50865
309 known affected

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

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() The type of sk_rcvbuf and sk_sndbuf in struct sock is int, and in tcp_add_backlog(), the variable limit is caculated by adding sk_rcvbuf, sk_sndbuf and 64 * 1024, it may exceed the max value of int and overflow. This patch reduces the limit budget by halving the sndbuf to solve this issue since ACK packets are much smaller than the payload.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2022-50865 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: tcp: fix a signed-integer-overflow bug in tcp_add_backlog()
106 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 9
  • kernel as a component of Red Hat Enterprise Linux 9
  • kernel-64k as a component of Red Hat Enterprise Linux 9
  • kernel-64k-core as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules-internal as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in the Linux kernel’s TCP implementation in the function tcp_add_backlog(). When calculating the maximum acceptable backlog for TCP sockets, the sum of the receive buffer (sk_rcvbuf), the send buffer (sk_sndbuf), and a fixed constant may exceed the maximum value of a signed integer due to both buffer values being of type int. This can result in a signed integer overflow, potentially leading to incorrect backlog limits and unexpected TCP behavior under certain workloads.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
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-2022-55833

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 9 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: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() The type of sk_rcvbuf and sk_sndbuf in struct sock is int, and in tcp_add_backlog(), the variable limit is caculated by adding sk_rcvbuf, sk_sndbuf and 64 * 1024, it may exceed the max value of int and overflow. This patch reduces the limit budget by halving the sndbuf to solve this issue since ACK packets are much smaller than the payload.

What

In the Linux kernel, the following vulnerability has been resolved: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() The type of sk_rcvbuf and sk_sndbuf in struct sock is int, and in tcp_add_backlog(), the variable limit is caculated by adding sk_rcvbuf, sk_sndbuf and 64 * 1024, it may exceed the max value of int and overflow. This patch reduces the limit budget by halving the sndbuf to solve this issue since ACK packets are much smaller than the payload.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() The type of sk_rcvbuf and sk_sndbuf in struct sock is int, and in tcp_add_backlog(), the variable limit is caculated by adding sk_rcvbuf, sk_sndbuf and 64 * 1024, it may exceed the max value of int and overflow. This patch reduces the limit budget by halving the sndbuf to solve this issue since ACK packets are much smaller than the payload.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

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
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticated
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-0783IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Programmcode auszuführen, um Informationen offenzulegen, um einen Denial of Service Angriff durchzuführen, um einen Cross-Site Scripting Angriff durchzuführen, und um Dateien zu manipulieren.

Official advisory ↗
BSI · German · WID-SEC-2025-2941Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann diese Schwachstellen ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu Denial‑of‑Service, Speicherbeschädigung oder weiteren nicht definierten Auswirkungen führen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251231Security Bulletin 31 Dec 2025

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

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

ort/pages/node/7266518 Bulletin de sécurité IBM 7266520 du 17 mars 2026 https://www.ibm.com/support/pages/node/7266520 Bulletin de sécurité IBM 7266677 du 18 mars 2026 https://www.ibm.com/support/pages/node/7266677 Bulletin de sécurité IBM 7266678 du 18 mars 2026 https://www.ibm.com/support/pages/node/7266678 Bulletin de sécurité IBM 7266711 du 18 mars 2026 https://www.ibm.com/support/pages/node/7266711 Référence CVE CVE-2020-7660 https://www.cve.org/CVERecord?id=CVE-2020-7660 Référence CVE CVE-2022-46337 https://www.cve.org/CVERecord?id=CVE-2022-46337 Référence CVE CVE-2022-50673 https://www.cve.org/CVERecord?id=CVE-2022-50673 Référence CVE CVE-2022-50865 https://www.cve.org/CVERecord?id=CVE-2022-50865 Référence CVE CVE-2023-44483 https://www.cve.org/CVERecord?id=CVE-2023-44483 Référence CVE CVE-2023-53552 https://www.cve.org/CVERecord?id=CVE-2023-53552 Référence CVE CVE-2024-11831 https://www.cve.org/CVERecord?id=CVE-2024-11831 Référence CVE CVE-2024-26766 https://www.cve.org/CVERecord?id=CVE-2024-26766 Référence CVE CVE-2024-29371 https://www.cve.org/CVERecord?id=CVE-2024-29371 Référence CVE CVE-2024-45296 https://www.cve.org/CVERecord?id=CVE-2024-45296 Référence CVE CVE-2024-47831 https://www.cve.org/CVERecord?id=CVE-2024-47831 Référence CVE CVE-2024-51479 https://www.cve.org/CVERecord?id=

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

277 Bulletin de sécurité Red Hat RHSA-2026:3293 du 25 février 2026 https://access.redhat.com/errata/RHSA-2026:3293 Bulletin de sécurité Red Hat RHSA-2026:3358 du 25 février 2026 https://access.redhat.com/errata/RHSA-2026:3358 Bulletin de sécurité Red Hat RHSA-2026:3360 du 25 février 2026 https://access.redhat.com/errata/RHSA-2026:3360 Bulletin de sécurité Red Hat RHSA-2026:3375 du 25 février 2026 https://access.redhat.com/errata/RHSA-2026:3375 Bulletin de sécurité Red Hat RHSA-2026:3388 du 26 février 2026 https://access.redhat.com/errata/RHSA-2026:3388 Référence CVE CVE-2022-50673 https://www.cve.org/CVERecord?id=CVE-2022-50673 Référence CVE CVE-2022-50865 https://www.cve.org/CVERecord?id=CVE-2022-50865 Référence CVE CVE-2023-53192 https://www.cve.org/CVERecord?id=CVE-2023-53192 Référence CVE CVE-2023-53513 https://www.cve.org/CVERecord?id=CVE-2023-53513 Référence CVE CVE-2023-53539 https://www.cve.org/CVERecord?id=CVE-2023-53539 Référence CVE CVE-2023-53581 https://www.cve.org/CVERecord?id=CVE-2023-53581 Référence CVE CVE-2023-53673 https://www.cve.org/CVERecord?id=CVE-2023-53673 Référence CVE CVE-2023-53762 https://www.cve.org/CVERecord?id=CVE-2023-53762 Référence CVE CVE-2023-53821 https://www.cve.org/CVERecord?id=CVE-2023-53821 Référence CVE CVE-2023-53827 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-50850 Référence CVE CVE-2022-50851 https://www.cve.org/CVERecord?id=CVE-2022-50851 Référence CVE CVE-2022-50853 https://www.cve.org/CVERecord?id=CVE-2022-50853 Référence CVE CVE-2022-50856 https://www.cve.org/CVERecord?id=CVE-2022-50856 Référence CVE CVE-2022-50858 https://www.cve.org/CVERecord?id=CVE-2022-50858 Référence CVE CVE-2022-50859 https://www.cve.org/CVERecord?id=CVE-2022-50859 Référence CVE CVE-2022-50860 https://www.cve.org/CVERecord?id=CVE-2022-50860 Référence CVE CVE-2022-50861 https://www.cve.org/CVERecord?id=CVE-2022-50861 Référence CVE CVE-2022-50864 https://www.cve.org/CVERecord?id=CVE-2022-50864 Référence CVE CVE-2022-50865 https://www.cve.org/CVERecord?id=CVE-2022-50865 Référence CVE CVE-2022-50866 https://www.cve.org/CVERecord?id=CVE-2022-50866 Référence CVE CVE-2022-50868 https://www.cve.org/CVERecord?id=CVE-2022-50868 Référence CVE CVE-2022-50870 https://www.cve.org/CVERecord?id=CVE-2022-50870 Référence CVE CVE-2022-50872 https://www.cve.org/CVERecord?id=CVE-2022-50872 Référence CVE CVE-2022-50876 https://www.cve.org/CVERecord?id=CVE-2022-50876 Référence CVE CVE-2022-50878 https://www.cve.org/CVERecord?id=CVE-2022-50878 Référence CVE CVE-2022-50880 https://www.cve.org/CVERecord?id=CVE-2022-50880 Référence CVE CVE-2022-50881 https://www.cve.org/CVERecord?id=

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

2577 du 11 février 2026 https://access.redhat.com/errata/RHSA-2026:2577 Bulletin de sécurité Red Hat RHSA-2026:2583 du 11 février 2026 https://access.redhat.com/errata/RHSA-2026:2583 Bulletin de sécurité Red Hat RHSA-2026:2594 du 12 février 2026 https://access.redhat.com/errata/RHSA-2026:2594 Bulletin de sécurité Red Hat RHSA-2026:2664 du 12 février 2026 https://access.redhat.com/errata/RHSA-2026:2664 Référence CVE CVE-2022-49503 https://www.cve.org/CVERecord?id=CVE-2022-49503 Référence CVE CVE-2022-50341 https://www.cve.org/CVERecord?id=CVE-2022-50341 Référence CVE CVE-2022-50673 https://www.cve.org/CVERecord?id=CVE-2022-50673 Référence CVE CVE-2022-50865 https://www.cve.org/CVERecord?id=CVE-2022-50865 Référence CVE CVE-2023-53192 https://www.cve.org/CVERecord?id=CVE-2023-53192 Référence CVE CVE-2023-53539 https://www.cve.org/CVERecord?id=CVE-2023-53539 Référence CVE CVE-2023-53581 https://www.cve.org/CVERecord?id=CVE-2023-53581 Référence CVE CVE-2023-53673 https://www.cve.org/CVERecord?id=CVE-2023-53673 Référence CVE CVE-2023-53751 https://www.cve.org/CVERecord?id=CVE-2023-53751 Référence CVE CVE-2023-53833 https://www.cve.org/CVERecord?id=CVE-2023-53833 Référence CVE CVE-2024-54456 https://www.cve.org/CVERecord?id=CVE-2024-54456 Référence CVE CVE-2025-21647 https://www.cve.org/CVERecord?id=

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

tin de sécurité Red Hat RHSA-2026:1703 du 02 février 2026 https://access.redhat.com/errata/RHSA-2026:1703 Bulletin de sécurité Red Hat RHSA-2026:1886 du 04 février 2026 https://access.redhat.com/errata/RHSA-2026:1886 Bulletin de sécurité Red Hat RHSA-2026:1946 du 04 février 2026 https://access.redhat.com/errata/RHSA-2026:1946 Référence CVE CVE-2022-49290 https://www.cve.org/CVERecord?id=CVE-2022-49290 Référence CVE CVE-2022-49581 https://www.cve.org/CVERecord?id=CVE-2022-49581 Référence CVE CVE-2022-49667 https://www.cve.org/CVERecord?id=CVE-2022-49667 Référence CVE CVE-2022-50341 https://www.cve.org/CVERecord?id=CVE-2022-50341 Référence CVE CVE-2022-50865 https://www.cve.org/CVERecord?id=CVE-2022-50865 Référence CVE CVE-2023-53034 https://www.cve.org/CVERecord?id=CVE-2023-53034 Référence CVE CVE-2023-53539 https://www.cve.org/CVERecord?id=CVE-2023-53539 Référence CVE CVE-2023-53751 https://www.cve.org/CVERecord?id=CVE-2023-53751 Référence CVE CVE-2024-26766 https://www.cve.org/CVERecord?id=CVE-2024-26766 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-37789 https://www.cve.org/CVERecord?id=CVE-2025-37789 Référence CVE CVE-2025-37849 https://www.cve.org/CVERecord?id=CVE-2025-37849 Référence CVE CVE-2025-38022 https://www.cve.org/CVERecord?id=

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.9, 5.4.278 ≤ 5.4.*, 5.10.153 ≤ 5.10.*, 5.15.77 ≤ 5.15.*, 6.0.7 ≤ 6.0.*, 6.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 30 Dec 2025 · Last source change 5 Aug 2026, 08:59 UTC · CWE not yet assigned

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-2022-55833
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD not scheduled

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

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

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-2022-55833↗Vendor CSAF · SUSE Product Security Team↗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-2022-50865 · cve.blacktree.nl