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

tls: separate no-async decryption request handling from async

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 10 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 severityCriticalOperational priority:Critical, 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.33% 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 3 daysRemediation target: Within 90 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 10 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.7.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.153-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.9-1Debian Security Tracker ↗Source updated 5 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 5 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 5 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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, 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-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 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, 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
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-2024-58240 · CSAF 2.0 · revision 33 · interimSUSE Product Security TeamCVE-2024-58240
48 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default as component of SUSE Linux Enterprise Micro 5.0
  • kernel-default as component of SUSE Linux Enterprise Server 15 SP1-LTSS
  • kernel-default-base as component of SUSE Linux Enterprise Server 15 SP1-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise Server 15 SP1-LTSS
Summary
In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-032379 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-032379: Multiple Vulnerabilities in SIMATIC CN 4100 Before V5.0
1 known affected

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

  • SIMATIC CN 4100
Summary
In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.
Remediation
Update to V5.0 or later version
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-2024-54920

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.

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
9.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 10 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: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.

What

In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.

Why

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

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: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.

Why

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

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 → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-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:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

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.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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-416
A

Official authority intelligence

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

ENISA EUVD · EUVD-2024-54920Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.

Official EUVD record ↗
BSI · German · WID-SEC-2026-0349Dell Avamar und NetWorker: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Avamar und Dell NetWorker ausnutzen, um Angriffe zu starten, die die Integrität, Vertraulichkeit und Verfügbarkeit von Systemen beeinträchtigen.

Official advisory ↗
BSI · German · WID-SEC-2025-1921Linux Kernel: Schwachstelle ermöglicht Denial of Service

Ein lokaler Angreifer kann eine Schwachstelle in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250903Security Bulletin 03 Sep 2025

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

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

siemens.com/productcert/html/ssa-387223.html Bulletin de sécurité Siemens SSA-392349 du 12 mai 2026 https://cert-portal.siemens.com/productcert/html/ssa-392349.html Bulletin de sécurité Siemens SSA-688146 du 12 mai 2026 https://cert-portal.siemens.com/productcert/html/ssa-688146.html Bulletin de sécurité Siemens SSA-786884 du 12 mai 2026 https://cert-portal.siemens.com/productcert/html/ssa-786884.html Référence CVE CVE-2024-47704 https://www.cve.org/CVERecord?id=CVE-2024-47704 Référence CVE CVE-2024-54017 https://www.cve.org/CVERecord?id=CVE-2024-54017 Référence CVE CVE-2024-57924 https://www.cve.org/CVERecord?id=CVE-2024-57924 Référence CVE CVE-2024-58240 https://www.cve.org/CVERecord?id=CVE-2024-58240 Référence CVE CVE-2025-14831 https://www.cve.org/CVERecord?id=CVE-2025-14831 Référence CVE CVE-2025-23143 https://www.cve.org/CVERecord?id=CVE-2025-23143 Référence CVE CVE-2025-23160 https://www.cve.org/CVERecord?id=CVE-2025-23160 Référence CVE CVE-2025-31257 https://www.cve.org/CVERecord?id=CVE-2025-31257 Référence CVE CVE-2025-37931 https://www.cve.org/CVERecord?id=CVE-2025-37931 Référence CVE CVE-2025-37968 https://www.cve.org/CVERecord?id=CVE-2025-37968 Référence CVE CVE-2025-38322 https://www.cve.org/CVERecord?id=CVE-2025-38322 Référence CVE CVE-2025-38347 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53125 Référence CVE CVE-2023-53178 https://www.cve.org/CVERecord?id=CVE-2023-53178 Référence CVE CVE-2023-53185 https://www.cve.org/CVERecord?id=CVE-2023-53185 Référence CVE CVE-2023-53213 https://www.cve.org/CVERecord?id=CVE-2023-53213 Référence CVE CVE-2023-53305 https://www.cve.org/CVERecord?id=CVE-2023-53305 Référence CVE CVE-2023-53354 https://www.cve.org/CVERecord?id=CVE-2023-53354 Référence CVE CVE-2023-53373 https://www.cve.org/CVERecord?id=CVE-2023-53373 Référence CVE CVE-2023-53386 https://www.cve.org/CVERecord?id=CVE-2023-53386 Référence CVE CVE-2023-53513 https://www.cve.org/CVERecord?id=CVE-2023-53513 Référence CVE CVE-2024-58240 https://www.cve.org/CVERecord?id=CVE-2024-58240 Référence CVE CVE-2025-22026 https://www.cve.org/CVERecord?id=CVE-2025-22026 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-37797 https://www.cve.org/CVERecord?id=CVE-2025-37797 Référence CVE CVE-2025-37914 https://www.cve.org/CVERecord?id=CVE-2025-37914 Référence CVE CVE-2025-38200 https://www.cve.org/CVERecord?id=CVE-2025-38200 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38332 https://www.cve.org/CVERecord?id=CVE-2025-38332 Référence CVE CVE-2025-38449 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53173 Référence CVE CVE-2024-53214 https://www.cve.org/CVERecord?id=CVE-2024-53214 Référence CVE CVE-2024-56600 https://www.cve.org/CVERecord?id=CVE-2024-56600 Référence CVE CVE-2024-56601 https://www.cve.org/CVERecord?id=CVE-2024-56601 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56664 https://www.cve.org/CVERecord?id=CVE-2024-56664 Référence CVE CVE-2024-57893 https://www.cve.org/CVERecord?id=CVE-2024-57893 Référence CVE CVE-2024-57996 https://www.cve.org/CVERecord?id=CVE-2024-57996 Référence CVE CVE-2024-58240 https://www.cve.org/CVERecord?id=CVE-2024-58240 Référence CVE CVE-2024-8805 https://www.cve.org/CVERecord?id=CVE-2024-8805 Référence CVE CVE-2025-21702 https://www.cve.org/CVERecord?id=CVE-2025-21702 Référence CVE CVE-2025-21772 https://www.cve.org/CVERecord?id=CVE-2025-21772 Référence CVE CVE-2025-21791 https://www.cve.org/CVERecord?id=CVE-2025-21791 Référence CVE CVE-2025-21971 https://www.cve.org/CVERecord?id=CVE-2025-21971 Référence CVE CVE-2025-37752 https://www.cve.org/CVERecord?id=CVE-2025-37752 Référence CVE CVE-2025-37797 https://www.cve.org/CVERecord?id=CVE-2025-37797 Référence CVE CVE-2025-37885 https://www.cve.org/CVERecord?id=CV

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

