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

sock_map: avoid race between sock_map_close and sk_psock_put

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 13 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 5 Aug 2026

Evidence used

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

17 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 13 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.9.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.99-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

1 current
CVE-2024-39500 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: sock_map: avoid race between sock_map_close and sk_psock_put
98 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 7
  • kernel as a component of Red Hat Enterprise Linux 7
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 7
  • kernel-debug as a component of Red Hat Enterprise Linux 7
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 7
  • kernel-devel as a component of Red Hat Enterprise Linux 7
  • kernel-doc as a component of Red Hat Enterprise Linux 7
  • kernel-headers as a component of Red Hat Enterprise Linux 7
  • kernel-kdump as a component of Red Hat Enterprise Linux 7
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 7
  • kernel-rt as a component of Red Hat Enterprise Linux 7
Summary
A flaw was found in the Linux kernel's `sock_map` component. A local attacker could exploit a race condition between the `sock_map_close` and `sk_psock_put` functions. This race condition can lead to a null pointer dereference, which triggers a kernel warning and may result in a denial of service.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
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-38026

No EUVD known-exploited evidence

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

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 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: sock_map: avoid race between sock_map_close and sk_psock_put sk_psock_get will return NULL if the refcount of psock has gone to 0, which will happen when the last call of sk_psock_put is done. However, sk_psock_drop may not have finished yet, so the close callback will still point to sock_map_close despite psock being NULL. This can be reproduced with a thread deleting an element from the sock map, while the second one creates a socket, adds it to the map and closes it. That will trigger the WARN_ON_ONCE: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 7220 at net/core/sock_map.c:1701 sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701 Modules linked in: CPU: 1 PID: 7220 Comm: syz-executor380 Not tainted 6.9.0-syzkaller-07726-g3c999d1ae3c7 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 RIP: 0010:sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701 Code: df e8 92 29 88 f8 48 8b 1b 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 79 29 88 f8 4c 8b 23 eb 89 e8 4f 15 23 f8 90 <0f> 0b 90 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d e9 13 26 3d 02 RSP: 0018:ffffc9000441fda8 EFLAGS: 00010293 RAX: ffffffff89731ae1 RBX: ffffffff94b87540 RCX: ffff888029470000 RDX: 0000000000000000 RSI: ffffffff8bcab5c0 RDI: ffffffff8c1faba0 RBP: 0000000000000000 R08: ffffffff92f9b61f R09: 1ffffffff25f36c3 R10: dffffc0000000000 R11: fffffbfff25f36c4 R12: ffffffff89731840 R13: ffff88804b587000 R14: ffff88804b587000 R15: ffffffff89731870 FS: 000055555e080380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000000207d4000 CR4: 0000000000350ef0 Call Trace: <TASK> unix_release+0x87/0xc0 net/unix/af_unix.c:1048 __sock_release net/socket.c:659 [inline] sock_close+0xbe/0x240 net/socket.c:1421 __fput+0x42b/0x8a0 fs/file_table.c:422 __do_sys_close fs/open.c:1556 [inline] __se_sys_close fs/open.c:1541 [inline] __x64_sys_close+0x7f/0x110 fs/open.c:1541 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fb37d618070 Code: 00 00 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d4 e8 10 2c 00 00 80 3d 31 f0 07 00 00 74 17 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c RSP: 002b:00007ffcd4a525d8 EFLAGS: 00000202 ORIG_RAX: 0000000000000003 RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007fb37d618070 RDX: 0000000000000010 RSI: 00000000200001c0 RDI: 0000000000000004 RBP: 0000000000000000 R08: 0000000100000000 R09: 0000000100000000 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> Use sk_psock, which will only check that the pointer is not been set to NULL yet, which should only happen after the callbacks are restored. If, then, a reference can still be gotten, we may call sk_psock_stop and cancel psock->work. As suggested by Paolo Abeni, reorder the condition so the control flow is less convoluted. After that change, the reproducer does not trigger the WARN_ON_ONCE anymore.

