Full vulnerability report · 2025

CVE-2024-57903High confidence

net: restrict SO_REUSEPORT to inet sockets

Linux · Linux

5.5MediumCVSS 3.1

Recommended action

Patch only the product branches with a verified fix

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

Fix availability varies by product

Operational reassessment

Published severity in operational context

Open reassessment dashboard →

Published severityMediumOperational priority:Low, lowered one band.downgradedsince 23 May 2026

Evidence used

No CISA KEV confirmation is currently recorded.
Exploitation requires an existing local or physical foothold with privileges.
EPSS is 0.20% 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

Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.

Cross-source reconciliation

Remediation availability differs by product scope

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

Canonical Ubuntu Security: 19 affected package states with no published fix

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 release	Source package	Vendor state	Fixed version	Evidence
Debian trixietrixie · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.9-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.1.124-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.9-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.9-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

1 current

CVE-2024-57903 · CSAF 2.0 · revision 73 · interimSUSE Product Security TeamCVE-2024-57903

339 known affected

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

kernel-default as component of SLES-LTSS-TERADATA 15 SP2
kernel-source as component of SLES-LTSS-TERADATA 15 SP2
kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
kernel-default as component of SUSE Linux Enterprise High Availability Extension 12 SP5
kernel-source as component of SUSE Linux Enterprise High Availability Extension 12 SP5
kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP5
kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4

Summary: In the Linux kernel, the following vulnerability has been resolved: net: restrict SO_REUSEPORT to inet sockets After blamed commit, crypto sockets could accidentally be destroyed from RCU call back, as spotted by zyzbot [1]. Trying to acquire a mutex in RCU callback is not allowed. Restrict SO_REUSEPORT socket option to inet sockets. v1 of this patch supported TCP, UDP and SCTP sockets, but fcnal-test.sh test needed RAW and ICMP support. [1] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:562 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 24, name: ksoftirqd/1 preempt_count: 100, expected: 0 RCU nest depth: 0, expected: 0 1 lock held by ksoftirqd/1/24: #0: ffffffff8e937ba0 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline] #0: ffffffff8e937ba0 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2561 [inline] #0: ffffffff8e937ba0 (rcu_callback){....}-{0:0}, at: rcu_core+0xa37/0x17a0 kernel/rcu/tree.c:2823 Preemption disabled at: [ ] softirq_handle_begin kernel/softirq.c:402 [inline] [ ] handle_softirqs+0x128/0x9b0 kernel/softirq.c:537 CPU: 1 UID: 0 PID: 24 Comm: ksoftirqd/1 Not tainted 6.13.0-rc3-syzkaller-00174-ga024e377efed #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 __might_resched+0x5d4/0x780 kernel/sched/core.c:8758 __mutex_lock_common kernel/locking/mutex.c:562 [inline] __mutex_lock+0x131/0xee0 kernel/locking/mutex.c:735 crypto_put_default_null_skcipher+0x18/0x70 crypto/crypto_null.c:179 aead_release+0x3d/0x50 crypto/algif_aead.c:489 alg_do_release crypto/af_alg.c:118 [inline] alg_sock_destruct+0x86/0xc0 crypto/af_alg.c:502 __sk_destruct+0x58/0x5f0 net/core/sock.c:2260 rcu_do_batch kernel/rcu/tree.c:2567 [inline] rcu_core+0xaaa/0x17a0 kernel/rcu/tree.c:2823 handle_softirqs+0x2d4/0x9b0 kernel/softirq.c:561 run_ksoftirqd+0xca/0x130 kernel/softirq.c:950 smpboot_thread_fn+0x544/0xa30 kernel/smpboot.c:164 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
Remediation: To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

Recommended actionPatch only the product branches with a verified fix

Fix availability varies by product

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net: restrict SO_REUSEPORT to inet sockets After blamed commit, crypto sockets could accidentally be destroyed from RCU call back, as spotted by zyzbot [1]. Trying to acquire a mutex in RCU callback is not allowed. Restrict SO_REUSEPORT socket option to inet sockets. v1 of this patch supported TCP, UDP and SCTP sockets, but fcnal-test.sh test needed RAW and ICMP support. [1] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:562 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 24, name: ksoftirqd/1 preempt_count: 100, expected: 0 RCU nest depth: 0, expected: 0 1 lock held by ksoftirqd/1/24: #0: ffffffff8e937ba0 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline] #0: ffffffff8e937ba0 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2561 [inline] #0: ffffffff8e937ba0 (rcu_callback){....}-{0:0}, at: rcu_core+0xa37/0x17a0 kernel/rcu/tree.c:2823 Preemption disabled at: [<ffffffff8161c8c8>] softirq_handle_begin kernel/softirq.c:402 [inline] [<ffffffff8161c8c8>] handle_softirqs+0x128/0x9b0 kernel/softirq.c:537 CPU: 1 UID: 0 PID: 24 Comm: ksoftirqd/1 Not tainted 6.13.0-rc3-syzkaller-00174-ga024e377efed #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 __might_resched+0x5d4/0x780 kernel/sched/core.c:8758 __mutex_lock_common kernel/locking/mutex.c:562 [inline] __mutex_lock+0x131/0xee0 kernel/locking/mutex.c:735 crypto_put_default_null_skcipher+0x18/0x70 crypto/crypto_null.c:179 aead_release+0x3d/0x50 crypto/algif_aead.c:489 alg_do_release crypto/af_alg.c:118 [inline] alg_sock_destruct+0x86/0xc0 crypto/af_alg.c:502 __sk_destruct+0x58/0x5f0 net/core/sock.c:2260 rcu_do_batch kernel/rcu/tree.c:2567 [inline] rcu_core+0xaaa/0x17a0 kernel/rcu/tree.c:2823 handle_softirqs+0x2d4/0x9b0 kernel/softirq.c:561 run_ksoftirqd+0xca/0x130 kernel/softirq.c:950 smpboot_thread_fn+0x544/0xa30 kernel/smpboot.c:164 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK>

