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

scsi: sg: Fix slab-use-after-free read in sg_release()

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Evidence used

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

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 25 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 19 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.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.128-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-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 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

3 current
CVE-2024-56631 · CSAF 2.0 · revision 84 · interimSUSE Product Security TeamCVE-2024-56631
262 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP5
  • 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
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: scsi: sg: Fix slab-use-after-free read in sg_release() Fix a use-after-free bug in sg_release(), detected by syzbot with KASAN: BUG: KASAN: slab-use-after-free in lock_release+0x151/0xa30 kernel/locking/lockdep.c:5838 __mutex_unlock_slowpath+0xe2/0x750 kernel/locking/mutex.c:912 sg_release+0x1f4/0x2e0 drivers/scsi/sg.c:407 In sg_release(), the function kref_put(&sfp->f_ref, sg_remove_sfp) is called before releasing the open_rel_lock mutex. The kref_put() call may decrement the reference count of sfp to zero, triggering its cleanup through sg_remove_sfp(). This cleanup includes scheduling deferred work via sg_remove_sfp_usercontext(), which ultimately frees sfp. After kref_put(), sg_release() continues to unlock open_rel_lock and may reference sfp or sdp. If sfp has already been freed, this results in a slab-use-after-free error. Move the kref_put(&sfp->f_ref, sg_remove_sfp) call after unlocking the open_rel_lock mutex. This ensures: - No references to sfp or sdp occur after the reference count is decremented. - Cleanup functions such as sg_remove_sfp() and sg_remove_sfp_usercontext() can safely execute without impacting the mutex handling in sg_release(). The fix has been tested and validated by syzbot. This patch closes the bug reported at the following syzkaller link and ensures proper sequencing of resource cleanup and mutex operations, eliminating the risk of use-after-free errors in sg_release().
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: scsi: sg: Fix slab-use-after-free read in sg_release() Fix a use-after-free bug in sg_release(), detected by syzbot with KASAN: BUG: KASAN: slab-use-after-free in lock_release+0x151/0xa30 kernel/locking/lockdep.c:5838 __mutex_unlock_slowpath+0xe2/0x750 kernel/locking/mutex.c:912 sg_release+0x1f4/0x2e0 drivers/scsi/sg.c:407 In sg_release(), the function kref_put(&sfp->f_ref, sg_remove_sfp) is called before releasing the open_rel_lock mutex. The kref_put() call may decrement the reference count of sfp to zero, triggering its cleanup through sg_remove_sfp(). This cleanup includes scheduling deferred work via sg_remove_sfp_usercontext(), which ultimately frees sfp. After kref_put(), sg_release() continues to unlock open_rel_lock and may reference sfp or sdp. If sfp has already been freed, this results in a slab-use-after-free error. Move the kref_put(&sfp->f_ref, sg_remove_sfp) call after unlocking the open_rel_lock mutex. This ensures: - No references to sfp or sdp occur after the reference count is decremented. - Cleanup functions such as sg_remove_sfp() and sg_remove_sfp_usercontext() can safely execute without impacting the mutex handling in sg_release(). The fix has been tested and validated by syzbot. This patch closes the bug reported at the following syzkaller link and ensures proper sequencing of resource cleanup and mutex operations, eliminating the risk of use-after-free errors in sg_release().
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-265688 · CSAF 2.0 · revision 13 · interimSiemens ProductCERTSSA-265688: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP V1.1
1 known affected

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

  • SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
