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

rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

23 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.10-1Debian Security Tracker ↗Source updated 6 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-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-2025-21635 · CSAF 2.0 · revision 59 · interimSUSE Product Security TeamCVE-2025-21635
382 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
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. - current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acct(2). The per-netns structure can be obtained from the table->data using container_of(), then the 'net' one can be retrieved from the listen socket (if available).
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-2025-2584

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. - current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acct(2). The per-netns structure can be obtained from the table->data using container_of(), then the 'net' one can be retrieved from the listen socket (if available).

What

In the Linux kernel, the following vulnerability has been resolved: rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. - current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acct(2). The per-netns structure can be obtained from the table->data using container_of(), then the 'net' one can be retrieved from the listen socket (if available).

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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: rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy As mentioned in a previous commit of this series, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. - current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acct(2). The per-netns structure can be obtained from the table->data using container_of(), then the 'net' one can be retrieved from the listen socket (if available).

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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 → NULL Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.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
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-476
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-1439Dell Secure Connect Gateway: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-0119Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Auswirkungen zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250122Security Bulletin 22 Jan 2025

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

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

d?id=CVE-2025-14524 Référence CVE CVE-2025-14831 https://www.cve.org/CVERecord?id=CVE-2025-14831 Référence CVE CVE-2025-15079 https://www.cve.org/CVERecord?id=CVE-2025-15079 Référence CVE CVE-2025-15224 https://www.cve.org/CVERecord?id=CVE-2025-15224 Référence CVE CVE-2025-15467 https://www.cve.org/CVERecord?id=CVE-2025-15467 Référence CVE CVE-2025-15468 https://www.cve.org/CVERecord?id=CVE-2025-15468 Référence CVE CVE-2025-15469 https://www.cve.org/CVERecord?id=CVE-2025-15469 Référence CVE CVE-2025-21629 https://www.cve.org/CVERecord?id=CVE-2025-21629 Référence CVE CVE-2025-21634 https://www.cve.org/CVERecord?id=CVE-2025-21634 Référence CVE CVE-2025-21635 https://www.cve.org/CVERecord?id=CVE-2025-21635 Référence CVE CVE-2025-21645 https://www.cve.org/CVERecord?id=CVE-2025-21645 Référence CVE CVE-2025-21649 https://www.cve.org/CVERecord?id=CVE-2025-21649 Référence CVE CVE-2025-21651 https://www.cve.org/CVERecord?id=CVE-2025-21651 Référence CVE CVE-2025-21656 https://www.cve.org/CVERecord?id=CVE-2025-21656 Référence CVE CVE-2025-21658 https://www.cve.org/CVERecord?id=CVE-2025-21658 Référence CVE CVE-2025-21667 https://www.cve.org/CVERecord?id=CVE-2025-21667 Référence CVE CVE-2025-21672 https://www.cve.org/CVERecord?id=CVE-2025-21672 Référence CVE CVE-2025-21673 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-14524 Référence CVE CVE-2025-14831 https://www.cve.org/CVERecord?id=CVE-2025-14831 Référence CVE CVE-2025-15079 https://www.cve.org/CVERecord?id=CVE-2025-15079 Référence CVE CVE-2025-15224 https://www.cve.org/CVERecord?id=CVE-2025-15224 Référence CVE CVE-2025-15467 https://www.cve.org/CVERecord?id=CVE-2025-15467 Référence CVE CVE-2025-15468 https://www.cve.org/CVERecord?id=CVE-2025-15468 Référence CVE CVE-2025-15469 https://www.cve.org/CVERecord?id=CVE-2025-15469 Référence CVE CVE-2025-21629 https://www.cve.org/CVERecord?id=CVE-2025-21629 Référence CVE CVE-2025-21634 https://www.cve.org/CVERecord?id=CVE-2025-21634 Référence CVE CVE-2025-21635 https://www.cve.org/CVERecord?id=CVE-2025-21635 Référence CVE CVE-2025-21645 https://www.cve.org/CVERecord?id=CVE-2025-21645 Référence CVE CVE-2025-21649 https://www.cve.org/CVERecord?id=CVE-2025-21649 Référence CVE CVE-2025-21651 https://www.cve.org/CVERecord?id=CVE-2025-21651 Référence CVE CVE-2025-21656 https://www.cve.org/CVERecord?id=CVE-2025-21656 Référence CVE CVE-2025-21658 https://www.cve.org/CVERecord?id=CVE-2025-21658 Référence CVE CVE-2025-21667 https://www.cve.org/CVERecord?id=CVE-2025-21667 Référence CVE CVE-2025-21672 https://www.cve.org/CVERecord?id=CVE-2025-21672 Référence CVE CVE-2025-21673 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-58094 Référence CVE CVE-2024-58095 https://www.cve.org/CVERecord?id=CVE-2024-58095 Référence CVE CVE-2024-58096 https://www.cve.org/CVERecord?id=CVE-2024-58096 Référence CVE CVE-2024-58097 https://www.cve.org/CVERecord?id=CVE-2024-58097 Référence CVE CVE-2024-58098 https://www.cve.org/CVERecord?id=CVE-2024-58098 Référence CVE CVE-2024-58099 https://www.cve.org/CVERecord?id=CVE-2024-58099 Référence CVE CVE-2024-58100 https://www.cve.org/CVERecord?id=CVE-2024-58100 Référence CVE CVE-2024-58237 https://www.cve.org/CVERecord?id=CVE-2024-58237 Référence CVE CVE-2025-21629 https://www.cve.org/CVERecord?id=CVE-2025-21629 Référence CVE CVE-2025-21635 https://www.cve.org/CVERecord?id=CVE-2025-21635 Référence CVE CVE-2025-21648 https://www.cve.org/CVERecord?id=CVE-2025-21648 Référence CVE CVE-2025-21659 https://www.cve.org/CVERecord?id=CVE-2025-21659 Référence CVE CVE-2025-21680 https://www.cve.org/CVERecord?id=CVE-2025-21680 Référence CVE CVE-2025-21683 https://www.cve.org/CVERecord?id=CVE-2025-21683 Référence CVE CVE-2025-21693 https://www.cve.org/CVERecord?id=CVE-2025-21693 Référence CVE CVE-2025-21696 https://www.cve.org/CVERecord?id=CVE-2025-21696 Référence CVE CVE-2025-21701 https://www.cve.org/CVERecord?id=CVE-2025-21701 Référence CVE CVE-2025-21702 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-58085 Référence CVE CVE-2024-58086 https://www.cve.org/CVERecord?id=CVE-2024-58086 Référence CVE CVE-2024-58088 https://www.cve.org/CVERecord?id=CVE-2024-58088 Référence CVE CVE-2024-58093 https://www.cve.org/CVERecord?id=CVE-2024-58093 Référence CVE CVE-2024-58094 https://www.cve.org/CVERecord?id=CVE-2024-58094 Référence CVE CVE-2024-58095 https://www.cve.org/CVERecord?id=CVE-2024-58095 Référence CVE CVE-2024-58096 https://www.cve.org/CVERecord?id=CVE-2024-58096 Référence CVE CVE-2024-58097 https://www.cve.org/CVERecord?id=CVE-2024-58097 Référence CVE CVE-2025-21631 https://www.cve.org/CVERecord?id=CVE-2025-21631 Référence CVE CVE-2025-21635 https://www.cve.org/CVERecord?id=CVE-2025-21635 Référence CVE CVE-2025-21648 https://www.cve.org/CVERecord?id=CVE-2025-21648 Référence CVE CVE-2025-21659 https://www.cve.org/CVERecord?id=CVE-2025-21659 Référence CVE CVE-2025-21671 https://www.cve.org/CVERecord?id=CVE-2025-21671 Référence CVE CVE-2025-21680 https://www.cve.org/CVERecord?id=CVE-2025-21680 Référence CVE CVE-2025-21683 https://www.cve.org/CVERecord?id=CVE-2025-21683 Référence CVE CVE-2025-21693 https://www.cve.org/CVERecord?id=CVE-2025-21693 Référence CVE CVE-2025-21696 https://www.cve.org/CVERecord?id=CVE-2025-21696 Référence CVE CVE-2025-21701 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-58068 Référence CVE CVE-2024-58070 https://www.cve.org/CVERecord?id=CVE-2024-58070 Référence CVE CVE-2024-58071 https://www.cve.org/CVERecord?id=CVE-2024-58071 Référence CVE CVE-2024-58088 https://www.cve.org/CVERecord?id=CVE-2024-58088 Référence CVE CVE-2024-58093 https://www.cve.org/CVERecord?id=CVE-2024-58093 Référence CVE CVE-2024-58094 https://www.cve.org/CVERecord?id=CVE-2024-58094 Référence CVE CVE-2024-58095 https://www.cve.org/CVERecord?id=CVE-2024-58095 Référence CVE CVE-2024-58096 https://www.cve.org/CVERecord?id=CVE-2024-58096 Référence CVE CVE-2024-58097 https://www.cve.org/CVERecord?id=CVE-2024-58097 Référence CVE CVE-2025-21635 https://www.cve.org/CVERecord?id=CVE-2025-21635 Référence CVE CVE-2025-21683 https://www.cve.org/CVERecord?id=CVE-2025-21683 Référence CVE CVE-2025-21696 https://www.cve.org/CVERecord?id=CVE-2025-21696 Référence CVE CVE-2025-21707 https://www.cve.org/CVERecord?id=CVE-2025-21707 Référence CVE CVE-2025-21726 https://www.cve.org/CVERecord?id=CVE-2025-21726 Référence CVE CVE-2025-21729 https://www.cve.org/CVERecord?id=CVE-2025-21729 Référence CVE CVE-2025-21735 https://www.cve.org/CVERecord?id=CVE-2025-21735 Référence CVE CVE-2025-21750 https://www.cve.org/CVERecord?id=CVE-2025-21750 Référence CVE CVE-2025-21755 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-58072 Référence CVE CVE-2024-58076 https://www.cve.org/CVERecord?id=CVE-2024-58076 Référence CVE CVE-2024-58078 https://www.cve.org/CVERecord?id=CVE-2024-58078 Référence CVE CVE-2024-58079 https://www.cve.org/CVERecord?id=CVE-2024-58079 Référence CVE CVE-2024-58080 https://www.cve.org/CVERecord?id=CVE-2024-58080 Référence CVE CVE-2024-58083 https://www.cve.org/CVERecord?id=CVE-2024-58083 Référence CVE CVE-2024-58085 https://www.cve.org/CVERecord?id=CVE-2024-58085 Référence CVE CVE-2024-58086 https://www.cve.org/CVERecord?id=CVE-2024-58086 Référence CVE CVE-2025-21631 https://www.cve.org/CVERecord?id=CVE-2025-21631 Référence CVE CVE-2025-21635 https://www.cve.org/CVERecord?id=CVE-2025-21635 Référence CVE CVE-2025-21659 https://www.cve.org/CVERecord?id=CVE-2025-21659 Référence CVE CVE-2025-21671 https://www.cve.org/CVERecord?id=CVE-2025-21671 Référence CVE CVE-2025-21693 https://www.cve.org/CVERecord?id=CVE-2025-21693 Référence CVE CVE-2025-21701 https://www.cve.org/CVERecord?id=CVE-2025-21701 Référence CVE CVE-2025-21703 https://www.cve.org/CVERecord?id=CVE-2025-21703 Référence CVE CVE-2025-21704 https://www.cve.org/CVERecord?id=CVE-2025-21704 Référence CVE CVE-2025-21706 https://www.cve.org/CVERecord?id=CVE-2025-21706 Référence CVE CVE-2025-21708 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2024-57945 Référence CVE CVE-2024-57946 https://www.cve.org/CVERecord?id=CVE-2024-57946 Référence CVE CVE-2024-58087 https://www.cve.org/CVERecord?id=CVE-2024-58087 Référence CVE CVE-2025-0927 https://www.cve.org/CVERecord?id=CVE-2025-0927 Référence CVE CVE-2025-21629 https://www.cve.org/CVERecord?id=CVE-2025-21629 Référence CVE CVE-2025-21631 https://www.cve.org/CVERecord?id=CVE-2025-21631 Référence CVE CVE-2025-21632 https://www.cve.org/CVERecord?id=CVE-2025-21632 Référence CVE CVE-2025-21633 https://www.cve.org/CVERecord?id=CVE-2025-21633 Référence CVE CVE-2025-21634 https://www.cve.org/CVERecord?id=CVE-2025-21634 Référence CVE CVE-2025-21635 https://www.cve.org/CVERecord?id=CVE-2025-21635 Référence CVE CVE-2025-21636 https://www.cve.org/CVERecord?id=CVE-2025-21636 Référence CVE CVE-2025-21637 https://www.cve.org/CVERecord?id=CVE-2025-21637 Référence CVE CVE-2025-21638 https://www.cve.org/CVERecord?id=CVE-2025-21638 Référence CVE CVE-2025-21639 https://www.cve.org/CVERecord?id=CVE-2025-21639 Référence CVE CVE-2025-21640 https://www.cve.org/CVERecord?id=CVE-2025-21640 Référence CVE CVE-2025-21642 https://www.cve.org/CVERecord?id=CVE-2025-21642 Référence CVE CVE-2025-21643 https://www.cve.org/CVERecord?id=CVE-2025-21643 Référence CVE CVE-2025-21644 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-002198Linux の Linux Kernel における NULL ポインタデリファレンスに関する脆弱性

Linux の Linux Kernel には、NULL ポインタデリファレンスに関する脆弱性が存在します。

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.6, 6.12.10 ≤ 6.12.*, 6.13 ≤ *
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 Jan 2025 · Last source change 11 May 2026, 21:03 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-2025-2584
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗

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-2025-2584↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-2025-21635 · cve.blacktree.nl