BlackTreeIndependent security intelligence

Full vulnerability report · 2024

CVE-2024-53100High confidence

nvme: tcp: avoid race between queue_lock lock and destroy

Linux · Linux

7.8HighCVSS 3.1

Recommended action

Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

19 package states

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.

Ubuntu release	Source package	Vendor state	Fixed version	Evidence
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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 2026

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-50516

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state: Present in the current official mapping
Known exploitation: Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score: Not supplied in the stored EUVD record
Advisory evidence: No linked advisory details stored yet

Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

What, why and how

In the Linux kernel, the following vulnerability has been resolved: nvme: tcp: avoid race between queue_lock lock and destroy Commit 76d54bf20cdc ("nvme-tcp: don't access released socket during error recovery") added a mutex_lock() call for the queue->queue_lock in nvme_tcp_get_address(). However, the mutex_lock() races with mutex_destroy() in nvme_tcp_free_queue(), and causes the WARN below. DEBUG_LOCKS_WARN_ON(lock->magic != lock) WARNING: CPU: 3 PID: 34077 at kernel/locking/mutex.c:587 __mutex_lock+0xcf0/0x1220 Modules linked in: nvmet_tcp nvmet nvme_tcp nvme_fabrics iw_cm ib_cm ib_core pktcdvd nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables qrtr sunrpc ppdev 9pnet_virtio 9pnet pcspkr netfs parport_pc parport e1000 i2c_piix4 i2c_smbus loop fuse nfnetlink zram bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper xfs drm sym53c8xx floppy nvme scsi_transport_spi nvme_core nvme_auth serio_raw ata_generic pata_acpi dm_multipath qemu_fw_cfg [last unloaded: ib_uverbs] CPU: 3 UID: 0 PID: 34077 Comm: udisksd Not tainted 6.11.0-rc7 #319 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014 RIP: 0010:__mutex_lock+0xcf0/0x1220 Code: 08 84 d2 0f 85 c8 04 00 00 8b 15 ef b6 c8 01 85 d2 0f 85 78 f4 ff ff 48 c7 c6 20 93 ee af 48 c7 c7 60 91 ee af e8 f0 a7 6d fd <0f> 0b e9 5e f4 ff ff 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 RSP: 0018:ffff88811305f760 EFLAGS: 00010286 RAX: 0000000000000000 RBX: ffff88812c652058 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000001 RBP: ffff88811305f8b0 R08: 0000000000000001 R09: ffffed1075c36341 R10: ffff8883ae1b1a0b R11: 0000000000010498 R12: 0000000000000000 R13: 0000000000000000 R14: dffffc0000000000 R15: ffff88812c652058 FS: 00007f9713ae4980(0000) GS:ffff8883ae180000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fcd78483c7c CR3: 0000000122c38000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? __warn.cold+0x5b/0x1af ? __mutex_lock+0xcf0/0x1220 ? report_bug+0x1ec/0x390 ? handle_bug+0x3c/0x80 ? exc_invalid_op+0x13/0x40 ? asm_exc_invalid_op+0x16/0x20 ? __mutex_lock+0xcf0/0x1220 ? nvme_tcp_get_address+0xc2/0x1e0 [nvme_tcp] ? __pfx___mutex_lock+0x10/0x10 ? __lock_acquire+0xd6a/0x59e0 ? nvme_tcp_get_address+0xc2/0x1e0 [nvme_tcp] nvme_tcp_get_address+0xc2/0x1e0 [nvme_tcp] ? __pfx_nvme_tcp_get_address+0x10/0x10 [nvme_tcp] nvme_sysfs_show_address+0x81/0xc0 [nvme_core] dev_attr_show+0x42/0x80 ? __asan_memset+0x1f/0x40 sysfs_kf_seq_show+0x1f0/0x370 seq_read_iter+0x2cb/0x1130 ? rw_verify_area+0x3b1/0x590 ? __mutex_lock+0x433/0x1220 vfs_read+0x6a6/0xa20 ? lockdep_hardirqs_on+0x78/0x100 ? __pfx_vfs_read+0x10/0x10 ksys_read+0xf7/0x1d0 ? __pfx_ksys_read+0x10/0x10 ? __x64_sys_openat+0x105/0x1d0 do_syscall_64+0x93/0x180 ? lockdep_hardirqs_on_prepare+0x16d/0x400 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on+0x78/0x100 ? do_syscall_64+0x9f/0x180 ? __pfx_ksys_read+0x10/0x10 ? lockdep_hardirqs_on_prepare+0x16d/0x400 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on+0x78/0x100 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on_prepare+0x16d/0x400 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on+0x78/0x100 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on_prepare+0x16d/0x400 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on+0x78/0x100 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on_prepare+0x16d/0x400 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on+0x78/0x100 ? do_syscall_64+0x9f/0x180 ? do_syscall_64+0x9f/0x180 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f9713f55cfa Code: 55 48 89 e5 48 83 ec 20 48 89 55 e8 48 89 75 f0 89 7d f8 e8 e8 74 f8 ff 48 8b 55 e8 48 8b 75 f0 4 ---truncated---