Summary
In the Linux kernel, the following vulnerability has been resolved: scsi: sg: Fix slab-use-after-free read in sg_release() Fix a use-after-free bug in sg_release(), detected by syzbot with KASAN: The fix has been tested and validated by syzbot. This patch closes the bug reported at the following syzkaller link and ensures proper sequencing of resource cleanup and mutex operations, eliminating the risk of use-after-free errors in sg_release().
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-53279

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: scsi: sg: Fix slab-use-after-free read in sg_release() Fix a use-after-free bug in sg_release(), detected by syzbot with KASAN: BUG: KASAN: slab-use-after-free in lock_release+0x151/0xa30 kernel/locking/lockdep.c:5838 __mutex_unlock_slowpath+0xe2/0x750 kernel/locking/mutex.c:912 sg_release+0x1f4/0x2e0 drivers/scsi/sg.c:407 In sg_release(), the function kref_put(&sfp->f_ref, sg_remove_sfp) is called before releasing the open_rel_lock mutex. The kref_put() call may decrement the reference count of sfp to zero, triggering its cleanup through sg_remove_sfp(). This cleanup includes scheduling deferred work via sg_remove_sfp_usercontext(), which ultimately frees sfp. After kref_put(), sg_release() continues to unlock open_rel_lock and may reference sfp or sdp. If sfp has already been freed, this results in a slab-use-after-free error. Move the kref_put(&sfp->f_ref, sg_remove_sfp) call after unlocking the open_rel_lock mutex. This ensures: - No references to sfp or sdp occur after the reference count is decremented. - Cleanup functions such as sg_remove_sfp() and sg_remove_sfp_usercontext() can safely execute without impacting the mutex handling in sg_release(). The fix has been tested and validated by syzbot. This patch closes the bug reported at the following syzkaller link and ensures proper sequencing of resource cleanup and mutex operations, eliminating the risk of use-after-free errors in sg_release().

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 25 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: scsi: sg: Fix slab-use-after-free read in sg_release() Fix a use-after-free bug in sg_release(), detected by syzbot with KASAN: BUG: KASAN: slab-use-after-free in lock_release+0x151/0xa30 kernel/locking/lockdep.c:5838 __mutex_unlock_slowpath+0xe2/0x750 kernel/locking/mutex.c:912 sg_release+0x1f4/0x2e0 drivers/scsi/sg.c:407 In sg_release(), the function kref_put(&sfp->f_ref, sg_remove_sfp) is called before releasing the open_rel_lock mutex. The kref_put() call may decrement the reference count of sfp to zero, triggering its cleanup through sg_remove_sfp(). This cleanup includes scheduling deferred work via sg_remove_sfp_usercontext(), which ultimately frees sfp. After kref_put(), sg_release() continues to unlock open_rel_lock and may reference sfp or sdp. If sfp has already been freed, this results in a slab-use-after-free error. Move the kref_put(&sfp->f_ref, sg_remove_sfp) call after unlocking the open_rel_lock mutex. This ensures: - No references to sfp or sdp occur after the reference count is decremented. - Cleanup functions such as sg_remove_sfp() and sg_remove_sfp_usercontext() can safely execute without impacting the mutex handling in sg_release(). The fix has been tested and validated by syzbot. This patch closes the bug reported at the following syzkaller link and ensures proper sequencing of resource cleanup and mutex operations, eliminating the risk of use-after-free errors in sg_release().

What

In the Linux kernel, the following vulnerability has been resolved: scsi: sg: Fix slab-use-after-free read in sg_release() Fix a use-after-free bug in sg_release(), detected by syzbot with KASAN: BUG: KASAN: slab-use-after-free in lock_release+0x151/0xa30 kernel/locking/lockdep.c:5838 __mutex_unlock_slowpath+0xe2/0x750 kernel/locking/mutex.c:912 sg_release+0x1f4/0x2e0 drivers/scsi/sg.c:407 In sg_release(), the function kref_put(&sfp->f_ref, sg_remove_sfp) is called before releasing the open_rel_lock mutex. The kref_put() call may decrement the reference count of sfp to zero, triggering its cleanup through sg_remove_sfp(). This cleanup includes scheduling deferred work via sg_remove_sfp_usercontext(), which ultimately frees sfp. After kref_put(), sg_release() continues to unlock open_rel_lock and may reference sfp or sdp. If sfp has already been freed, this results in a slab-use-after-free error. Move the kref_put(&sfp->f_ref, sg_remove_sfp) call after unlocking the open_rel_lock mutex. This ensures: - No references to sfp or sdp occur after the reference count is decremented. - Cleanup functions such as sg_remove_sfp() and sg_remove_sfp_usercontext() can safely execute without impacting the mutex handling in sg_release(). The fix has been tested and validated by syzbot. This patch closes the bug reported at the following syzkaller link and ensures proper sequencing of resource cleanup and mutex operations, eliminating the risk of use-after-free errors in sg_release().

Why

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

How

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

What