ité Red Hat RHSA-2025:21760 du 19 novembre 2025 https://access.redhat.com/errata/RHSA-2025:21760 Référence CVE CVE-2022-49969 https://www.cve.org/CVERecord?id=CVE-2022-49969 Référence CVE CVE-2022-50087 https://www.cve.org/CVERecord?id=CVE-2022-50087 Référence CVE CVE-2022-50228 https://www.cve.org/CVERecord?id=CVE-2022-50228 Référence CVE CVE-2022-50229 https://www.cve.org/CVERecord?id=CVE-2022-50229 Référence CVE CVE-2023-53125 https://www.cve.org/CVERecord?id=CVE-2023-53125 Référence CVE CVE-2023-53494 https://www.cve.org/CVERecord?id=CVE-2023-53494 Référence CVE CVE-2024-56690 https://www.cve.org/CVERecord?id=CVE-2024-56690 Référence CVE CVE-2024-58240 https://www.cve.org/CVERecord?id=CVE-2024-58240 Référence CVE CVE-2025-22026 https://www.cve.org/CVERecord?id=CVE-2025-22026 Référence CVE CVE-2025-37797 https://www.cve.org/CVERecord?id=CVE-2025-37797 Référence CVE CVE-2025-38085 https://www.cve.org/CVERecord?id=CVE-2025-38085 Référence CVE CVE-2025-38159 https://www.cve.org/CVERecord?id=CVE-2025-38159 Référence CVE CVE-2025-38200 https://www.cve.org/CVERecord?id=CVE-2025-38200 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38332 https://www.cve.org/CVERecord?id=CVE-2025-38332 Référence CVE CVE-2025-38351 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46800 Référence CVE CVE-2024-53125 https://www.cve.org/CVERecord?id=CVE-2024-53125 Référence CVE CVE-2024-53141 https://www.cve.org/CVERecord?id=CVE-2024-53141 Référence CVE CVE-2024-53164 https://www.cve.org/CVERecord?id=CVE-2024-53164 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=CVE-2024-53168 Référence CVE CVE-2024-53197 https://www.cve.org/CVERecord?id=CVE-2024-53197 Référence CVE CVE-2024-56558 https://www.cve.org/CVERecord?id=CVE-2024-56558 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=CVE-2024-56770 Référence CVE CVE-2024-57999 https://www.cve.org/CVERecord?id=CVE-2024-57999 Référence CVE CVE-2024-58240 https://www.cve.org/CVERecord?id=CVE-2024-58240 Référence CVE CVE-2025-21700 https://www.cve.org/CVERecord?id=CVE-2025-21700 Référence CVE CVE-2025-21702 https://www.cve.org/CVERecord?id=CVE-2025-21702 Référence CVE CVE-2025-21703 https://www.cve.org/CVERecord?id=CVE-2025-21703 Référence CVE CVE-2025-21756 https://www.cve.org/CVERecord?id=CVE-2025-21756 Référence CVE CVE-2025-21999 https://www.cve.org/CVERecord?id=CVE-2025-21999 Référence CVE CVE-2025-22056 https://www.cve.org/CVERecord?id=CVE-2025-22056 Référence CVE CVE-2025-23141 https://www.cve.org/CVERecord?id=CVE-2025-23141 Référence CVE CVE-2025-23145 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53125 Référence CVE CVE-2023-53178 https://www.cve.org/CVERecord?id=CVE-2023-53178 Référence CVE CVE-2023-53226 https://www.cve.org/CVERecord?id=CVE-2023-53226 Référence CVE CVE-2023-53257 https://www.cve.org/CVERecord?id=CVE-2023-53257 Référence CVE CVE-2023-53331 https://www.cve.org/CVERecord?id=CVE-2023-53331 Référence CVE CVE-2023-53373 https://www.cve.org/CVERecord?id=CVE-2023-53373 Référence CVE CVE-2023-53401 https://www.cve.org/CVERecord?id=CVE-2023-53401 Référence CVE CVE-2023-53494 https://www.cve.org/CVERecord?id=CVE-2023-53494 Référence CVE CVE-2024-46679 https://www.cve.org/CVERecord?id=CVE-2024-46679 Référence CVE CVE-2024-58240 https://www.cve.org/CVERecord?id=CVE-2024-58240 Référence CVE CVE-2025-38556 https://www.cve.org/CVERecord?id=CVE-2025-38556 Référence CVE CVE-2025-38614 https://www.cve.org/CVERecord?id=CVE-2025-38614 Référence CVE CVE-2025-39702 https://www.cve.org/CVERecord?id=CVE-2025-39702 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39751 https://www.cve.org/CVERecord?id=CVE-2025-39751 Référence CVE CVE-2025-39864 https://www.cve.org/CVERecord?id=CVE-2025-39864 Référence CVE CVE-2025-39881 https://www.cve.org/CVERecord?id=CVE-2025-39881 Gestion détaillée du document le 07 novembre 2025 Version init

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