What

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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

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 → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → 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-362 ↗
CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
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-362

Official authority intelligence

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

ENISA EUVD · EUVD-2024-50516Official EUVD mapping

0 linked advisory records.

Official EUVD record

BSI · German · WID-SEC-W-2024-3547Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory

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

d?id=CVE-2024-53088 Référence CVE CVE-2024-53089 https://www.cve.org/CVERecord?id=CVE-2024-53089 Référence CVE CVE-2024-53090 https://www.cve.org/CVERecord?id=CVE-2024-53090 Référence CVE CVE-2024-53091 https://www.cve.org/CVERecord?id=CVE-2024-53091 Référence CVE CVE-2024-53093 https://www.cve.org/CVERecord?id=CVE-2024-53093 Référence CVE CVE-2024-53094 https://www.cve.org/CVERecord?id=CVE-2024-53094 Référence CVE CVE-2024-53095 https://www.cve.org/CVERecord?id=CVE-2024-53095 Référence CVE CVE-2024-53096 https://www.cve.org/CVERecord?id=CVE-2024-53096 Référence CVE CVE-2024-53099 https://www.cve.org/CVERecord?id=CVE-2024-53099 Référence CVE CVE-2024-53100 https://www.cve.org/CVERecord?id=CVE-2024-53100 Référence CVE CVE-2024-53101 https://www.cve.org/CVERecord?id=CVE-2024-53101 Référence CVE CVE-2024-53103 https://www.cve.org/CVERecord?id=CVE-2024-53103 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53105 https://www.cve.org/CVERecord?id=CVE-2024-53105 Référence CVE CVE-2024-53106 https://www.cve.org/CVERecord?id=CVE-2024-53106 Référence CVE CVE-2024-53107 https://www.cve.org/CVERecord?id=CVE-2024-53107 Référence CVE CVE-2024-53108 https://www.cve.org/CVERecord?id=CVE-2024-53108 Référence CVE CVE-2024-53109 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-53089 Référence CVE CVE-2024-53090 https://www.cve.org/CVERecord?id=CVE-2024-53090 Référence CVE CVE-2024-53091 https://www.cve.org/CVERecord?id=CVE-2024-53091 Référence CVE CVE-2024-53093 https://www.cve.org/CVERecord?id=CVE-2024-53093 Référence CVE CVE-2024-53094 https://www.cve.org/CVERecord?id=CVE-2024-53094 Référence CVE CVE-2024-53095 https://www.cve.org/CVERecord?id=CVE-2024-53095 Référence CVE CVE-2024-53096 https://www.cve.org/CVERecord?id=CVE-2024-53096 Référence CVE CVE-2024-53097 https://www.cve.org/CVERecord?id=CVE-2024-53097 Référence CVE CVE-2024-53099 https://www.cve.org/CVERecord?id=CVE-2024-53099 Référence CVE CVE-2024-53100 https://www.cve.org/CVERecord?id=CVE-2024-53100 Référence CVE CVE-2024-53101 https://www.cve.org/CVERecord?id=CVE-2024-53101 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53105 https://www.cve.org/CVERecord?id=CVE-2024-53105 Référence CVE CVE-2024-53106 https://www.cve.org/CVERecord?id=CVE-2024-53106 Référence CVE CVE-2024-53107 https://www.cve.org/CVERecord?id=CVE-2024-53107 Référence CVE CVE-2024-53108 https://www.cve.org/CVERecord?id=CVE-2024-53108 Référence CVE CVE-2024-53109 https://www.cve.org/CVERecord?id=CVE-2024-53109 Référence CVE CVE-2024-53110 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2024-53090 Référence CVE CVE-2024-53091 https://www.cve.org/CVERecord?id=CVE-2024-53091 Référence CVE CVE-2024-53092 https://www.cve.org/CVERecord?id=CVE-2024-53092 Référence CVE CVE-2024-53093 https://www.cve.org/CVERecord?id=CVE-2024-53093 Référence CVE CVE-2024-53094 https://www.cve.org/CVERecord?id=CVE-2024-53094 Référence CVE CVE-2024-53095 https://www.cve.org/CVERecord?id=CVE-2024-53095 Référence CVE CVE-2024-53097 https://www.cve.org/CVERecord?id=CVE-2024-53097 Référence CVE CVE-2024-53098 https://www.cve.org/CVERecord?id=CVE-2024-53098 Référence CVE CVE-2024-53099 https://www.cve.org/CVERecord?id=CVE-2024-53099 Référence CVE CVE-2024-53100 https://www.cve.org/CVERecord?id=CVE-2024-53100 Référence CVE CVE-2024-53101 https://www.cve.org/CVERecord?id=CVE-2024-53101 Référence CVE CVE-2024-53103 https://www.cve.org/CVERecord?id=CVE-2024-53103 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53105 https://www.cve.org/CVERecord?id=CVE-2024-53105 Référence CVE CVE-2024-53106 https://www.cve.org/CVERecord?id=CVE-2024-53106 Référence CVE CVE-2024-53107 https://www.cve.org/CVERecord?id=CVE-2024-53107 Référence CVE CVE-2024-53108 https://www.cve.org/CVERecord?id=CVE-2024-53108 Référence CVE CVE-2024-53109 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2024-53089 Référence CVE CVE-2024-53090 https://www.cve.org/CVERecord?id=CVE-2024-53090 Référence CVE CVE-2024-53091 https://www.cve.org/CVERecord?id=CVE-2024-53091 Référence CVE CVE-2024-53092 https://www.cve.org/CVERecord?id=CVE-2024-53092 Référence CVE CVE-2024-53093 https://www.cve.org/CVERecord?id=CVE-2024-53093 Référence CVE CVE-2024-53094 https://www.cve.org/CVERecord?id=CVE-2024-53094 Référence CVE CVE-2024-53095 https://www.cve.org/CVERecord?id=CVE-2024-53095 Référence CVE CVE-2024-53098 https://www.cve.org/CVERecord?id=CVE-2024-53098 Référence CVE CVE-2024-53099 https://www.cve.org/CVERecord?id=CVE-2024-53099 Référence CVE CVE-2024-53100 https://www.cve.org/CVERecord?id=CVE-2024-53100 Référence CVE CVE-2024-53101 https://www.cve.org/CVERecord?id=CVE-2024-53101 Référence CVE CVE-2024-53103 https://www.cve.org/CVERecord?id=CVE-2024-53103 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53105 https://www.cve.org/CVERecord?id=CVE-2024-53105 Référence CVE CVE-2024-53106 https://www.cve.org/CVERecord?id=CVE-2024-53106 Référence CVE CVE-2024-53107 https://www.cve.org/CVERecord?id=CVE-2024-53107 Référence CVE CVE-2024-53108 https://www.cve.org/CVERecord?id=CVE-2024-53108 Référence CVE CVE-2024-53109 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2024-53066 Référence CVE CVE-2024-53070 https://www.cve.org/CVERecord?id=CVE-2024-53070 Référence CVE CVE-2024-53072 https://www.cve.org/CVERecord?id=CVE-2024-53072 Référence CVE CVE-2024-53081 https://www.cve.org/CVERecord?id=CVE-2024-53081 Référence CVE CVE-2024-53082 https://www.cve.org/CVERecord?id=CVE-2024-53082 Référence CVE CVE-2024-53088 https://www.cve.org/CVERecord?id=CVE-2024-53088 Référence CVE CVE-2024-53093 https://www.cve.org/CVERecord?id=CVE-2024-53093 Référence CVE CVE-2024-53096 https://www.cve.org/CVERecord?id=CVE-2024-53096 Référence CVE CVE-2024-53097 https://www.cve.org/CVERecord?id=CVE-2024-53097 Référence CVE CVE-2024-53100 https://www.cve.org/CVERecord?id=CVE-2024-53100 Référence CVE CVE-2024-53101 https://www.cve.org/CVERecord?id=CVE-2024-53101 Référence CVE CVE-2024-53103 https://www.cve.org/CVERecord?id=CVE-2024-53103 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53106 https://www.cve.org/CVERecord?id=CVE-2024-53106 Référence CVE CVE-2024-53110 https://www.cve.org/CVERecord?id=CVE-2024-53110 Référence CVE CVE-2024-53112 https://www.cve.org/CVERecord?id=CVE-2024-53112 Référence CVE CVE-2024-53113 https://www.cve.org/CVERecord?id=CVE-2024-53113 Référence CVE CVE-2024-53119 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2024-53079 Référence CVE CVE-2024-53081 https://www.cve.org/CVERecord?id=CVE-2024-53081 Référence CVE CVE-2024-53082 https://www.cve.org/CVERecord?id=CVE-2024-53082 Référence CVE CVE-2024-53085 https://www.cve.org/CVERecord?id=CVE-2024-53085 Référence CVE CVE-2024-53088 https://www.cve.org/CVERecord?id=CVE-2024-53088 Référence CVE CVE-2024-53093 https://www.cve.org/CVERecord?id=CVE-2024-53093 Référence CVE CVE-2024-53094 https://www.cve.org/CVERecord?id=CVE-2024-53094 Référence CVE CVE-2024-53095 https://www.cve.org/CVERecord?id=CVE-2024-53095 Référence CVE CVE-2024-53096 https://www.cve.org/CVERecord?id=CVE-2024-53096 Référence CVE CVE-2024-53100 https://www.cve.org/CVERecord?id=CVE-2024-53100 Référence CVE CVE-2024-53101 https://www.cve.org/CVERecord?id=CVE-2024-53101 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53106 https://www.cve.org/CVERecord?id=CVE-2024-53106 Référence CVE CVE-2024-53108 https://www.cve.org/CVERecord?id=CVE-2024-53108 Référence CVE CVE-2024-53110 https://www.cve.org/CVERecord?id=CVE-2024-53110 Référence CVE CVE-2024-53112 https://www.cve.org/CVERecord?id=CVE-2024-53112 Référence CVE CVE-2024-53114 https://www.cve.org/CVERecord?id=CVE-2024-53114 Référence CVE CVE-2024-53121 https://www.cve.org/CVERecord?id=

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.: Patch available
Affected: 3f2304f8c6d6ed97849057bd16fee99e434ca796 < 4f946479b326a3cbb193f2b8368aed9269514c35; 3f2304f8c6d6ed97849057bd16fee99e434ca796 < 975cb1d2121511584695d0e47fdb90e6782da007; 3f2304f8c6d6ed97849057bd16fee99e434ca796 < e15cebc1b21856944b387f4abd03b66bd3d4f027; 3f2304f8c6d6ed97849057bd16fee99e434ca796 < 782373ba27660ba7d330208cf5509ece6feb4545; 5.0
Fixed: < 5.0; 6.1.118 ≤ 6.1.*; 6.6.62 ≤ 6.6.*; 6.11.9 ≤ 6.11.*; 6.12 ≤ *
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 25 Nov 2024 · Last source change 5 Aug 2026, 11:43 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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-50516

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceCISA ADP

NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates →

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

2024-11-25CVE published

2026-08-05Fixed release or patch reference recorded

ENISA EUVD · EUVD-2024-50516↗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.

nvme: tcp: avoid race between queue_lock lock and destroy

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

EUVD-2024-50516

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

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