In the Linux kernel, the following vulnerability has been resolved: scsi: sg: Fix slab-use-after-free read in sg_release() Fix a use-after-free bug in sg_release(), detected by syzbot with KASAN: BUG: KASAN: slab-use-after-free in lock_release+0x151/0xa30 kernel/locking/lockdep.c:5838 __mutex_unlock_slowpath+0xe2/0x750 kernel/locking/mutex.c:912 sg_release+0x1f4/0x2e0 drivers/scsi/sg.c:407 In sg_release(), the function kref_put(&sfp->f_ref, sg_remove_sfp) is called before releasing the open_rel_lock mutex. The kref_put() call may decrement the reference count of sfp to zero, triggering its cleanup through sg_remove_sfp(). This cleanup includes scheduling deferred work via sg_remove_sfp_usercontext(), which ultimately frees sfp. After kref_put(), sg_release() continues to unlock open_rel_lock and may reference sfp or sdp. If sfp has already been freed, this results in a slab-use-after-free error. Move the kref_put(&sfp->f_ref, sg_remove_sfp) call after unlocking the open_rel_lock mutex. This ensures: - No references to sfp or sdp occur after the reference count is decremented. - Cleanup functions such as sg_remove_sfp() and sg_remove_sfp_usercontext() can safely execute without impacting the mutex handling in sg_release(). The fix has been tested and validated by syzbot. This patch closes the bug reported at the following syzkaller link and ensures proper sequencing of resource cleanup and mutex operations, eliminating the risk of use-after-free errors in sg_release().

Why

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

How

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

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
local access → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

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

Official authority intelligence

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

ENISA EUVD · EUVD-2024-53279Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: scsi: sg: Fix slab-use-after-free read in sg_release() Fix a use-after-free bug in sg_release(), detected by syzbot with KASAN: BUG: KASAN: slab-use-after-free in lock_release+0x151/0xa30 kernel/locking/lockdep.c:5838 __mutex_unlock_slowpath+0xe2/0x750 kernel/locking/mutex.c:912 sg_release+0x1f4/0x2e0 drivers/scsi/sg.c:407 In sg_release(), the function kref_put(&sfp->f_ref, sg_remove_sfp) is called before releasing the open_rel_lock mutex. The kref_put() call may decrement the reference count of sfp to zero, triggering its cleanup through sg_remove_sfp(). This cleanup includes scheduling deferred work via sg_remove_sfp_usercontext(), which ultimately frees sfp. After kref_put(), sg_release() continues to unlock open_rel_lock and may reference sfp or sdp. If sfp has already been freed, this results in a slab-use-after-free error. Move the kref_put(&sfp->f_ref, sg_remove_sfp) call after unlocking the open_rel_lock mutex. This ensures: - No references to sfp or sdp occur after the reference count is decremented. - Cleanup functions such as sg_remove_sfp() and sg_remove_sfp_usercontext() can safely execute without impacting the mutex handling in sg_release(). The fix has been tested and validated by syzbot. This patch closes the bug reported at the following syzkaller link and ensures proper sequencing of resource cleanup and mutex operations, eliminating the risk of use-after-free errors in sg_release().

Official EUVD record ↗
BSI · German · WID-SEC-2024-3762Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.

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

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 01 Jan 2025, published on 1 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-0880Multiples vulnérabilités dans les produits Siemens

tance Non spécifié par l'éditeur Élévation de privilèges Systèmes affectés Desigo CC toutes versions Desigo CC toutes versions pour la vulnérabilité CVE-2025-15467 Desigo CC versions antérieures à 9.0.1 SIMATIC S7-1500 versions supérieures ou égales à 3.1.6 pour les vulnérabilités CVE-2021-41617, CVE-2023-28531, CVE-2023-51384, CVE-2023-52927, CVE-2024-26783, CVE-2024-27056, CVE-2024-28956, CVE-2024-36903, CVE-2024-36927, CVE-2024-42079, CVE-2024-46786, CVE-2024-47736, CVE-2024-47809, CVE-2024-49968, CVE-2024-49994, CVE-2024-49998, CVE-2024-50014, CVE-2024-50063, CVE-2024-50164, CVE-2024-50298, CVE-2024-53124, CVE-2024-53170, CVE-2024-54458, CVE-2024-56631, CVE-2024-56703, CVE-2024-56719, CVE-2024-57917, CVE-2024-57924, CVE-2024-57973, CVE-2024-57977, CVE-2024-57979, CVE-2024-58011, CVE-2024-58016, CVE-2024-58020, CVE-2024-58056, CVE-2024-58058, CVE-2024-58061, CVE-2024-58086, CVE-2025-21645, CVE-2025-21648, CVE-2025-21655, CVE-2025-21676, CVE-2025-21682, CVE-2025-21702, CVE-2025-21705, CVE-2025-21706, CVE-2025-21707, CVE-2025-21718, CVE-2025-21731, CVE-2025-21745, CVE-2025-21758, CVE-2025-21760, CVE-2025-21764, CVE-2025-21765, CVE-2025-21780, CVE-2025-21795, CVE-2025-21796, CVE-2025-21802, CVE-2025-21814, CVE-2025-21846, CVE-2025-21853, CVE-2025-21861, CVE-2025-21864, CVE-2025-21867, CVE-2025

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

