BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-44935High confidence

sctp: Fix null-ptr-deref in reuseport_add_sock().

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

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

15 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 releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

3 current
SSA-265688 · CSAF 2.0 · revision 13 · interimSiemens ProductCERTSSA-265688: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP V1.1
1 known affected

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

  • SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
Summary
sctp: Fix null-ptr-deref in reuseport_add_sock(). A Null Pointer Dereference in reuseport_add_sock() while accessing sk2->sk_reuseport_cb . The repro first creates a listener with SO_REUSEPORT. Then, it creates another listener on the same port and concurrently closes the first listener. The second listen() calls reuseport_add_sock() with the first listener as sk2, where sk2->sk_reuseport_cb is not expected to be cleared concurrently, but the close() does clear it by reuseport_detach_sock().
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-355557 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-355557: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.2
3 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
sctp: Fix null-ptr-deref in reuseport_add_sock(). A Null Pointer Dereference in reuseport_add_sock() while accessing sk2->sk_reuseport_cb . The repro first creates a listener with SO_REUSEPORT. Then, it creates another listener on the same port and concurrently closes the first listener. The second listen() calls reuseport_add_sock() with the first listener as sk2, where sk2->sk_reuseport_cb is not expected to be cleared concurrently, but the close() does clear it by reuseport_detach_sock().
Remediation
No remediation text is recorded.
SSA-613116 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-613116: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.1
2 known affected

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

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
sctp: Fix null-ptr-deref in reuseport_add_sock(). A Null Pointer Dereference in reuseport_add_sock() while accessing sk2->sk_reuseport_cb . The repro first creates a listener with SO_REUSEPORT. Then, it creates another listener on the same port and concurrently closes the first listener. The second listen() calls reuseport_add_sock() with the first listener as sk2, where sk2->sk_reuseport_cb is not expected to be cleared concurrently, but the close() does clear it by reuseport_detach_sock().
Remediation
Update to V3.1 or later version
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: sctp: Fix null-ptr-deref in reuseport_add_sock(). syzbot reported a null-ptr-deref while accessing sk2->sk_reuseport_cb in reuseport_add_sock(). [0] The repro first creates a listener with SO_REUSEPORT. Then, it creates another listener on the same port and concurrently closes the first listener. The second listen() calls reuseport_add_sock() with the first listener as sk2, where sk2->sk_reuseport_cb is not expected to be cleared concurrently, but the close() does clear it by reuseport_detach_sock(). The problem is SCTP does not properly synchronise reuseport_alloc(), reuseport_add_sock(), and reuseport_detach_sock(). The caller of reuseport_alloc() and reuseport_{add,detach}_sock() must provide synchronisation for sockets that are classified into the same reuseport group. Otherwise, such sockets form multiple identical reuseport groups, and all groups except one would be silently dead. 1. Two sockets call listen() concurrently 2. No socket in the same group found in sctp_ep_hashtable[] 3. Two sockets call reuseport_alloc() and form two reuseport groups 4. Only one group hit first in __sctp_rcv_lookup_endpoint() receives incoming packets Also, the reported null-ptr-deref could occur. TCP/UDP guarantees that would not happen by holding the hash bucket lock. Let's apply the locking strategy to __sctp_hash_endpoint() and __sctp_unhash_endpoint(). [0]: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] CPU: 1 UID: 0 PID: 10230 Comm: syz-executor119 Not tainted 6.10.0-syzkaller-12585-g301927d2d2eb #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 RIP: 0010:reuseport_add_sock+0x27e/0x5e0 net/core/sock_reuseport.c:350 Code: 00 0f b7 5d 00 bf 01 00 00 00 89 de e8 1b a4 ff f7 83 fb 01 0f 85 a3 01 00 00 e8 6d a0 ff f7 49 8d 7e 12 48 89 f8 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 4b 02 00 00 41 0f b7 5e 12 49 8d 7e 14 RSP: 0018:ffffc9000b947c98 EFLAGS: 00010202 RAX: 0000000000000002 RBX: ffff8880252ddf98 RCX: ffff888079478000 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000012 RBP: 0000000000000001 R08: ffffffff8993e18d R09: 1ffffffff1fef385 R10: dffffc0000000000 R11: fffffbfff1fef386 R12: ffff8880252ddac0 R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f24e45b96c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffcced5f7b8 CR3: 00000000241be000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> __sctp_hash_endpoint net/sctp/input.c:762 [inline] sctp_hash_endpoint+0x52a/0x600 net/sctp/input.c:790 sctp_listen_start net/sctp/socket.c:8570 [inline] sctp_inet_listen+0x767/0xa20 net/sctp/socket.c:8625 __sys_listen_socket net/socket.c:1883 [inline] __sys_listen+0x1b7/0x230 net/socket.c:1894 __do_sys_listen net/socket.c:1902 [inline] __se_sys_listen net/socket.c:1900 [inline] __x64_sys_listen+0x5a/0x70 net/socket.c:1900 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f24e46039b9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 91 1a 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f24e45b9228 EFLAGS: 00000246 ORIG_RAX: 0000000000000032 RAX: ffffffffffffffda RBX: 00007f24e468e428 RCX: 00007f24e46039b9 RDX: 00007f24e46039b9 RSI: 0000000000000003 RDI: 0000000000000004 RBP: 00007f24e468e420 R08: 00007f24e45b96c0 R09: 00007f24e45b96c0 R10: 00007f24e45b96c0 R11: 0000000000000246 R12: 00007f24e468e42c R13: ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: sctp: Fix null-ptr-deref in reuseport_add_sock(). syzbot reported a null-ptr-deref while accessing sk2->sk_reuseport_cb in reuseport_add_sock(). [0] The repro first creates a listener with SO_REUSEPORT. Then, it creates another listener on the same port and concurrently closes the first listener. The second listen() calls reuseport_add_sock() with the first listener as sk2, where sk2->sk_reuseport_cb is not expected to be cleared concurrently, but the close() does clear it by reuseport_detach_sock(). The problem is SCTP does not properly synchronise reuseport_alloc(), reuseport_add_sock(), and reuseport_detach_sock(). The caller of reuseport_alloc() and reuseport_{add,detach}_sock() must provide synchronisation for sockets that are classified into the same reuseport group. Otherwise, such sockets form multiple identical reuseport groups, and all groups except one would be silently dead. 1. Two sockets call listen() concurrently 2. No socket in the same group found in sctp_ep_hashtable[] 3. Two sockets call reuseport_alloc() and form two reuseport groups 4. Only one group hit first in __sctp_rcv_lookup_endpoint() receives incoming packets Also, the reported null-ptr-deref could occur. TCP/UDP guarantees that would not happen by holding the hash bucket lock. Let's apply the locking strategy to __sctp_hash_endpoint() and __sctp_unhash_endpoint(). [0]: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] CPU: 1 UID: 0 PID: 10230 Comm: syz-executor119 Not tainted 6.10.0-syzkaller-12585-g301927d2d2eb #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 RIP: 0010:reuseport_add_sock+0x27e/0x5e0 net/core/sock_reuseport.c:350 Code: 00 0f b7 5d 00 bf 01 00 00 00 89 de e8 1b a4 ff f7 83 fb 01 0f 85 a3 01 00 00 e8 6d a0 ff f7 49 8d 7e 12 48 89 f8 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 4b 02 00 00 41 0f b7 5e 12 49 8d 7e 14 RSP: 0018:ffffc9000b947c98 EFLAGS: 00010202 RAX: 0000000000000002 RBX: ffff8880252ddf98 RCX: ffff888079478000 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000012 RBP: 0000000000000001 R08: ffffffff8993e18d R09: 1ffffffff1fef385 R10: dffffc0000000000 R11: fffffbfff1fef386 R12: ffff8880252ddac0 R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f24e45b96c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffcced5f7b8 CR3: 00000000241be000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> __sctp_hash_endpoint net/sctp/input.c:762 [inline] sctp_hash_endpoint+0x52a/0x600 net/sctp/input.c:790 sctp_listen_start net/sctp/socket.c:8570 [inline] sctp_inet_listen+0x767/0xa20 net/sctp/socket.c:8625 __sys_listen_socket net/socket.c:1883 [inline] __sys_listen+0x1b7/0x230 net/socket.c:1894 __do_sys_listen net/socket.c:1902 [inline] __se_sys_listen net/socket.c:1900 [inline] __x64_sys_listen+0x5a/0x70 net/socket.c:1900 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f24e46039b9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 91 1a 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f24e45b9228 EFLAGS: 00000246 ORIG_RAX: 0000000000000032 RAX: ffffffffffffffda RBX: 00007f24e468e428 RCX: 00007f24e46039b9 RDX: 00007f24e46039b9 RSI: 0000000000000003 RDI: 0000000000000004 RBP: 00007f24e468e420 R08: 00007f24e45b96c0 R09: 00007f24e45b96c0 R10: 00007f24e45b96c0 R11: 0000000000000246 R12: 00007f24e468e42c R13: ---truncated---

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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: sctp: Fix null-ptr-deref in reuseport_add_sock(). syzbot reported a null-ptr-deref while accessing sk2->sk_reuseport_cb in reuseport_add_sock(). [0] The repro first creates a listener with SO_REUSEPORT. Then, it creates another listener on the same port and concurrently closes the first listener. The second listen() calls reuseport_add_sock() with the first listener as sk2, where sk2->sk_reuseport_cb is not expected to be cleared concurrently, but the close() does clear it by reuseport_detach_sock(). The problem is SCTP does not properly synchronise reuseport_alloc(), reuseport_add_sock(), and reuseport_detach_sock(). The caller of reuseport_alloc() and reuseport_{add,detach}_sock() must provide synchronisation for sockets that are classified into the same reuseport group. Otherwise, such sockets form multiple identical reuseport groups, and all groups except one would be silently dead. 1. Two sockets call listen() concurrently 2. No socket in the same group found in sctp_ep_hashtable[] 3. Two sockets call reuseport_alloc() and form two reuseport groups 4. Only one group hit first in __sctp_rcv_lookup_endpoint() receives incoming packets Also, the reported null-ptr-deref could occur. TCP/UDP guarantees that would not happen by holding the hash bucket lock. Let's apply the locking strategy to __sctp_hash_endpoint() and __sctp_unhash_endpoint(). [0]: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] CPU: 1 UID: 0 PID: 10230 Comm: syz-executor119 Not tainted 6.10.0-syzkaller-12585-g301927d2d2eb #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 RIP: 0010:reuseport_add_sock+0x27e/0x5e0 net/core/sock_reuseport.c:350 Code: 00 0f b7 5d 00 bf 01 00 00 00 89 de e8 1b a4 ff f7 83 fb 01 0f 85 a3 01 00 00 e8 6d a0 ff f7 49 8d 7e 12 48 89 f8 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 4b 02 00 00 41 0f b7 5e 12 49 8d 7e 14 RSP: 0018:ffffc9000b947c98 EFLAGS: 00010202 RAX: 0000000000000002 RBX: ffff8880252ddf98 RCX: ffff888079478000 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000012 RBP: 0000000000000001 R08: ffffffff8993e18d R09: 1ffffffff1fef385 R10: dffffc0000000000 R11: fffffbfff1fef386 R12: ffff8880252ddac0 R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f24e45b96c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffcced5f7b8 CR3: 00000000241be000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> __sctp_hash_endpoint net/sctp/input.c:762 [inline] sctp_hash_endpoint+0x52a/0x600 net/sctp/input.c:790 sctp_listen_start net/sctp/socket.c:8570 [inline] sctp_inet_listen+0x767/0xa20 net/sctp/socket.c:8625 __sys_listen_socket net/socket.c:1883 [inline] __sys_listen+0x1b7/0x230 net/socket.c:1894 __do_sys_listen net/socket.c:1902 [inline] __se_sys_listen net/socket.c:1900 [inline] __x64_sys_listen+0x5a/0x70 net/socket.c:1900 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f24e46039b9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 91 1a 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f24e45b9228 EFLAGS: 00000246 ORIG_RAX: 0000000000000032 RAX: ffffffffffffffda RBX: 00007f24e468e428 RCX: 00007f24e46039b9 RDX: 00007f24e46039b9 RSI: 0000000000000003 RDI: 0000000000000004 RBP: 00007f24e468e420 R08: 00007f24e45b96c0 R09: 00007f24e45b96c0 R10: 00007f24e45b96c0 R11: 0000000000000246 R12: 00007f24e468e42c R13: ---truncated---

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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 → NULL Pointer Dereference → 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-476

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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

Official authority intelligence

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

BSI · German · WID-SEC-W-2024-1925Linux Kernel: Mehrere Schwachstellen

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

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0677Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2024-43882 Référence CVE CVE-2024-43883 https://www.cve.org/CVERecord?id=CVE-2024-43883 Référence CVE CVE-2024-43889 https://www.cve.org/CVERecord?id=CVE-2024-43889 Référence CVE CVE-2024-43890 https://www.cve.org/CVERecord?id=CVE-2024-43890 Référence CVE CVE-2024-43893 https://www.cve.org/CVERecord?id=CVE-2024-43893 Référence CVE CVE-2024-43894 https://www.cve.org/CVERecord?id=CVE-2024-43894 Référence CVE CVE-2024-43907 https://www.cve.org/CVERecord?id=CVE-2024-43907 Référence CVE CVE-2024-43908 https://www.cve.org/CVERecord?id=CVE-2024-43908 Référence CVE CVE-2024-43914 https://www.cve.org/CVERecord?id=CVE-2024-43914 Référence CVE CVE-2024-44935 https://www.cve.org/CVERecord?id=CVE-2024-44935 Référence CVE CVE-2024-44944 https://www.cve.org/CVERecord?id=CVE-2024-44944 Référence CVE CVE-2024-44949 https://www.cve.org/CVERecord?id=CVE-2024-44949 Référence CVE CVE-2024-44952 https://www.cve.org/CVERecord?id=CVE-2024-44952 Référence CVE CVE-2024-44954 https://www.cve.org/CVERecord?id=CVE-2024-44954 Référence CVE CVE-2024-44960 https://www.cve.org/CVERecord?id=CVE-2024-44960 Référence CVE CVE-2024-44965 https://www.cve.org/CVERecord?id=CVE-2024-44965 Référence CVE CVE-2024-44969 https://www.cve.org/CVERecord?id=CVE-2024-44969 Référence CVE CVE-2024-44971 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0401Multiples vulnérabilités dans Juniper Networks Secure Analytics

ord?id=CVE-2024-42244 Référence CVE CVE-2024-42284 https://www.cve.org/CVERecord?id=CVE-2024-42284 Référence CVE CVE-2024-42292 https://www.cve.org/CVERecord?id=CVE-2024-42292 Référence CVE CVE-2024-42301 https://www.cve.org/CVERecord?id=CVE-2024-42301 Référence CVE CVE-2024-4317 https://www.cve.org/CVERecord?id=CVE-2024-4317 Référence CVE CVE-2024-43854 https://www.cve.org/CVERecord?id=CVE-2024-43854 Référence CVE CVE-2024-43880 https://www.cve.org/CVERecord?id=CVE-2024-43880 Référence CVE CVE-2024-43889 https://www.cve.org/CVERecord?id=CVE-2024-43889 Référence CVE CVE-2024-43892 https://www.cve.org/CVERecord?id=CVE-2024-43892 Référence CVE CVE-2024-44935 https://www.cve.org/CVERecord?id=CVE-2024-44935 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45769 https://www.cve.org/CVERecord?id=CVE-2024-45769 Référence CVE CVE-2024-45770 https://www.cve.org/CVERecord?id=CVE-2024-45770 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=CVE-2024-46826 Référence CVE CVE-2024-47668 https://www.cve.org/CVERecord?id=CVE-2024-47668 Référence CVE CVE-2024-50302 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0106Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2024-42284 Référence CVE CVE-2024-42292 https://www.cve.org/CVERecord?id=CVE-2024-42292 Référence CVE CVE-2024-42301 https://www.cve.org/CVERecord?id=CVE-2024-42301 Référence CVE CVE-2024-4317 https://www.cve.org/CVERecord?id=CVE-2024-4317 Référence CVE CVE-2024-43788 https://www.cve.org/CVERecord?id=CVE-2024-43788 Référence CVE CVE-2024-43854 https://www.cve.org/CVERecord?id=CVE-2024-43854 Référence CVE CVE-2024-43880 https://www.cve.org/CVERecord?id=CVE-2024-43880 Référence CVE CVE-2024-43889 https://www.cve.org/CVERecord?id=CVE-2024-43889 Référence CVE CVE-2024-43892 https://www.cve.org/CVERecord?id=CVE-2024-43892 Référence CVE CVE-2024-44935 https://www.cve.org/CVERecord?id=CVE-2024-44935 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45020 https://www.cve.org/CVERecord?id=CVE-2024-45020 Référence CVE CVE-2024-45769 https://www.cve.org/CVERecord?id=CVE-2024-45769 Référence CVE CVE-2024-45770 https://www.cve.org/CVERecord?id=CVE-2024-45770 Référence CVE CVE-2024-46820 https://www.cve.org/CVERecord?id=CVE-2024-46820 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-43908 Référence CVE CVE-2024-43909 https://www.cve.org/CVERecord?id=CVE-2024-43909 Référence CVE CVE-2024-43910 https://www.cve.org/CVERecord?id=CVE-2024-43910 Référence CVE CVE-2024-43911 https://www.cve.org/CVERecord?id=CVE-2024-43911 Référence CVE CVE-2024-43912 https://www.cve.org/CVERecord?id=CVE-2024-43912 Référence CVE CVE-2024-43913 https://www.cve.org/CVERecord?id=CVE-2024-43913 Référence CVE CVE-2024-43914 https://www.cve.org/CVERecord?id=CVE-2024-43914 Référence CVE CVE-2024-44931 https://www.cve.org/CVERecord?id=CVE-2024-44931 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44935 https://www.cve.org/CVERecord?id=CVE-2024-44935 Référence CVE CVE-2024-44937 https://www.cve.org/CVERecord?id=CVE-2024-44937 Référence CVE CVE-2024-44938 https://www.cve.org/CVERecord?id=CVE-2024-44938 Référence CVE CVE-2024-44939 https://www.cve.org/CVERecord?id=CVE-2024-44939 Référence CVE CVE-2024-44940 https://www.cve.org/CVERecord?id=CVE-2024-44940 Référence CVE CVE-2024-44941 https://www.cve.org/CVERecord?id=CVE-2024-44941 Référence CVE CVE-2024-44942 https://www.cve.org/CVERecord?id=CVE-2024-44942 Référence CVE CVE-2024-44943 https://www.cve.org/CVERecord?id=CVE-2024-44943 Référence CVE CVE-2024-44944 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-43905 Référence CVE CVE-2024-43907 https://www.cve.org/CVERecord?id=CVE-2024-43907 Référence CVE CVE-2024-43908 https://www.cve.org/CVERecord?id=CVE-2024-43908 Référence CVE CVE-2024-43909 https://www.cve.org/CVERecord?id=CVE-2024-43909 Référence CVE CVE-2024-43911 https://www.cve.org/CVERecord?id=CVE-2024-43911 Référence CVE CVE-2024-43912 https://www.cve.org/CVERecord?id=CVE-2024-43912 Référence CVE CVE-2024-43914 https://www.cve.org/CVERecord?id=CVE-2024-43914 Référence CVE CVE-2024-44931 https://www.cve.org/CVERecord?id=CVE-2024-44931 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44935 https://www.cve.org/CVERecord?id=CVE-2024-44935 Référence CVE CVE-2024-44938 https://www.cve.org/CVERecord?id=CVE-2024-44938 Référence CVE CVE-2024-44939 https://www.cve.org/CVERecord?id=CVE-2024-44939 Référence CVE CVE-2024-44940 https://www.cve.org/CVERecord?id=CVE-2024-44940 Référence CVE CVE-2024-44944 https://www.cve.org/CVERecord?id=CVE-2024-44944 Référence CVE CVE-2024-44946 https://www.cve.org/CVERecord?id=CVE-2024-44946 Référence CVE CVE-2024-44947 https://www.cve.org/CVERecord?id=CVE-2024-44947 Référence CVE CVE-2024-44948 https://www.cve.org/CVERecord?id=CVE-2024-44948 Référence CVE CVE-2024-44949 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-43908 Référence CVE CVE-2024-43909 https://www.cve.org/CVERecord?id=CVE-2024-43909 Référence CVE CVE-2024-43910 https://www.cve.org/CVERecord?id=CVE-2024-43910 Référence CVE CVE-2024-43911 https://www.cve.org/CVERecord?id=CVE-2024-43911 Référence CVE CVE-2024-43912 https://www.cve.org/CVERecord?id=CVE-2024-43912 Référence CVE CVE-2024-43913 https://www.cve.org/CVERecord?id=CVE-2024-43913 Référence CVE CVE-2024-43914 https://www.cve.org/CVERecord?id=CVE-2024-43914 Référence CVE CVE-2024-44931 https://www.cve.org/CVERecord?id=CVE-2024-44931 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44935 https://www.cve.org/CVERecord?id=CVE-2024-44935 Référence CVE CVE-2024-44937 https://www.cve.org/CVERecord?id=CVE-2024-44937 Référence CVE CVE-2024-44938 https://www.cve.org/CVERecord?id=CVE-2024-44938 Référence CVE CVE-2024-44939 https://www.cve.org/CVERecord?id=CVE-2024-44939 Référence CVE CVE-2024-44940 https://www.cve.org/CVERecord?id=CVE-2024-44940 Référence CVE CVE-2024-44941 https://www.cve.org/CVERecord?id=CVE-2024-44941 Référence CVE CVE-2024-44942 https://www.cve.org/CVERecord?id=CVE-2024-44942 Référence CVE CVE-2024-44943 https://www.cve.org/CVERecord?id=CVE-2024-44943 Référence CVE CVE-2024-44944 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-43893 Référence CVE CVE-2024-43894 https://www.cve.org/CVERecord?id=CVE-2024-43894 Référence CVE CVE-2024-43902 https://www.cve.org/CVERecord?id=CVE-2024-43902 Référence CVE CVE-2024-43905 https://www.cve.org/CVERecord?id=CVE-2024-43905 Référence CVE CVE-2024-43907 https://www.cve.org/CVERecord?id=CVE-2024-43907 Référence CVE CVE-2024-43908 https://www.cve.org/CVERecord?id=CVE-2024-43908 Référence CVE CVE-2024-43909 https://www.cve.org/CVERecord?id=CVE-2024-43909 Référence CVE CVE-2024-43914 https://www.cve.org/CVERecord?id=CVE-2024-43914 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44935 https://www.cve.org/CVERecord?id=CVE-2024-44935 Référence CVE CVE-2024-44942 https://www.cve.org/CVERecord?id=CVE-2024-44942 Référence CVE CVE-2024-44944 https://www.cve.org/CVERecord?id=CVE-2024-44944 Référence CVE CVE-2024-44946 https://www.cve.org/CVERecord?id=CVE-2024-44946 Référence CVE CVE-2024-44947 https://www.cve.org/CVERecord?id=CVE-2024-44947 Référence CVE CVE-2024-44948 https://www.cve.org/CVERecord?id=CVE-2024-44948 Référence CVE CVE-2024-44954 https://www.cve.org/CVERecord?id=CVE-2024-44954 Référence CVE CVE-2024-44958 https://www.cve.org/CVERecord?id=CVE-2024-44958 Référence CVE CVE-2024-44960 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-43893 Référence CVE CVE-2024-43894 https://www.cve.org/CVERecord?id=CVE-2024-43894 Référence CVE CVE-2024-43902 https://www.cve.org/CVERecord?id=CVE-2024-43902 Référence CVE CVE-2024-43905 https://www.cve.org/CVERecord?id=CVE-2024-43905 Référence CVE CVE-2024-43907 https://www.cve.org/CVERecord?id=CVE-2024-43907 Référence CVE CVE-2024-43908 https://www.cve.org/CVERecord?id=CVE-2024-43908 Référence CVE CVE-2024-43909 https://www.cve.org/CVERecord?id=CVE-2024-43909 Référence CVE CVE-2024-43914 https://www.cve.org/CVERecord?id=CVE-2024-43914 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44935 https://www.cve.org/CVERecord?id=CVE-2024-44935 Référence CVE CVE-2024-44940 https://www.cve.org/CVERecord?id=CVE-2024-44940 Référence CVE CVE-2024-44944 https://www.cve.org/CVERecord?id=CVE-2024-44944 Référence CVE CVE-2024-44946 https://www.cve.org/CVERecord?id=CVE-2024-44946 Référence CVE CVE-2024-44947 https://www.cve.org/CVERecord?id=CVE-2024-44947 Référence CVE CVE-2024-44948 https://www.cve.org/CVERecord?id=CVE-2024-44948 Référence CVE CVE-2024-44952 https://www.cve.org/CVERecord?id=CVE-2024-44952 Référence CVE CVE-2024-44954 https://www.cve.org/CVERecord?id=CVE-2024-44954 Référence CVE CVE-2024-44958 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-43880 Référence CVE CVE-2024-43882 https://www.cve.org/CVERecord?id=CVE-2024-43882 Référence CVE CVE-2024-43883 https://www.cve.org/CVERecord?id=CVE-2024-43883 Référence CVE CVE-2024-43884 https://www.cve.org/CVERecord?id=CVE-2024-43884 Référence CVE CVE-2024-43890 https://www.cve.org/CVERecord?id=CVE-2024-43890 Référence CVE CVE-2024-43893 https://www.cve.org/CVERecord?id=CVE-2024-43893 Référence CVE CVE-2024-43894 https://www.cve.org/CVERecord?id=CVE-2024-43894 Référence CVE CVE-2024-43908 https://www.cve.org/CVERecord?id=CVE-2024-43908 Référence CVE CVE-2024-43914 https://www.cve.org/CVERecord?id=CVE-2024-43914 Référence CVE CVE-2024-44935 https://www.cve.org/CVERecord?id=CVE-2024-44935 Référence CVE CVE-2024-44944 https://www.cve.org/CVERecord?id=CVE-2024-44944 Référence CVE CVE-2024-44946 https://www.cve.org/CVERecord?id=CVE-2024-44946 Référence CVE CVE-2024-44947 https://www.cve.org/CVERecord?id=CVE-2024-44947 Référence CVE CVE-2024-44948 https://www.cve.org/CVERecord?id=CVE-2024-44948 Référence CVE CVE-2024-44952 https://www.cve.org/CVERecord?id=CVE-2024-44952 Référence CVE CVE-2024-44954 https://www.cve.org/CVERecord?id=CVE-2024-44954 Référence CVE CVE-2024-44960 https://www.cve.org/CVERecord?id=CVE-2024-44960 Référence CVE CVE-2024-44965 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-42079 Référence CVE CVE-2024-42244 https://www.cve.org/CVERecord?id=CVE-2024-42244 Référence CVE CVE-2024-42284 https://www.cve.org/CVERecord?id=CVE-2024-42284 Référence CVE CVE-2024-42292 https://www.cve.org/CVERecord?id=CVE-2024-42292 Référence CVE CVE-2024-42301 https://www.cve.org/CVERecord?id=CVE-2024-42301 Référence CVE CVE-2024-43854 https://www.cve.org/CVERecord?id=CVE-2024-43854 Référence CVE CVE-2024-43880 https://www.cve.org/CVERecord?id=CVE-2024-43880 Référence CVE CVE-2024-43889 https://www.cve.org/CVERecord?id=CVE-2024-43889 Référence CVE CVE-2024-43892 https://www.cve.org/CVERecord?id=CVE-2024-43892 Référence CVE CVE-2024-44935 https://www.cve.org/CVERecord?id=CVE-2024-44935 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=CVE-2024-46826 Référence CVE CVE-2024-47668 https://www.cve.org/CVERecord?id=CVE-2024-47668 Gestion détaillée du document le 08 novembre 2024 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.go

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

d?id=CVE-2024-43889 Référence CVE CVE-2024-43890 https://www.cve.org/CVERecord?id=CVE-2024-43890 Référence CVE CVE-2024-43892 https://www.cve.org/CVERecord?id=CVE-2024-43892 Référence CVE CVE-2024-43893 https://www.cve.org/CVERecord?id=CVE-2024-43893 Référence CVE CVE-2024-43894 https://www.cve.org/CVERecord?id=CVE-2024-43894 Référence CVE CVE-2024-43905 https://www.cve.org/CVERecord?id=CVE-2024-43905 Référence CVE CVE-2024-43907 https://www.cve.org/CVERecord?id=CVE-2024-43907 Référence CVE CVE-2024-43908 https://www.cve.org/CVERecord?id=CVE-2024-43908 Référence CVE CVE-2024-43914 https://www.cve.org/CVERecord?id=CVE-2024-43914 Référence CVE CVE-2024-44935 https://www.cve.org/CVERecord?id=CVE-2024-44935 Référence CVE CVE-2024-44944 https://www.cve.org/CVERecord?id=CVE-2024-44944 Référence CVE CVE-2024-44946 https://www.cve.org/CVERecord?id=CVE-2024-44946 Référence CVE CVE-2024-44947 https://www.cve.org/CVERecord?id=CVE-2024-44947 Référence CVE CVE-2024-44948 https://www.cve.org/CVERecord?id=CVE-2024-44948 Référence CVE CVE-2024-44952 https://www.cve.org/CVERecord?id=CVE-2024-44952 Référence CVE CVE-2024-44954 https://www.cve.org/CVERecord?id=CVE-2024-44954 Référence CVE CVE-2024-44960 https://www.cve.org/CVERecord?id=CVE-2024-44960 Référence CVE CVE-2024-44965 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-43845 Référence CVE CVE-2024-43870 https://www.cve.org/CVERecord?id=CVE-2024-43870 Référence CVE CVE-2024-43884 https://www.cve.org/CVERecord?id=CVE-2024-43884 Référence CVE CVE-2024-43886 https://www.cve.org/CVERecord?id=CVE-2024-43886 Référence CVE CVE-2024-43890 https://www.cve.org/CVERecord?id=CVE-2024-43890 Référence CVE CVE-2024-43898 https://www.cve.org/CVERecord?id=CVE-2024-43898 Référence CVE CVE-2024-43904 https://www.cve.org/CVERecord?id=CVE-2024-43904 Référence CVE CVE-2024-43912 https://www.cve.org/CVERecord?id=CVE-2024-43912 Référence CVE CVE-2024-43914 https://www.cve.org/CVERecord?id=CVE-2024-43914 Référence CVE CVE-2024-44935 https://www.cve.org/CVERecord?id=CVE-2024-44935 Référence CVE CVE-2024-44944 https://www.cve.org/CVERecord?id=CVE-2024-44944 Référence CVE CVE-2024-44946 https://www.cve.org/CVERecord?id=CVE-2024-44946 Référence CVE CVE-2024-44947 https://www.cve.org/CVERecord?id=CVE-2024-44947 Référence CVE CVE-2024-44948 https://www.cve.org/CVERecord?id=CVE-2024-44948 Référence CVE CVE-2024-44950 https://www.cve.org/CVERecord?id=CVE-2024-44950 Référence CVE CVE-2024-44951 https://www.cve.org/CVERecord?id=CVE-2024-44951 Référence CVE CVE-2024-44952 https://www.cve.org/CVERecord?id=CVE-2024-44952 Référence CVE CVE-2024-44954 https://www.cve.org/CVERecord?id=

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.
Patch available
Affected
SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
Fixed
< 5.0; 5.4.282 ≤ 5.4.*; 5.10.224 ≤ 5.10.*; 5.15.165 ≤ 5.15.*; 6.1.105 ≤ 6.1.*; 6.6.46 ≤ 6.6.*; 6.10.5 ≤ 6.10.*; 6.11 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 26 Aug 2024 · Last source change 12 May 2026, 11:57 UTC · CWE-476 · NULL Pointer Dereference

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-41147
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
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
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-44935 · cve.blacktree.nl