d?id=CVE-2022-50070 Référence CVE CVE-2022-50137 https://www.cve.org/CVERecord?id=CVE-2022-50137 Référence CVE CVE-2022-50228 https://www.cve.org/CVERecord?id=CVE-2022-50228 Référence CVE CVE-2022-50386 https://www.cve.org/CVERecord?id=CVE-2022-50386 Référence CVE CVE-2023-53125 https://www.cve.org/CVERecord?id=CVE-2023-53125 Référence CVE CVE-2023-53297 https://www.cve.org/CVERecord?id=CVE-2023-53297 Référence CVE CVE-2023-53305 https://www.cve.org/CVERecord?id=CVE-2023-53305 Référence CVE CVE-2023-53373 https://www.cve.org/CVERecord?id=CVE-2023-53373 Référence CVE CVE-2023-53386 https://www.cve.org/CVERecord?id=CVE-2023-53386 Référence CVE CVE-2024-58240 https://www.cve.org/CVERecord?id=CVE-2024-58240 Référence CVE CVE-2025-22026 https://www.cve.org/CVERecord?id=CVE-2025-22026 Référence CVE CVE-2025-37797 https://www.cve.org/CVERecord?id=CVE-2025-37797 Référence CVE CVE-2025-38556 https://www.cve.org/CVERecord?id=CVE-2025-38556 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38614 https://www.cve.org/CVERecord?id=CVE-2025-38614 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-39682 https://www.cve.org/CVERecord?id=CVE-2025-39682 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26583 Référence CVE CVE-2024-26584 https://www.cve.org/CVERecord?id=CVE-2024-26584 Référence CVE CVE-2024-26661 https://www.cve.org/CVERecord?id=CVE-2024-26661 Référence CVE CVE-2024-46733 https://www.cve.org/CVERecord?id=CVE-2024-46733 Référence CVE CVE-2024-49974 https://www.cve.org/CVERecord?id=CVE-2024-49974 Référence CVE CVE-2024-53125 https://www.cve.org/CVERecord?id=CVE-2024-53125 Référence CVE CVE-2024-58090 https://www.cve.org/CVERecord?id=CVE-2024-58090 Référence CVE CVE-2024-58238 https://www.cve.org/CVERecord?id=CVE-2024-58238 Référence CVE CVE-2024-58239 https://www.cve.org/CVERecord?id=CVE-2024-58239 Référence CVE CVE-2024-58240 https://www.cve.org/CVERecord?id=CVE-2024-58240 Référence CVE CVE-2025-21971 https://www.cve.org/CVERecord?id=CVE-2025-21971 Référence CVE CVE-2025-22022 https://www.cve.org/CVERecord?id=CVE-2025-22022 Référence CVE CVE-2025-23155 https://www.cve.org/CVERecord?id=CVE-2025-23155 Référence CVE CVE-2025-37738 https://www.cve.org/CVERecord?id=CVE-2025-37738 Référence CVE CVE-2025-37885 https://www.cve.org/CVERecord?id=CVE-2025-37885 Référence CVE CVE-2025-37958 https://www.cve.org/CVERecord?id=CVE-2025-37958 Référence CVE CVE-2025-38006 https://www.cve.org/CVERecord?id=CVE-2025-38006 Référence CVE CVE-2025-38014 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46733 Référence CVE CVE-2024-50154 https://www.cve.org/CVERecord?id=CVE-2024-50154 Référence CVE CVE-2024-53093 https://www.cve.org/CVERecord?id=CVE-2024-53093 Référence CVE CVE-2024-53125 https://www.cve.org/CVERecord?id=CVE-2024-53125 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=CVE-2024-53168 Référence CVE CVE-2024-53194 https://www.cve.org/CVERecord?id=CVE-2024-53194 Référence CVE CVE-2024-58090 https://www.cve.org/CVERecord?id=CVE-2024-58090 Référence CVE CVE-2024-58238 https://www.cve.org/CVERecord?id=CVE-2024-58238 Référence CVE CVE-2024-58239 https://www.cve.org/CVERecord?id=CVE-2024-58239 Référence CVE CVE-2024-58240 https://www.cve.org/CVERecord?id=CVE-2024-58240 Référence CVE CVE-2025-21692 https://www.cve.org/CVERecord?id=CVE-2025-21692 Référence CVE CVE-2025-21791 https://www.cve.org/CVERecord?id=CVE-2025-21791 Référence CVE CVE-2025-21969 https://www.cve.org/CVERecord?id=CVE-2025-21969 Référence CVE CVE-2025-22022 https://www.cve.org/CVERecord?id=CVE-2025-22022 Référence CVE CVE-2025-22023 https://www.cve.org/CVERecord?id=CVE-2025-22023 Référence CVE CVE-2025-37738 https://www.cve.org/CVERecord?id=CVE-2025-37738 Référence CVE CVE-2025-37885 https://www.cve.org/CVERecord?id=CVE-2025-37885 Référence CVE CVE-2025-37958 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46751 Référence CVE CVE-2024-46855 https://www.cve.org/CVERecord?id=CVE-2024-46855 Référence CVE CVE-2024-47704 https://www.cve.org/CVERecord?id=CVE-2024-47704 Référence CVE CVE-2024-49935 https://www.cve.org/CVERecord?id=CVE-2024-49935 Référence CVE CVE-2024-53203 https://www.cve.org/CVERecord?id=CVE-2024-53203 Référence CVE CVE-2024-56758 https://www.cve.org/CVERecord?id=CVE-2024-56758 Référence CVE CVE-2024-57883 https://www.cve.org/CVERecord?id=CVE-2024-57883 Référence CVE CVE-2024-57924 https://www.cve.org/CVERecord?id=CVE-2024-57924 Référence CVE CVE-2024-57996 https://www.cve.org/CVERecord?id=CVE-2024-57996 Référence CVE CVE-2024-58240 https://www.cve.org/CVERecord?id=CVE-2024-58240 Référence CVE CVE-2025-21816 https://www.cve.org/CVERecord?id=CVE-2025-21816 Référence CVE CVE-2025-21912 https://www.cve.org/CVERecord?id=CVE-2025-21912 Référence CVE CVE-2025-22119 https://www.cve.org/CVERecord?id=CVE-2025-22119 Référence CVE CVE-2025-23143 https://www.cve.org/CVERecord?id=CVE-2025-23143 Référence CVE CVE-2025-23160 https://www.cve.org/CVERecord?id=CVE-2025-23160 Référence CVE CVE-2025-27558 https://www.cve.org/CVERecord?id=CVE-2025-27558 Référence CVE CVE-2025-37798 https://www.cve.org/CVERecord?id=CVE-2025-37798 Référence CVE CVE-2025-37819 https://www.cve.org/CVERecord?id=

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