What

In the Linux kernel, the following vulnerability has been resolved: sock_map: avoid race between sock_map_close and sk_psock_put sk_psock_get will return NULL if the refcount of psock has gone to 0, which will happen when the last call of sk_psock_put is done. However, sk_psock_drop may not have finished yet, so the close callback will still point to sock_map_close despite psock being NULL. This can be reproduced with a thread deleting an element from the sock map, while the second one creates a socket, adds it to the map and closes it. That will trigger the WARN_ON_ONCE: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 7220 at net/core/sock_map.c:1701 sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701 Modules linked in: CPU: 1 PID: 7220 Comm: syz-executor380 Not tainted 6.9.0-syzkaller-07726-g3c999d1ae3c7 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 RIP: 0010:sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701 Code: df e8 92 29 88 f8 48 8b 1b 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 79 29 88 f8 4c 8b 23 eb 89 e8 4f 15 23 f8 90 <0f> 0b 90 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d e9 13 26 3d 02 RSP: 0018:ffffc9000441fda8 EFLAGS: 00010293 RAX: ffffffff89731ae1 RBX: ffffffff94b87540 RCX: ffff888029470000 RDX: 0000000000000000 RSI: ffffffff8bcab5c0 RDI: ffffffff8c1faba0 RBP: 0000000000000000 R08: ffffffff92f9b61f R09: 1ffffffff25f36c3 R10: dffffc0000000000 R11: fffffbfff25f36c4 R12: ffffffff89731840 R13: ffff88804b587000 R14: ffff88804b587000 R15: ffffffff89731870 FS: 000055555e080380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000000207d4000 CR4: 0000000000350ef0 Call Trace: <TASK> unix_release+0x87/0xc0 net/unix/af_unix.c:1048 __sock_release net/socket.c:659 [inline] sock_close+0xbe/0x240 net/socket.c:1421 __fput+0x42b/0x8a0 fs/file_table.c:422 __do_sys_close fs/open.c:1556 [inline] __se_sys_close fs/open.c:1541 [inline] __x64_sys_close+0x7f/0x110 fs/open.c:1541 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fb37d618070 Code: 00 00 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d4 e8 10 2c 00 00 80 3d 31 f0 07 00 00 74 17 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c RSP: 002b:00007ffcd4a525d8 EFLAGS: 00000202 ORIG_RAX: 0000000000000003 RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007fb37d618070 RDX: 0000000000000010 RSI: 00000000200001c0 RDI: 0000000000000004 RBP: 0000000000000000 R08: 0000000100000000 R09: 0000000100000000 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> Use sk_psock, which will only check that the pointer is not been set to NULL yet, which should only happen after the callbacks are restored. If, then, a reference can still be gotten, we may call sk_psock_stop and cancel psock->work. As suggested by Paolo Abeni, reorder the condition so the control flow is less convoluted. After that change, the reproducer does not trigger the WARN_ON_ONCE anymore.

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