d?id=CVE-2024-50248 Référence CVE CVE-2024-50256 https://www.cve.org/CVERecord?id=CVE-2024-50256 Référence CVE CVE-2024-50296 https://www.cve.org/CVERecord?id=CVE-2024-50296 Référence CVE CVE-2024-53063 https://www.cve.org/CVERecord?id=CVE-2024-53063 Référence CVE CVE-2024-53066 https://www.cve.org/CVERecord?id=CVE-2024-53066 Référence CVE CVE-2024-53140 https://www.cve.org/CVERecord?id=CVE-2024-53140 Référence CVE CVE-2024-53173 https://www.cve.org/CVERecord?id=CVE-2024-53173 Référence CVE CVE-2024-53237 https://www.cve.org/CVERecord?id=CVE-2024-53237 Référence CVE CVE-2024-56598 https://www.cve.org/CVERecord?id=CVE-2024-56598 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56651 https://www.cve.org/CVERecord?id=CVE-2024-56651 Référence CVE CVE-2024-56653 https://www.cve.org/CVERecord?id=CVE-2024-56653 Référence CVE CVE-2024-56658 https://www.cve.org/CVERecord?id=CVE-2024-56658 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=CVE-2024-56770 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-58081 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56620 Référence CVE CVE-2024-56621 https://www.cve.org/CVERecord?id=CVE-2024-56621 Référence CVE CVE-2024-56622 https://www.cve.org/CVERecord?id=CVE-2024-56622 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56625 https://www.cve.org/CVERecord?id=CVE-2024-56625 Référence CVE CVE-2024-56626 https://www.cve.org/CVERecord?id=CVE-2024-56626 Référence CVE CVE-2024-56627 https://www.cve.org/CVERecord?id=CVE-2024-56627 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56632 https://www.cve.org/CVERecord?id=CVE-2024-56632 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56635 https://www.cve.org/CVERecord?id=CVE-2024-56635 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56638 https://www.cve.org/CVERecord?id=CVE-2024-56638 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56620 Référence CVE CVE-2024-56621 https://www.cve.org/CVERecord?id=CVE-2024-56621 Référence CVE CVE-2024-56622 https://www.cve.org/CVERecord?id=CVE-2024-56622 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56625 https://www.cve.org/CVERecord?id=CVE-2024-56625 Référence CVE CVE-2024-56626 https://www.cve.org/CVERecord?id=CVE-2024-56626 Référence CVE CVE-2024-56627 https://www.cve.org/CVERecord?id=CVE-2024-56627 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56632 https://www.cve.org/CVERecord?id=CVE-2024-56632 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56635 https://www.cve.org/CVERecord?id=CVE-2024-56635 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56638 https://www.cve.org/CVERecord?id=CVE-2024-56638 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56616 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56622 https://www.cve.org/CVERecord?id=CVE-2024-56622 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56625 https://www.cve.org/CVERecord?id=CVE-2024-56625 Référence CVE CVE-2024-56626 https://www.cve.org/CVERecord?id=CVE-2024-56626 Référence CVE CVE-2024-56627 https://www.cve.org/CVERecord?id=CVE-2024-56627 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56616 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56622 https://www.cve.org/CVERecord?id=CVE-2024-56622 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56625 https://www.cve.org/CVERecord?id=CVE-2024-56625 Référence CVE CVE-2024-56626 https://www.cve.org/CVERecord?id=CVE-2024-56626 Référence CVE CVE-2024-56627 https://www.cve.org/CVERecord?id=CVE-2024-56627 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56621 Référence CVE CVE-2024-56622 https://www.cve.org/CVERecord?id=CVE-2024-56622 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56624 https://www.cve.org/CVERecord?id=CVE-2024-56624 Référence CVE CVE-2024-56625 https://www.cve.org/CVERecord?id=CVE-2024-56625 Référence CVE CVE-2024-56626 https://www.cve.org/CVERecord?id=CVE-2024-56626 Référence CVE CVE-2024-56627 https://www.cve.org/CVERecord?id=CVE-2024-56627 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56632 https://www.cve.org/CVERecord?id=CVE-2024-56632 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56635 https://www.cve.org/CVERecord?id=CVE-2024-56635 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56638 https://www.cve.org/CVERecord?id=CVE-2024-56638 Référence CVE CVE-2024-56639 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56598 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-56602 https://www.cve.org/CVERecord?id=CVE-2024-56602 Référence CVE CVE-2024-56604 https://www.cve.org/CVERecord?id=CVE-2024-56604 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56658 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56619 Référence CVE CVE-2024-56622 https://www.cve.org/CVERecord?id=CVE-2024-56622 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56625 https://www.cve.org/CVERecord?id=CVE-2024-56625 Référence CVE CVE-2024-56626 https://www.cve.org/CVERecord?id=CVE-2024-56626 Référence CVE CVE-2024-56627 https://www.cve.org/CVERecord?id=CVE-2024-56627 Référence CVE CVE-2024-56628 https://www.cve.org/CVERecord?id=CVE-2024-56628 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56616 Référence CVE CVE-2024-56617 https://www.cve.org/CVERecord?id=CVE-2024-56617 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56620 https://www.cve.org/CVERecord?id=CVE-2024-56620 Référence CVE CVE-2024-56622 https://www.cve.org/CVERecord?id=CVE-2024-56622 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56625 https://www.cve.org/CVERecord?id=CVE-2024-56625 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56632 https://www.cve.org/CVERecord?id=CVE-2024-56632 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56635 https://www.cve.org/CVERecord?id=CVE-2024-56635 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53124 Référence CVE CVE-2024-53128 https://www.cve.org/CVERecord?id=CVE-2024-53128 Référence CVE CVE-2024-53170 https://www.cve.org/CVERecord?id=CVE-2024-53170 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53234 https://www.cve.org/CVERecord?id=CVE-2024-53234 Référence CVE CVE-2024-53685 https://www.cve.org/CVERecord?id=CVE-2024-53685 Référence CVE CVE-2024-56551 https://www.cve.org/CVERecord?id=CVE-2024-56551 Référence CVE CVE-2024-56599 https://www.cve.org/CVERecord?id=CVE-2024-56599 Référence CVE CVE-2024-56608 https://www.cve.org/CVERecord?id=CVE-2024-56608 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56664 https://www.cve.org/CVERecord?id=CVE-2024-56664 Référence CVE CVE-2024-56703 https://www.cve.org/CVERecord?id=CVE-2024-56703 Référence CVE CVE-2024-57887 https://www.cve.org/CVERecord?id=CVE-2024-57887 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=CVE-2024-57907 Référence CVE CVE-2024-57908 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56616 Référence CVE CVE-2024-56617 https://www.cve.org/CVERecord?id=CVE-2024-56617 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56620 https://www.cve.org/CVERecord?id=CVE-2024-56620 Référence CVE CVE-2024-56622 https://www.cve.org/CVERecord?id=CVE-2024-56622 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56625 https://www.cve.org/CVERecord?id=CVE-2024-56625 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56632 https://www.cve.org/CVERecord?id=CVE-2024-56632 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56635 https://www.cve.org/CVERecord?id=CVE-2024-56635 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56616 Référence CVE CVE-2024-56617 https://www.cve.org/CVERecord?id=CVE-2024-56617 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56620 https://www.cve.org/CVERecord?id=CVE-2024-56620 Référence CVE CVE-2024-56622 https://www.cve.org/CVERecord?id=CVE-2024-56622 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56625 https://www.cve.org/CVERecord?id=CVE-2024-56625 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56632 https://www.cve.org/CVERecord?id=CVE-2024-56632 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56635 https://www.cve.org/CVERecord?id=CVE-2024-56635 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56571 Référence CVE CVE-2024-56575 https://www.cve.org/CVERecord?id=CVE-2024-56575 Référence CVE CVE-2024-56576 https://www.cve.org/CVERecord?id=CVE-2024-56576 Référence CVE CVE-2024-56582 https://www.cve.org/CVERecord?id=CVE-2024-56582 Référence CVE CVE-2024-56598 https://www.cve.org/CVERecord?id=CVE-2024-56598 Référence CVE CVE-2024-56599 https://www.cve.org/CVERecord?id=CVE-2024-56599 Référence CVE CVE-2024-56604 https://www.cve.org/CVERecord?id=CVE-2024-56604 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56667 https://www.cve.org/CVERecord?id=CVE-2024-56667 Référence CVE CVE-2024-56704 https://www.cve.org/CVERecord?id=CVE-2024-56704 Référence CVE CVE-2024-56752 https://www.cve.org/CVERecord?id=CVE-2024-56752 Référence CVE CVE-2024-56754 https://www.cve.org/CVERecord?id=CVE-2024-56754 Référence CVE CVE-2024-56755 https://www.cve.org/CVERecord?id=CVE-2024-56755 Référence CVE CVE-2024-56756 https://www.cve.org/CVERecord?id=CVE-2024-56756 Référence CVE CVE-2024-8805 https://www.cve.org/CVERecord?id=C

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