vation de privilèges, une atteinte à la confidentialité des données et un déni de service. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian DSA-6008-1 du 22 septembre 2025 https://lists.debian.org/debian-security-announce/2025/msg00172.html Bulletin de sécurité Debian DSA-6009-1 du 22 septembre 2025 https://lists.debian.org/debian-security-announce/2025/msg00173.html Référence CVE CVE-2024-47704 https://www.cve.org/CVERecord?id=CVE-2024-47704 Référence CVE CVE-2024-57924 https://www.cve.org/CVERecord?id=CVE-2024-57924 Référence CVE CVE-2024-58240 https://www.cve.org/CVERecord?id=CVE-2024-58240 Référence CVE CVE-2025-21751 https://www.cve.org/CVERecord?id=CVE-2025-21751 Référence CVE CVE-2025-22103 https://www.cve.org/CVERecord?id=CVE-2025-22103 Référence CVE CVE-2025-22113 https://www.cve.org/CVERecord?id=CVE-2025-22113 Référence CVE CVE-2025-22124 https://www.cve.org/CVERecord?id=CVE-2025-22124 Référence CVE CVE-2025-22125 https://www.cve.org/CVERecord?id=CVE-2025-22125 Référence CVE CVE-2025-23133 https://www.cve.org/CVERecord?id=CVE-2025-23133 Référence CVE CVE-2025-23143 https://www.cve.org/CVERecord?id=CVE-2025-23143 Référence CVE CVE-2025-23160 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-024493Debian等の複数ベンダの製品における解放済みメモリの使用に関する脆弱性

