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

tipc: Fix use-after-free of kernel socket in cleanup_bearer().

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 22 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.24% 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 22 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

23 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 19 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.123-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-1Debian Security Tracker ↗Source updated 5 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-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 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-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 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-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 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-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 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
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 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.

2 current
CVE-2024-56642 · CSAF 2.0 · revision 87 · interimSUSE Product Security TeamCVE-2024-56642
191 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free of kernel socket in cleanup_bearer(). syzkaller reported a use-after-free of UDP kernel socket in cleanup_bearer() without repro. [0][1] When bearer_disable() calls tipc_udp_disable(), cleanup of the UDP kernel socket is deferred by work calling cleanup_bearer(). tipc_exit_net() waits for such works to finish by checking tipc_net(net)->wq_count. However, the work decrements the count too early before releasing the kernel socket, unblocking cleanup_net() and resulting in use-after-free. Let's move the decrement after releasing the socket in cleanup_bearer(). [0]: ref_tracker: net notrefcnt@000000009b3d1faf has 1/1 users at sk_alloc+0x438/0x608 inet_create+0x4c8/0xcb0 __sock_create+0x350/0x6b8 sock_create_kern+0x58/0x78 udp_sock_create4+0x68/0x398 udp_sock_create+0x88/0xc8 tipc_udp_enable+0x5e8/0x848 __tipc_nl_bearer_enable+0x84c/0xed8 tipc_nl_bearer_enable+0x38/0x60 genl_family_rcv_msg_doit+0x170/0x248 genl_rcv_msg+0x400/0x5b0 netlink_rcv_skb+0x1dc/0x398 genl_rcv+0x44/0x68 netlink_unicast+0x678/0x8b0 netlink_sendmsg+0x5e4/0x898 ____sys_sendmsg+0x500/0x830 [1]: BUG: KMSAN: use-after-free in udp_hashslot include/net/udp.h:85 [inline] BUG: KMSAN: use-after-free in udp_lib_unhash+0x3b8/0x930 net/ipv4/udp.c:1979 udp_hashslot include/net/udp.h:85 [inline] udp_lib_unhash+0x3b8/0x930 net/ipv4/udp.c:1979 sk_common_release+0xaf/0x3f0 net/core/sock.c:3820 inet_release+0x1e0/0x260 net/ipv4/af_inet.c:437 inet6_release+0x6f/0xd0 net/ipv6/af_inet6.c:489 __sock_release net/socket.c:658 [inline] sock_release+0xa0/0x210 net/socket.c:686 cleanup_bearer+0x42d/0x4c0 net/tipc/udp_media.c:819 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xcaf/0x1c90 kernel/workqueue.c:3310 worker_thread+0xf6c/0x1510 kernel/workqueue.c:3391 kthread+0x531/0x6b0 kernel/kthread.c:389 ret_from_fork+0x60/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:244 Uninit was created at: slab_free_hook mm/slub.c:2269 [inline] slab_free mm/slub.c:4580 [inline] kmem_cache_free+0x207/0xc40 mm/slub.c:4682 net_free net/core/net_namespace.c:454 [inline] cleanup_net+0x16f2/0x19d0 net/core/net_namespace.c:647 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xcaf/0x1c90 kernel/workqueue.c:3310 worker_thread+0xf6c/0x1510 kernel/workqueue.c:3391 kthread+0x531/0x6b0 kernel/kthread.c:389 ret_from_fork+0x60/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:244 CPU: 0 UID: 0 PID: 54 Comm: kworker/0:2 Not tainted 6.12.0-rc1-00131-gf66ebf37d69c #7 91723d6f74857f70725e1583cba3cf4adc716cfa Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 Workqueue: events cleanup_bearer
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-355557 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-355557: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.2
3 known affected

The vendor explicitly identifies these products as 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
tipc: vulnerability in TIPC (Transparent Inter-Process Communication) involves a use-after-free issue with the UDP kernel socket in cleanup_bearer(), caused by premature reference count decrements, which is resolved by moving the decrement after releasing the socket.
Remediation
Update to V3.2 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.

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

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 22 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: tipc: Fix use-after-free of kernel socket in cleanup_bearer(). syzkaller reported a use-after-free of UDP kernel socket in cleanup_bearer() without repro. [0][1] When bearer_disable() calls tipc_udp_disable(), cleanup of the UDP kernel socket is deferred by work calling cleanup_bearer(). tipc_exit_net() waits for such works to finish by checking tipc_net(net)->wq_count. However, the work decrements the count too early before releasing the kernel socket, unblocking cleanup_net() and resulting in use-after-free. Let's move the decrement after releasing the socket in cleanup_bearer(). [0]: ref_tracker: net notrefcnt@000000009b3d1faf has 1/1 users at sk_alloc+0x438/0x608 inet_create+0x4c8/0xcb0 __sock_create+0x350/0x6b8 sock_create_kern+0x58/0x78 udp_sock_create4+0x68/0x398 udp_sock_create+0x88/0xc8 tipc_udp_enable+0x5e8/0x848 __tipc_nl_bearer_enable+0x84c/0xed8 tipc_nl_bearer_enable+0x38/0x60 genl_family_rcv_msg_doit+0x170/0x248 genl_rcv_msg+0x400/0x5b0 netlink_rcv_skb+0x1dc/0x398 genl_rcv+0x44/0x68 netlink_unicast+0x678/0x8b0 netlink_sendmsg+0x5e4/0x898 ____sys_sendmsg+0x500/0x830 [1]: BUG: KMSAN: use-after-free in udp_hashslot include/net/udp.h:85 [inline] BUG: KMSAN: use-after-free in udp_lib_unhash+0x3b8/0x930 net/ipv4/udp.c:1979 udp_hashslot include/net/udp.h:85 [inline] udp_lib_unhash+0x3b8/0x930 net/ipv4/udp.c:1979 sk_common_release+0xaf/0x3f0 net/core/sock.c:3820 inet_release+0x1e0/0x260 net/ipv4/af_inet.c:437 inet6_release+0x6f/0xd0 net/ipv6/af_inet6.c:489 __sock_release net/socket.c:658 [inline] sock_release+0xa0/0x210 net/socket.c:686 cleanup_bearer+0x42d/0x4c0 net/tipc/udp_media.c:819 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xcaf/0x1c90 kernel/workqueue.c:3310 worker_thread+0xf6c/0x1510 kernel/workqueue.c:3391 kthread+0x531/0x6b0 kernel/kthread.c:389 ret_from_fork+0x60/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:244 Uninit was created at: slab_free_hook mm/slub.c:2269 [inline] slab_free mm/slub.c:4580 [inline] kmem_cache_free+0x207/0xc40 mm/slub.c:4682 net_free net/core/net_namespace.c:454 [inline] cleanup_net+0x16f2/0x19d0 net/core/net_namespace.c:647 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xcaf/0x1c90 kernel/workqueue.c:3310 worker_thread+0xf6c/0x1510 kernel/workqueue.c:3391 kthread+0x531/0x6b0 kernel/kthread.c:389 ret_from_fork+0x60/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:244 CPU: 0 UID: 0 PID: 54 Comm: kworker/0:2 Not tainted 6.12.0-rc1-00131-gf66ebf37d69c #7 91723d6f74857f70725e1583cba3cf4adc716cfa Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 Workqueue: events cleanup_bearer

What

In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free of kernel socket in cleanup_bearer(). syzkaller reported a use-after-free of UDP kernel socket in cleanup_bearer() without repro. [0][1] When bearer_disable() calls tipc_udp_disable(), cleanup of the UDP kernel socket is deferred by work calling cleanup_bearer(). tipc_exit_net() waits for such works to finish by checking tipc_net(net)->wq_count. However, the work decrements the count too early before releasing the kernel socket, unblocking cleanup_net() and resulting in use-after-free. Let's move the decrement after releasing the socket in cleanup_bearer(). [0]: ref_tracker: net notrefcnt@000000009b3d1faf has 1/1 users at sk_alloc+0x438/0x608 inet_create+0x4c8/0xcb0 __sock_create+0x350/0x6b8 sock_create_kern+0x58/0x78 udp_sock_create4+0x68/0x398 udp_sock_create+0x88/0xc8 tipc_udp_enable+0x5e8/0x848 __tipc_nl_bearer_enable+0x84c/0xed8 tipc_nl_bearer_enable+0x38/0x60 genl_family_rcv_msg_doit+0x170/0x248 genl_rcv_msg+0x400/0x5b0 netlink_rcv_skb+0x1dc/0x398 genl_rcv+0x44/0x68 netlink_unicast+0x678/0x8b0 netlink_sendmsg+0x5e4/0x898 ____sys_sendmsg+0x500/0x830 [1]: BUG: KMSAN: use-after-free in udp_hashslot include/net/udp.h:85 [inline] BUG: KMSAN: use-after-free in udp_lib_unhash+0x3b8/0x930 net/ipv4/udp.c:1979 udp_hashslot include/net/udp.h:85 [inline] udp_lib_unhash+0x3b8/0x930 net/ipv4/udp.c:1979 sk_common_release+0xaf/0x3f0 net/core/sock.c:3820 inet_release+0x1e0/0x260 net/ipv4/af_inet.c:437 inet6_release+0x6f/0xd0 net/ipv6/af_inet6.c:489 __sock_release net/socket.c:658 [inline] sock_release+0xa0/0x210 net/socket.c:686 cleanup_bearer+0x42d/0x4c0 net/tipc/udp_media.c:819 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xcaf/0x1c90 kernel/workqueue.c:3310 worker_thread+0xf6c/0x1510 kernel/workqueue.c:3391 kthread+0x531/0x6b0 kernel/kthread.c:389 ret_from_fork+0x60/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:244 Uninit was created at: slab_free_hook mm/slub.c:2269 [inline] slab_free mm/slub.c:4580 [inline] kmem_cache_free+0x207/0xc40 mm/slub.c:4682 net_free net/core/net_namespace.c:454 [inline] cleanup_net+0x16f2/0x19d0 net/core/net_namespace.c:647 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xcaf/0x1c90 kernel/workqueue.c:3310 worker_thread+0xf6c/0x1510 kernel/workqueue.c:3391 kthread+0x531/0x6b0 kernel/kthread.c:389 ret_from_fork+0x60/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:244 CPU: 0 UID: 0 PID: 54 Comm: kworker/0:2 Not tainted 6.12.0-rc1-00131-gf66ebf37d69c #7 91723d6f74857f70725e1583cba3cf4adc716cfa Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 Workqueue: events cleanup_bearer

Why

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

How

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

What

In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free of kernel socket in cleanup_bearer(). syzkaller reported a use-after-free of UDP kernel socket in cleanup_bearer() without repro. [0][1] When bearer_disable() calls tipc_udp_disable(), cleanup of the UDP kernel socket is deferred by work calling cleanup_bearer(). tipc_exit_net() waits for such works to finish by checking tipc_net(net)->wq_count. However, the work decrements the count too early before releasing the kernel socket, unblocking cleanup_net() and resulting in use-after-free. Let's move the decrement after releasing the socket in cleanup_bearer(). [0]: ref_tracker: net notrefcnt@000000009b3d1faf has 1/1 users at sk_alloc+0x438/0x608 inet_create+0x4c8/0xcb0 __sock_create+0x350/0x6b8 sock_create_kern+0x58/0x78 udp_sock_create4+0x68/0x398 udp_sock_create+0x88/0xc8 tipc_udp_enable+0x5e8/0x848 __tipc_nl_bearer_enable+0x84c/0xed8 tipc_nl_bearer_enable+0x38/0x60 genl_family_rcv_msg_doit+0x170/0x248 genl_rcv_msg+0x400/0x5b0 netlink_rcv_skb+0x1dc/0x398 genl_rcv+0x44/0x68 netlink_unicast+0x678/0x8b0 netlink_sendmsg+0x5e4/0x898 ____sys_sendmsg+0x500/0x830 [1]: BUG: KMSAN: use-after-free in udp_hashslot include/net/udp.h:85 [inline] BUG: KMSAN: use-after-free in udp_lib_unhash+0x3b8/0x930 net/ipv4/udp.c:1979 udp_hashslot include/net/udp.h:85 [inline] udp_lib_unhash+0x3b8/0x930 net/ipv4/udp.c:1979 sk_common_release+0xaf/0x3f0 net/core/sock.c:3820 inet_release+0x1e0/0x260 net/ipv4/af_inet.c:437 inet6_release+0x6f/0xd0 net/ipv6/af_inet6.c:489 __sock_release net/socket.c:658 [inline] sock_release+0xa0/0x210 net/socket.c:686 cleanup_bearer+0x42d/0x4c0 net/tipc/udp_media.c:819 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xcaf/0x1c90 kernel/workqueue.c:3310 worker_thread+0xf6c/0x1510 kernel/workqueue.c:3391 kthread+0x531/0x6b0 kernel/kthread.c:389 ret_from_fork+0x60/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:244 Uninit was created at: slab_free_hook mm/slub.c:2269 [inline] slab_free mm/slub.c:4580 [inline] kmem_cache_free+0x207/0xc40 mm/slub.c:4682 net_free net/core/net_namespace.c:454 [inline] cleanup_net+0x16f2/0x19d0 net/core/net_namespace.c:647 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xcaf/0x1c90 kernel/workqueue.c:3310 worker_thread+0xf6c/0x1510 kernel/workqueue.c:3391 kthread+0x531/0x6b0 kernel/kthread.c:389 ret_from_fork+0x60/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:244 CPU: 0 UID: 0 PID: 54 Comm: kworker/0:2 Not tainted 6.12.0-rc1-00131-gf66ebf37d69c #7 91723d6f74857f70725e1583cba3cf4adc716cfa Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 Workqueue: events cleanup_bearer

Why

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

How

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

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
local access → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

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

Official authority intelligence

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

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

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

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

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

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

d?id=CVE-2024-56615 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56659 https://www.cve.org/CVERecord?id=CVE-2024-56659 Référence CVE CVE-2024-56661 https://www.cve.org/CVERecord?id=CVE-2024-56661 Référence CVE CVE-2024-56662 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50272 Référence CVE CVE-2024-52559 https://www.cve.org/CVERecord?id=CVE-2024-52559 Référence CVE CVE-2024-53042 https://www.cve.org/CVERecord?id=CVE-2024-53042 Référence CVE CVE-2024-53124 https://www.cve.org/CVERecord?id=CVE-2024-53124 Référence CVE CVE-2024-53139 https://www.cve.org/CVERecord?id=CVE-2024-53139 Référence CVE CVE-2024-53156 https://www.cve.org/CVERecord?id=CVE-2024-53156 Référence CVE CVE-2024-54683 https://www.cve.org/CVERecord?id=CVE-2024-54683 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56661 https://www.cve.org/CVERecord?id=CVE-2024-56661 Référence CVE CVE-2024-56702 https://www.cve.org/CVERecord?id=CVE-2024-56702 Référence CVE CVE-2024-57924 https://www.cve.org/CVERecord?id=CVE-2024-57924 Référence CVE CVE-2024-57980 https://www.cve.org/CVERecord?id=CVE-2024-57980 Référence CVE CVE-2024-57981 https://www.cve.org/CVERecord?id=CVE-2024-57981 Référence CVE CVE-2024-57998 https://www.cve.org/CVERecord?id=CVE-2024-57998 Référence CVE CVE-2024-58001 https://www.cve.org/CVERecord?id=CVE-2024-58001 Référence CVE CVE-2024-58005 https://www.cve.org/CVERecord?id=

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

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

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

d?id=CVE-2024-56632 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56635 https://www.cve.org/CVERecord?id=CVE-2024-56635 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56638 https://www.cve.org/CVERecord?id=CVE-2024-56638 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56649 https://www.cve.org/CVERecord?id=CVE-2024-56649 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56651 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56632 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56635 https://www.cve.org/CVERecord?id=CVE-2024-56635 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56638 https://www.cve.org/CVERecord?id=CVE-2024-56638 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56649 https://www.cve.org/CVERecord?id=CVE-2024-56649 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56651 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53063 Référence CVE CVE-2024-53124 https://www.cve.org/CVERecord?id=CVE-2024-53124 Référence CVE CVE-2024-53140 https://www.cve.org/CVERecord?id=CVE-2024-53140 Référence CVE CVE-2024-53176 https://www.cve.org/CVERecord?id=CVE-2024-53176 Référence CVE CVE-2024-53178 https://www.cve.org/CVERecord?id=CVE-2024-53178 Référence CVE CVE-2024-53680 https://www.cve.org/CVERecord?id=CVE-2024-53680 Référence CVE CVE-2024-56600 https://www.cve.org/CVERecord?id=CVE-2024-56600 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56651 https://www.cve.org/CVERecord?id=CVE-2024-56651 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=CVE-2024-56770 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57973 https://www.cve.org/CVERecord?id=CVE-2024-57973 Référence CVE CVE-2024-57979 https://www.cve.org/CVERecord?id=CVE-2024-57979 Référence CVE CVE-2024-57996 https://www.cve.org/CVERecord?id=CVE-2024-57996 Référence CVE CVE-2024-58013 https://www.cve.org/CVERecord?id=CVE-2024-58013 Référence CVE CVE-2024-58014 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56627 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56658 https://www.cve.org/CVERecord?id=CVE-2024-56658 Référence CVE CVE-2024-56659 https://www.cve.org/CVERecord?id=CVE-2024-56659 Référence CVE CVE-2024-56662 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53124 Référence CVE CVE-2024-53140 https://www.cve.org/CVERecord?id=CVE-2024-53140 Référence CVE CVE-2024-53163 https://www.cve.org/CVERecord?id=CVE-2024-53163 Référence CVE CVE-2024-53176 https://www.cve.org/CVERecord?id=CVE-2024-53176 Référence CVE CVE-2024-53178 https://www.cve.org/CVERecord?id=CVE-2024-53178 Référence CVE CVE-2024-53680 https://www.cve.org/CVERecord?id=CVE-2024-53680 Référence CVE CVE-2024-54683 https://www.cve.org/CVERecord?id=CVE-2024-54683 Référence CVE CVE-2024-56638 https://www.cve.org/CVERecord?id=CVE-2024-56638 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56651 https://www.cve.org/CVERecord?id=CVE-2024-56651 Référence CVE CVE-2024-56702 https://www.cve.org/CVERecord?id=CVE-2024-56702 Référence CVE CVE-2024-56703 https://www.cve.org/CVERecord?id=CVE-2024-56703 Référence CVE CVE-2024-56718 https://www.cve.org/CVERecord?id=CVE-2024-56718 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2024-56751 https://www.cve.org/CVERecord?id=CVE-2024-56751 Référence CVE CVE-2024-56758 https://www.cve.org/CVERecord?id=CVE-2024-56758 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56627 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56658 https://www.cve.org/CVERecord?id=CVE-2024-56658 Référence CVE CVE-2024-56659 https://www.cve.org/CVERecord?id=CVE-2024-56659 Référence CVE CVE-2024-56662 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56635 https://www.cve.org/CVERecord?id=CVE-2024-56635 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56638 https://www.cve.org/CVERecord?id=CVE-2024-56638 Référence CVE CVE-2024-56639 https://www.cve.org/CVERecord?id=CVE-2024-56639 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56646 https://www.cve.org/CVERecord?id=CVE-2024-56646 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56649 https://www.cve.org/CVERecord?id=CVE-2024-56649 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56601 Référence CVE CVE-2024-56602 https://www.cve.org/CVERecord?id=CVE-2024-56602 Référence CVE CVE-2024-56604 https://www.cve.org/CVERecord?id=CVE-2024-56604 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56658 https://www.cve.org/CVERecord?id=CVE-2024-56658 Référence CVE CVE-2024-56661 https://www.cve.org/CVERecord?id=CVE-2024-56661 Référence CVE CVE-2024-56664 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56628 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56651 https://www.cve.org/CVERecord?id=CVE-2024-56651 Référence CVE CVE-2024-56658 https://www.cve.org/CVERecord?id=CVE-2024-56658 Référence CVE CVE-2024-56659 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56632 https://www.cve.org/CVERecord?id=CVE-2024-56632 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56635 https://www.cve.org/CVERecord?id=CVE-2024-56635 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56649 https://www.cve.org/CVERecord?id=CVE-2024-56649 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56651 https://www.cve.org/CVERecord?id=CVE-2024-56651 Référence CVE CVE-2024-56654 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56632 https://www.cve.org/CVERecord?id=CVE-2024-56632 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56635 https://www.cve.org/CVERecord?id=CVE-2024-56635 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56649 https://www.cve.org/CVERecord?id=CVE-2024-56649 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56651 https://www.cve.org/CVERecord?id=CVE-2024-56651 Référence CVE CVE-2024-56654 https://www.cve.org/CVERecord?id=CVE-2024-56654 Référence CVE CVE-2024-56656 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56629 Référence CVE CVE-2024-56630 https://www.cve.org/CVERecord?id=CVE-2024-56630 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56632 https://www.cve.org/CVERecord?id=CVE-2024-56632 Référence CVE CVE-2024-56634 https://www.cve.org/CVERecord?id=CVE-2024-56634 Référence CVE CVE-2024-56635 https://www.cve.org/CVERecord?id=CVE-2024-56635 Référence CVE CVE-2024-56636 https://www.cve.org/CVERecord?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56649 https://www.cve.org/CVERecord?id=CVE-2024-56649 Référence CVE CVE-2024-56651 https://www.cve.org/CVERecord?id=CVE-2024-56651 Référence CVE CVE-2024-56654 https://www.cve.org/CVERecord?id=CVE-2024-56654 Référence CVE CVE-2024-56656 https://www.cve.org/CVERecord?id=

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

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

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.13, 5.4.287 ≤ 5.4.*, 5.10.231 ≤ 5.10.*, 5.15.174 ≤ 5.15.*, 6.1.120 ≤ 6.1.*, 6.6.66 ≤ 6.6.*, 6.12.5 ≤ 6.12.*, 6.13 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 27 Dec 2024 · Last source change 5 Aug 2026, 11:45 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-53290
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗

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-56642 · cve.blacktree.nl