Linux の Linux Kernel には、解放済みメモリの使用に関する脆弱性が存在します。

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: < 3.17, 5.4.290 ≤ 5.4.*, 5.10.234 ≤ 5.10.*, 5.15.177 ≤ 5.15.*, 6.1.127 ≤ 6.1.*, 6.6.66 ≤ 6.6.*, 6.12.5 ≤ 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 27 Dec 2024 · Last source change 8 Sept 2026, 08:39 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-53279
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    cc833acbee9db5ca8c6162b015b4c93863c6f821 < e19acb1926c4a1f30ee1ec84d8afba2d975bd534; cc833acbee9db5ca8c6162b015b4c93863c6f821 < 285ce1f89f8d414e7eecab5ef5118cd512596318; cc833acbee9db5ca8c6162b015b4c93863c6f821 < 198b89dd5a595ee3f96e5ce5c448b0484cd0e53c; cc833acbee9db5ca8c6162b015b4c93863c6f821 < 275b8347e21ab8193e93223a8394a806e4ba8918; cc833acbee9db5ca8c6162b015b4c93863c6f821 < 59b30afa578637169e2819536bb66459fdddc39d; cc833acbee9db5ca8c6162b015b4c93863c6f821 < 1f5e2f1ca5875728fcf62bc1a054707444ab4960; cc833acbee9db5ca8c6162b015b4c93863c6f821 < f10593ad9bc36921f623361c9e3dd96bd52d85ee; 3a27c0defb0315760100f8b1adc7c4acbe04c884 · Fixed: < 3.17; 5.4.290 ≤ 5.4.*; 5.10.234 ≤ 5.10.*; 5.15.177 ≤ 5.15.*; 6.1.127 ≤ 6.1.*; 6.6.66 ≤ 6.6.*; 6.12.5 ≤ 6.12.*; 6.13 ≤ *
    After
    Linux: cc833acbee9db5ca8c6162b015b4c93863c6f821 < e19acb1926c4a1f30ee1ec84d8afba2d975bd534, cc833acbee9db5ca8c6162b015b4c93863c6f821 < 285ce1f89f8d414e7eecab5ef5118cd512596318, cc833acbee9db5ca8c6162b015b4c93863c6f821 < 198b89dd5a595ee3f96e5ce5c448b0484cd0e53c, cc833acbee9db5ca8c6162b015b4c93863c6f821 < 275b8347e21ab8193e93223a8394a806e4ba8918, cc833acbee9db5ca8c6162b015b4c93863c6f821 < 59b30afa578637169e2819536bb66459fdddc39d, cc833acbee9db5ca8c6162b015b4c93863c6f821 < 1f5e2f1ca5875728fcf62bc1a054707444ab4960, cc833acbee9db5ca8c6162b015b4c93863c6f821 < f10593ad9bc36921f623361c9e3dd96bd52d85ee, 3a27c0defb0315760100f8b1adc7c4acbe04c884, 3.16.85 < 3.17, 3.17 · Fixed: Linux: < 3.17, 5.4.290 ≤ 5.4.*, 5.10.234 ≤ 5.10.*, 5.15.177 ≤ 5.15.*, 6.1.127 ≤ 6.1.*, 6.6.66 ≤ 6.6.*, 6.12.5 ≤ 6.12.*, 6.13 ≤ *
    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-53279↗Vendor CSAF · SUSE Product Security Team↗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-56631 · cve.blacktree.nl