In the Linux kernel, the following vulnerability has been resolved: sock_map: avoid race between sock_map_close and sk_psock_put sk_psock_get will return NULL if the refcount of psock has gone to 0, which will happen when the last call of sk_psock_put is done. However, sk_psock_drop may not have finished yet, so the close callback will still point to sock_map_close despite psock being NULL. This can be reproduced with a thread deleting an element from the sock map, while the second one creates a socket, adds it to the map and closes it. That will trigger the WARN_ON_ONCE: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 7220 at net/core/sock_map.c:1701 sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701 Modules linked in: CPU: 1 PID: 7220 Comm: syz-executor380 Not tainted 6.9.0-syzkaller-07726-g3c999d1ae3c7 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 RIP: 0010:sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701 Code: df e8 92 29 88 f8 48 8b 1b 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 79 29 88 f8 4c 8b 23 eb 89 e8 4f 15 23 f8 90 <0f> 0b 90 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d e9 13 26 3d 02 RSP: 0018:ffffc9000441fda8 EFLAGS: 00010293 RAX: ffffffff89731ae1 RBX: ffffffff94b87540 RCX: ffff888029470000 RDX: 0000000000000000 RSI: ffffffff8bcab5c0 RDI: ffffffff8c1faba0 RBP: 0000000000000000 R08: ffffffff92f9b61f R09: 1ffffffff25f36c3 R10: dffffc0000000000 R11: fffffbfff25f36c4 R12: ffffffff89731840 R13: ffff88804b587000 R14: ffff88804b587000 R15: ffffffff89731870 FS: 000055555e080380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000000207d4000 CR4: 0000000000350ef0 Call Trace: <TASK> unix_release+0x87/0xc0 net/unix/af_unix.c:1048 __sock_release net/socket.c:659 [inline] sock_close+0xbe/0x240 net/socket.c:1421 __fput+0x42b/0x8a0 fs/file_table.c:422 __do_sys_close fs/open.c:1556 [inline] __se_sys_close fs/open.c:1541 [inline] __x64_sys_close+0x7f/0x110 fs/open.c:1541 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fb37d618070 Code: 00 00 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d4 e8 10 2c 00 00 80 3d 31 f0 07 00 00 74 17 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c RSP: 002b:00007ffcd4a525d8 EFLAGS: 00000202 ORIG_RAX: 0000000000000003 RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007fb37d618070 RDX: 0000000000000010 RSI: 00000000200001c0 RDI: 0000000000000004 RBP: 0000000000000000 R08: 0000000100000000 R09: 0000000100000000 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> Use sk_psock, which will only check that the pointer is not been set to NULL yet, which should only happen after the callbacks are restored. If, then, a reference can still be gotten, we may call sk_psock_stop and cancel psock->work. As suggested by Paolo Abeni, reorder the condition so the control flow is less convoluted. After that change, the reproducer does not trigger the WARN_ON_ONCE anymore.

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.

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 → 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
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-2855IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand zu verursachen oder andere, nicht spezifizierte Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-1607Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um seine Privilegien zu erweitern, einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen oder einen unspezifischen Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240717Security Bulletin 17 Jul 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 17 Jul 2024, published on 17 July 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2024-38629 Référence CVE CVE-2024-38632 https://www.cve.org/CVERecord?id=CVE-2024-38632 Référence CVE CVE-2024-39291 https://www.cve.org/CVERecord?id=CVE-2024-39291 Référence CVE CVE-2024-39298 https://www.cve.org/CVERecord?id=CVE-2024-39298 Référence CVE CVE-2024-39479 https://www.cve.org/CVERecord?id=CVE-2024-39479 Référence CVE CVE-2024-39486 https://www.cve.org/CVERecord?id=CVE-2024-39486 Référence CVE CVE-2024-39491 https://www.cve.org/CVERecord?id=CVE-2024-39491 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-39498 https://www.cve.org/CVERecord?id=CVE-2024-39498 Référence CVE CVE-2024-39500 https://www.cve.org/CVERecord?id=CVE-2024-39500 Référence CVE CVE-2024-4030 https://www.cve.org/CVERecord?id=CVE-2024-4030 Référence CVE CVE-2024-4032 https://www.cve.org/CVERecord?id=CVE-2024-4032 Référence CVE CVE-2024-40900 https://www.cve.org/CVERecord?id=CVE-2024-40900 Référence CVE CVE-2024-40903 https://www.cve.org/CVERecord?id=CVE-2024-40903 Référence CVE CVE-2024-40907 https://www.cve.org/CVERecord?id=CVE-2024-40907 Référence CVE CVE-2024-40908 https://www.cve.org/CVERecord?id=CVE-2024-40908 Référence CVE CVE-2024-40913 https://www.cve.org/CVERecord?id=CVE-2024-40913 Référence CVE CVE-2024-40919 https://www.cve.org/CVERecord?id=CVE-

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

d?id=CVE-2024-39472 Référence CVE CVE-2024-39474 https://www.cve.org/CVERecord?id=CVE-2024-39474 Référence CVE CVE-2024-39484 https://www.cve.org/CVERecord?id=CVE-2024-39484 Référence CVE CVE-2024-39487 https://www.cve.org/CVERecord?id=CVE-2024-39487 Référence CVE CVE-2024-39494 https://www.cve.org/CVERecord?id=CVE-2024-39494 Référence CVE CVE-2024-39495 https://www.cve.org/CVERecord?id=CVE-2024-39495 Référence CVE CVE-2024-39496 https://www.cve.org/CVERecord?id=CVE-2024-39496 Référence CVE CVE-2024-39497 https://www.cve.org/CVERecord?id=CVE-2024-39497 Référence CVE CVE-2024-39499 https://www.cve.org/CVERecord?id=CVE-2024-39499 Référence CVE CVE-2024-39500 https://www.cve.org/CVERecord?id=CVE-2024-39500 Référence CVE CVE-2024-39501 https://www.cve.org/CVERecord?id=CVE-2024-39501 Référence CVE CVE-2024-39502 https://www.cve.org/CVERecord?id=CVE-2024-39502 Référence CVE CVE-2024-39503 https://www.cve.org/CVERecord?id=CVE-2024-39503 Référence CVE CVE-2024-39505 https://www.cve.org/CVERecord?id=CVE-2024-39505 Référence CVE CVE-2024-39506 https://www.cve.org/CVERecord?id=CVE-2024-39506 Référence CVE CVE-2024-39507 https://www.cve.org/CVERecord?id=CVE-2024-39507 Référence CVE CVE-2024-39509 https://www.cve.org/CVERecord?id=CVE-2024-39509 Référence CVE CVE-2024-39510 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-39483 Référence CVE CVE-2024-39484 https://www.cve.org/CVERecord?id=CVE-2024-39484 Référence CVE CVE-2024-39486 https://www.cve.org/CVERecord?id=CVE-2024-39486 Référence CVE CVE-2024-39488 https://www.cve.org/CVERecord?id=CVE-2024-39488 Référence CVE CVE-2024-39489 https://www.cve.org/CVERecord?id=CVE-2024-39489 Référence CVE CVE-2024-39491 https://www.cve.org/CVERecord?id=CVE-2024-39491 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-39497 https://www.cve.org/CVERecord?id=CVE-2024-39497 Référence CVE CVE-2024-39499 https://www.cve.org/CVERecord?id=CVE-2024-39499 Référence CVE CVE-2024-39500 https://www.cve.org/CVERecord?id=CVE-2024-39500 Référence CVE CVE-2024-39501 https://www.cve.org/CVERecord?id=CVE-2024-39501 Référence CVE CVE-2024-39505 https://www.cve.org/CVERecord?id=CVE-2024-39505 Référence CVE CVE-2024-39506 https://www.cve.org/CVERecord?id=CVE-2024-39506 Référence CVE CVE-2024-39508 https://www.cve.org/CVERecord?id=CVE-2024-39508 Référence CVE CVE-2024-39509 https://www.cve.org/CVERecord?id=CVE-2024-39509 Référence CVE CVE-2024-39510 https://www.cve.org/CVERecord?id=CVE-2024-39510 Référence CVE CVE-2024-40899 https://www.cve.org/CVERecord?id=CVE-2024-40899 Référence CVE CVE-2024-40900 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-39491 Référence CVE CVE-2024-39492 https://www.cve.org/CVERecord?id=CVE-2024-39492 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-39494 https://www.cve.org/CVERecord?id=CVE-2024-39494 Référence CVE CVE-2024-39495 https://www.cve.org/CVERecord?id=CVE-2024-39495 Référence CVE CVE-2024-39496 https://www.cve.org/CVERecord?id=CVE-2024-39496 Référence CVE CVE-2024-39497 https://www.cve.org/CVERecord?id=CVE-2024-39497 Référence CVE CVE-2024-39498 https://www.cve.org/CVERecord?id=CVE-2024-39498 Référence CVE CVE-2024-39499 https://www.cve.org/CVERecord?id=CVE-2024-39499 Référence CVE CVE-2024-39500 https://www.cve.org/CVERecord?id=CVE-2024-39500 Référence CVE CVE-2024-39501 https://www.cve.org/CVERecord?id=CVE-2024-39501 Référence CVE CVE-2024-39502 https://www.cve.org/CVERecord?id=CVE-2024-39502 Référence CVE CVE-2024-39503 https://www.cve.org/CVERecord?id=CVE-2024-39503 Référence CVE CVE-2024-39504 https://www.cve.org/CVERecord?id=CVE-2024-39504 Référence CVE CVE-2024-39505 https://www.cve.org/CVERecord?id=CVE-2024-39505 Référence CVE CVE-2024-39506 https://www.cve.org/CVERecord?id=CVE-2024-39506 Référence CVE CVE-2024-39507 https://www.cve.org/CVERecord?id=CVE-2024-39507 Référence CVE CVE-2024-39508 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-39491 Référence CVE CVE-2024-39492 https://www.cve.org/CVERecord?id=CVE-2024-39492 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-39494 https://www.cve.org/CVERecord?id=CVE-2024-39494 Référence CVE CVE-2024-39495 https://www.cve.org/CVERecord?id=CVE-2024-39495 Référence CVE CVE-2024-39496 https://www.cve.org/CVERecord?id=CVE-2024-39496 Référence CVE CVE-2024-39497 https://www.cve.org/CVERecord?id=CVE-2024-39497 Référence CVE CVE-2024-39498 https://www.cve.org/CVERecord?id=CVE-2024-39498 Référence CVE CVE-2024-39499 https://www.cve.org/CVERecord?id=CVE-2024-39499 Référence CVE CVE-2024-39500 https://www.cve.org/CVERecord?id=CVE-2024-39500 Référence CVE CVE-2024-39501 https://www.cve.org/CVERecord?id=CVE-2024-39501 Référence CVE CVE-2024-39502 https://www.cve.org/CVERecord?id=CVE-2024-39502 Référence CVE CVE-2024-39503 https://www.cve.org/CVERecord?id=CVE-2024-39503 Référence CVE CVE-2024-39504 https://www.cve.org/CVERecord?id=CVE-2024-39504 Référence CVE CVE-2024-39505 https://www.cve.org/CVERecord?id=CVE-2024-39505 Référence CVE CVE-2024-39506 https://www.cve.org/CVERecord?id=CVE-2024-39506 Référence CVE CVE-2024-39507 https://www.cve.org/CVERecord?id=CVE-2024-39507 Référence CVE CVE-2024-39508 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-39483 Référence CVE CVE-2024-39484 https://www.cve.org/CVERecord?id=CVE-2024-39484 Référence CVE CVE-2024-39486 https://www.cve.org/CVERecord?id=CVE-2024-39486 Référence CVE CVE-2024-39488 https://www.cve.org/CVERecord?id=CVE-2024-39488 Référence CVE CVE-2024-39489 https://www.cve.org/CVERecord?id=CVE-2024-39489 Référence CVE CVE-2024-39491 https://www.cve.org/CVERecord?id=CVE-2024-39491 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-39497 https://www.cve.org/CVERecord?id=CVE-2024-39497 Référence CVE CVE-2024-39499 https://www.cve.org/CVERecord?id=CVE-2024-39499 Référence CVE CVE-2024-39500 https://www.cve.org/CVERecord?id=CVE-2024-39500 Référence CVE CVE-2024-39501 https://www.cve.org/CVERecord?id=CVE-2024-39501 Référence CVE CVE-2024-39505 https://www.cve.org/CVERecord?id=CVE-2024-39505 Référence CVE CVE-2024-39506 https://www.cve.org/CVERecord?id=CVE-2024-39506 Référence CVE CVE-2024-39508 https://www.cve.org/CVERecord?id=CVE-2024-39508 Référence CVE CVE-2024-39509 https://www.cve.org/CVERecord?id=CVE-2024-39509 Référence CVE CVE-2024-39510 https://www.cve.org/CVERecord?id=CVE-2024-39510 Référence CVE CVE-2024-40899 https://www.cve.org/CVERecord?id=CVE-2024-40899 Référence CVE CVE-2024-40900 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-39491 Référence CVE CVE-2024-39492 https://www.cve.org/CVERecord?id=CVE-2024-39492 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-39494 https://www.cve.org/CVERecord?id=CVE-2024-39494 Référence CVE CVE-2024-39495 https://www.cve.org/CVERecord?id=CVE-2024-39495 Référence CVE CVE-2024-39496 https://www.cve.org/CVERecord?id=CVE-2024-39496 Référence CVE CVE-2024-39497 https://www.cve.org/CVERecord?id=CVE-2024-39497 Référence CVE CVE-2024-39498 https://www.cve.org/CVERecord?id=CVE-2024-39498 Référence CVE CVE-2024-39499 https://www.cve.org/CVERecord?id=CVE-2024-39499 Référence CVE CVE-2024-39500 https://www.cve.org/CVERecord?id=CVE-2024-39500 Référence CVE CVE-2024-39501 https://www.cve.org/CVERecord?id=CVE-2024-39501 Référence CVE CVE-2024-39502 https://www.cve.org/CVERecord?id=CVE-2024-39502 Référence CVE CVE-2024-39503 https://www.cve.org/CVERecord?id=CVE-2024-39503 Référence CVE CVE-2024-39504 https://www.cve.org/CVERecord?id=CVE-2024-39504 Référence CVE CVE-2024-39505 https://www.cve.org/CVERecord?id=CVE-2024-39505 Référence CVE CVE-2024-39506 https://www.cve.org/CVERecord?id=CVE-2024-39506 Référence CVE CVE-2024-39507 https://www.cve.org/CVERecord?id=CVE-2024-39507 Référence CVE CVE-2024-39508 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-39487 Référence CVE CVE-2024-39488 https://www.cve.org/CVERecord?id=CVE-2024-39488 Référence CVE CVE-2024-39490 https://www.cve.org/CVERecord?id=CVE-2024-39490 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-39494 https://www.cve.org/CVERecord?id=CVE-2024-39494 Référence CVE CVE-2024-39496 https://www.cve.org/CVERecord?id=CVE-2024-39496 Référence CVE CVE-2024-39497 https://www.cve.org/CVERecord?id=CVE-2024-39497 Référence CVE CVE-2024-39498 https://www.cve.org/CVERecord?id=CVE-2024-39498 Référence CVE CVE-2024-39499 https://www.cve.org/CVERecord?id=CVE-2024-39499 Référence CVE CVE-2024-39500 https://www.cve.org/CVERecord?id=CVE-2024-39500 Référence CVE CVE-2024-39501 https://www.cve.org/CVERecord?id=CVE-2024-39501 Référence CVE CVE-2024-39502 https://www.cve.org/CVERecord?id=CVE-2024-39502 Référence CVE CVE-2024-39504 https://www.cve.org/CVERecord?id=CVE-2024-39504 Référence CVE CVE-2024-39505 https://www.cve.org/CVERecord?id=CVE-2024-39505 Référence CVE CVE-2024-39506 https://www.cve.org/CVERecord?id=CVE-2024-39506 Référence CVE CVE-2024-39507 https://www.cve.org/CVERecord?id=CVE-2024-39507 Référence CVE CVE-2024-39508 https://www.cve.org/CVERecord?id=CVE-2024-39508 Référence CVE CVE-2024-39509 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-39487 Référence CVE CVE-2024-39488 https://www.cve.org/CVERecord?id=CVE-2024-39488 Référence CVE CVE-2024-39490 https://www.cve.org/CVERecord?id=CVE-2024-39490 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-39494 https://www.cve.org/CVERecord?id=CVE-2024-39494 Référence CVE CVE-2024-39496 https://www.cve.org/CVERecord?id=CVE-2024-39496 Référence CVE CVE-2024-39497 https://www.cve.org/CVERecord?id=CVE-2024-39497 Référence CVE CVE-2024-39498 https://www.cve.org/CVERecord?id=CVE-2024-39498 Référence CVE CVE-2024-39499 https://www.cve.org/CVERecord?id=CVE-2024-39499 Référence CVE CVE-2024-39500 https://www.cve.org/CVERecord?id=CVE-2024-39500 Référence CVE CVE-2024-39501 https://www.cve.org/CVERecord?id=CVE-2024-39501 Référence CVE CVE-2024-39502 https://www.cve.org/CVERecord?id=CVE-2024-39502 Référence CVE CVE-2024-39504 https://www.cve.org/CVERecord?id=CVE-2024-39504 Référence CVE CVE-2024-39505 https://www.cve.org/CVERecord?id=CVE-2024-39505 Référence CVE CVE-2024-39506 https://www.cve.org/CVERecord?id=CVE-2024-39506 Référence CVE CVE-2024-39507 https://www.cve.org/CVERecord?id=CVE-2024-39507 Référence CVE CVE-2024-39508 https://www.cve.org/CVERecord?id=CVE-2024-39508 Référence CVE CVE-2024-39509 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-39484 Référence CVE CVE-2024-39487 https://www.cve.org/CVERecord?id=CVE-2024-39487 Référence CVE CVE-2024-39488 https://www.cve.org/CVERecord?id=CVE-2024-39488 Référence CVE CVE-2024-39489 https://www.cve.org/CVERecord?id=CVE-2024-39489 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-39494 https://www.cve.org/CVERecord?id=CVE-2024-39494 Référence CVE CVE-2024-39495 https://www.cve.org/CVERecord?id=CVE-2024-39495 Référence CVE CVE-2024-39496 https://www.cve.org/CVERecord?id=CVE-2024-39496 Référence CVE CVE-2024-39499 https://www.cve.org/CVERecord?id=CVE-2024-39499 Référence CVE CVE-2024-39500 https://www.cve.org/CVERecord?id=CVE-2024-39500 Référence CVE CVE-2024-39501 https://www.cve.org/CVERecord?id=CVE-2024-39501 Référence CVE CVE-2024-39502 https://www.cve.org/CVERecord?id=CVE-2024-39502 Référence CVE CVE-2024-39503 https://www.cve.org/CVERecord?id=CVE-2024-39503 Référence CVE CVE-2024-39505 https://www.cve.org/CVERecord?id=CVE-2024-39505 Référence CVE CVE-2024-39506 https://www.cve.org/CVERecord?id=CVE-2024-39506 Référence CVE CVE-2024-39507 https://www.cve.org/CVERecord?id=CVE-2024-39507 Référence CVE CVE-2024-39509 https://www.cve.org/CVERecord?id=CVE-2024-39509 Référence CVE CVE-2024-39510 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-027936Linux の 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
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 12 Jul 2024 · Last source change 5 Aug 2026, 11:33 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-38026
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
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.

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-38026↗Vendor CSAF · Red Hat Product Security↗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.
Free version - for non-commercial use only.CVE-2024-39500 · cve.blacktree.nl