Linuxカーネルでは、非同期でないTLS復号リクエストの処理が非同期処理から分離されました。非同期処理が行われない場合は、処理が単純化され、参照カウントが不要となり、完了通知を待ってその結果を返します。この変更は、過去の問題を考慮しており、今後の修正を容易にします。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0147Kwetsbaarheden verholpen in Siemens-producten

Multiple SUSE Linux Enterprise kernels, including versions 12, 15 (SP3 to SP7), Micro 6.x, and Azure variants, received extensive security updates addressing vulnerabilities in Bluetooth, networking, filesystems, USB, SCSI, memory management, and hardware drivers, alongside a Linux kernel TLS decryption refactor to improve processing correctness.

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.13, 5.10.265 ≤ 5.10.*, 5.15.216 ≤ 5.15.*, 6.1.149 ≤ 6.1.*, 6.6.21 ≤ 6.6.*, 6.7.9 ≤ 6.7.*, 6.8 ≤ *
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 28 Aug 2025 · Last source change 19 Aug 2026, 16:27 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-2024-54920
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < 48905146d11dbf1ddbb2967319016a83976953f5; 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < dec5b6e7b211e405d3bcb504562ab21aa7e5a64d; 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < 999115298017a675d8ddf61414fc7a85c89f1186; 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < 41532b785e9d79636b3815a64ddf6a096647d011; 4.13 · Fixed: < 4.13; 6.1.149 ≤ 6.1.*; 6.6.21 ≤ 6.6.*; 6.7.9 ≤ 6.7.*; 6.8 ≤ *
    After
    3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < f32ab6cb544d01cdc150de5df389ac685aa507b0; 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < 5f7761c94b1db7570cab328c9f940a33284509b7; 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < 48905146d11dbf1ddbb2967319016a83976953f5; 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < dec5b6e7b211e405d3bcb504562ab21aa7e5a64d; 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < 999115298017a675d8ddf61414fc7a85c89f1186; 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < 41532b785e9d79636b3815a64ddf6a096647d011; 4.13 · Fixed: < 4.13; 5.10.265 ≤ 5.10.*; 5.15.216 ≤ 5.15.*; 6.1.149 ≤ 6.1.*; 6.6.21 ≤ 6.6.*; 6.7.9 ≤ 6.7.*; 6.8 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-54920↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-58240 · cve.blacktree.nl