What

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

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 → Improper Locking → 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-667 ↗
CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

CWE-667

Official authority intelligence

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

ENISA EUVD · EUVD-2024-53806Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

BSI · German · WID-SEC-2025-0105Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗

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

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

Official advisory ↗

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

d?id=CVE-2024-57884 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57901 https://www.cve.org/CVERecord?id=CVE-2024-57901 Référence CVE CVE-2024-57902 https://www.cve.org/CVERecord?id=CVE-2024-57902 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 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=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 https://www.cve.org/CVERecord?id=CVE-2024-57912 Référence CVE CVE-2024-57913 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

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

Official advisory ↗

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

Official advisory ↗

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

d?id=CVE-2024-57894 Référence CVE CVE-2024-57895 https://www.cve.org/CVERecord?id=CVE-2024-57895 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57898 https://www.cve.org/CVERecord?id=CVE-2024-57898 Référence CVE CVE-2024-57899 https://www.cve.org/CVERecord?id=CVE-2024-57899 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57901 https://www.cve.org/CVERecord?id=CVE-2024-57901 Référence CVE CVE-2024-57902 https://www.cve.org/CVERecord?id=CVE-2024-57902 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57905 https://www.cve.org/CVERecord?id=CVE-2024-57905 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=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 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-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57893 https://www.cve.org/CVERecord?id=CVE-2024-57893 Référence CVE CVE-2024-57894 https://www.cve.org/CVERecord?id=CVE-2024-57894 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57901 https://www.cve.org/CVERecord?id=CVE-2024-57901 Référence CVE CVE-2024-57902 https://www.cve.org/CVERecord?id=CVE-2024-57902 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 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=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 https://www.cve.org/CVERecord?id=CVE-2024-57912 Référence CVE CVE-2024-57913 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-57884 Référence CVE CVE-2024-57887 https://www.cve.org/CVERecord?id=CVE-2024-57887 Référence CVE CVE-2024-57888 https://www.cve.org/CVERecord?id=CVE-2024-57888 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57893 https://www.cve.org/CVERecord?id=CVE-2024-57893 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57899 https://www.cve.org/CVERecord?id=CVE-2024-57899 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 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=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 https://www.cve.org/CVERecord?id=CVE-2024-57912 Référence CVE CVE-2024-57913 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

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

d?id=CVE-2024-57876 Référence CVE CVE-2024-57887 https://www.cve.org/CVERecord?id=CVE-2024-57887 Référence CVE CVE-2024-57888 https://www.cve.org/CVERecord?id=CVE-2024-57888 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57893 https://www.cve.org/CVERecord?id=CVE-2024-57893 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57899 https://www.cve.org/CVERecord?id=CVE-2024-57899 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 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=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=CVE-2024-57910 Référence CVE CVE-2024-57911 https://www.cve.org/CVERecord?id=CVE-2024-57911 Référence CVE CVE-2024-57912 https://www.cve.org/CVERecord?id=CVE-2024-57912 Référence CVE CVE-2024-57913 https://www.cve.org/CVERecord?id=

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2024-028472Linux の Linux Kernel におけるリソースのロックに関する脆弱性

Linux の Linux Kernel には、リソースのロックに関する脆弱性が存在します。

Official advisory ↗

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: kernel-default as component of SLES-LTSS-TERADATA 15 SP2
kernel-source as component of SLES-LTSS-TERADATA 15 SP2
kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
kernel-default as component of SUSE Linux Enterprise High Availability Extension 12 SP5
kernel-source as component of SUSE Linux Enterprise High Availability Extension 12 SP5
kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP5
kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-devel-azure as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-source-azure as component of SUSE Linux Enterprise High Performance Computing 12 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
and 309 more
Fixed: Linux: < 5.4, 5.15.176 ≤ 5.15.*, 6.1.124 ≤ 6.1.*, 6.6.70 ≤ 6.6.*, 6.12.9 ≤ 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.

Evidence and provenance

Published 15 Jan 2025 · Last source change 23 May 2026, 15:56 UTC · CWE-667 · Improper Locking

CVE recordCVE.org · 5.2

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2024-53806

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 ↗

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

2025-01-15CVE published

2026-05-23Fixed release or patch reference recorded

ENISA EUVD · EUVD-2024-53806↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

net: restrict SO_REUSEPORT to inet sockets

Published severity in operational context

Evidence used

Compensating controls

Verification

Remediation availability differs by product scope

Release-specific package status

Authoritative vendor CSAF and VEX advisories

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2024-53806

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication