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

wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 14 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 12 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.28% 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: No default targetRemediation target: Normal maintenance

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

Distribution package intelligence

Release-specific package status

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

17 package states
Package result overrides the generic status

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

Repository candidate not checked

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

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

Authoritative vendor CSAF and VEX advisories

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

3 current
CVE-2024-40942 · CSAF 2.0 · revision 96 · interimSUSE Product Security TeamCVE-2024-40942
271 known affected

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

  • kernel-default as component of SUSE Enterprise Storage 7.1
  • kernel-default-devel as component of SUSE Enterprise Storage 7.1
  • kernel-devel as component of SUSE Enterprise Storage 7.1
  • kernel-macros as component of SUSE Enterprise Storage 7.1
  • kernel-source as component of SUSE Enterprise Storage 7.1
  • reiserfs-kmp-default as component of SUSE Enterprise Storage 7.1
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects The hwmp code use objects of type mesh_preq_queue, added to a list in ieee80211_if_mesh, to keep track of mpath we need to resolve. If the mpath gets deleted, ex mesh interface is removed, the entries in that list will never get cleaned. Fix this by flushing all corresponding items of the preq_queue in mesh_path_flush_pending(). This should take care of KASAN reports like this: unreferenced object 0xffff00000668d800 (size 128): comm "kworker/u8:4", pid 67, jiffies 4295419552 (age 1836.444s) hex dump (first 32 bytes): 00 1f 05 09 00 00 ff ff 00 d5 68 06 00 00 ff ff ..........h..... 8e 97 ea eb 3e b8 01 00 00 00 00 00 00 00 00 00 ....>........... backtrace: [ ] __kmem_cache_alloc_node+0x1e0/0x35c [ ] kmalloc_trace+0x34/0x80 [ ] mesh_queue_preq+0x44/0x2a8 [ ] mesh_nexthop_resolve+0x198/0x19c [ ] ieee80211_xmit+0x1d0/0x1f4 [ ] __ieee80211_subif_start_xmit+0x30c/0x764 [ ] ieee80211_subif_start_xmit+0x9c/0x7a4 [ ] dev_hard_start_xmit+0x174/0x440 [ ] __dev_queue_xmit+0xe24/0x111c [ ] batadv_send_skb_packet+0x180/0x1e4 [ ] batadv_v_elp_periodic_work+0x2f4/0x508 [ ] process_one_work+0x4b8/0xa1c [ ] worker_thread+0x9c/0x634 [ ] kthread+0x1bc/0x1c4 [ ] ret_from_fork+0x10/0x20 unreferenced object 0xffff000009051f00 (size 128): comm "kworker/u8:4", pid 67, jiffies 4295419553 (age 1836.440s) hex dump (first 32 bytes): 90 d6 92 0d 00 00 ff ff 00 d8 68 06 00 00 ff ff ..........h..... 36 27 92 e4 02 e0 01 00 00 58 79 06 00 00 ff ff 6'.......Xy..... backtrace: [ ] __kmem_cache_alloc_node+0x1e0/0x35c [ ] kmalloc_trace+0x34/0x80 [ ] mesh_queue_preq+0x44/0x2a8 [ ] mesh_nexthop_resolve+0x198/0x19c [ ] ieee80211_xmit+0x1d0/0x1f4 [ ] __ieee80211_subif_start_xmit+0x30c/0x764 [ ] ieee80211_subif_start_xmit+0x9c/0x7a4 [ ] dev_hard_start_xmit+0x174/0x440 [ ] __dev_queue_xmit+0xe24/0x111c [ ] batadv_send_skb_packet+0x180/0x1e4 [ ] batadv_v_elp_periodic_work+0x2f4/0x508 [ ] process_one_work+0x4b8/0xa1c [ ] worker_thread+0x9c/0x634 [ ] kthread+0x1bc/0x1c4 [ ] ret_from_fork+0x10/0x20
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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
wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects The hwmp code use objects of type mesh_preq_queue, added to a list in ieee80211_if_mesh, to keep track of mpath we need to resolve. If the mpath gets deleted, ex mesh interface is removed, the entries in that list will never get cleaned.
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
wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects The hwmp code use objects of type mesh_preq_queue, added to a list in ieee80211_if_mesh, to keep track of mpath we need to resolve. If the mpath gets deleted, ex mesh interface is removed, the entries in that list will never get cleaned.
Remediation
No remediation text is recorded.
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-38830

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 14 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: wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects The hwmp code use objects of type mesh_preq_queue, added to a list in ieee80211_if_mesh, to keep track of mpath we need to resolve. If the mpath gets deleted, ex mesh interface is removed, the entries in that list will never get cleaned. Fix this by flushing all corresponding items of the preq_queue in mesh_path_flush_pending(). This should take care of KASAN reports like this: unreferenced object 0xffff00000668d800 (size 128): comm "kworker/u8:4", pid 67, jiffies 4295419552 (age 1836.444s) hex dump (first 32 bytes): 00 1f 05 09 00 00 ff ff 00 d5 68 06 00 00 ff ff ..........h..... 8e 97 ea eb 3e b8 01 00 00 00 00 00 00 00 00 00 ....>........... backtrace: [<000000007302a0b6>] __kmem_cache_alloc_node+0x1e0/0x35c [<00000000049bd418>] kmalloc_trace+0x34/0x80 [<0000000000d792bb>] mesh_queue_preq+0x44/0x2a8 [<00000000c99c3696>] mesh_nexthop_resolve+0x198/0x19c [<00000000926bf598>] ieee80211_xmit+0x1d0/0x1f4 [<00000000fc8c2284>] __ieee80211_subif_start_xmit+0x30c/0x764 [<000000005926ee38>] ieee80211_subif_start_xmit+0x9c/0x7a4 [<000000004c86e916>] dev_hard_start_xmit+0x174/0x440 [<0000000023495647>] __dev_queue_xmit+0xe24/0x111c [<00000000cfe9ca78>] batadv_send_skb_packet+0x180/0x1e4 [<000000007bacc5d5>] batadv_v_elp_periodic_work+0x2f4/0x508 [<00000000adc3cd94>] process_one_work+0x4b8/0xa1c [<00000000b36425d1>] worker_thread+0x9c/0x634 [<0000000005852dd5>] kthread+0x1bc/0x1c4 [<000000005fccd770>] ret_from_fork+0x10/0x20 unreferenced object 0xffff000009051f00 (size 128): comm "kworker/u8:4", pid 67, jiffies 4295419553 (age 1836.440s) hex dump (first 32 bytes): 90 d6 92 0d 00 00 ff ff 00 d8 68 06 00 00 ff ff ..........h..... 36 27 92 e4 02 e0 01 00 00 58 79 06 00 00 ff ff 6'.......Xy..... backtrace: [<000000007302a0b6>] __kmem_cache_alloc_node+0x1e0/0x35c [<00000000049bd418>] kmalloc_trace+0x34/0x80 [<0000000000d792bb>] mesh_queue_preq+0x44/0x2a8 [<00000000c99c3696>] mesh_nexthop_resolve+0x198/0x19c [<00000000926bf598>] ieee80211_xmit+0x1d0/0x1f4 [<00000000fc8c2284>] __ieee80211_subif_start_xmit+0x30c/0x764 [<000000005926ee38>] ieee80211_subif_start_xmit+0x9c/0x7a4 [<000000004c86e916>] dev_hard_start_xmit+0x174/0x440 [<0000000023495647>] __dev_queue_xmit+0xe24/0x111c [<00000000cfe9ca78>] batadv_send_skb_packet+0x180/0x1e4 [<000000007bacc5d5>] batadv_v_elp_periodic_work+0x2f4/0x508 [<00000000adc3cd94>] process_one_work+0x4b8/0xa1c [<00000000b36425d1>] worker_thread+0x9c/0x634 [<0000000005852dd5>] kthread+0x1bc/0x1c4 [<000000005fccd770>] ret_from_fork+0x10/0x20

What

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects The hwmp code use objects of type mesh_preq_queue, added to a list in ieee80211_if_mesh, to keep track of mpath we need to resolve. If the mpath gets deleted, ex mesh interface is removed, the entries in that list will never get cleaned. Fix this by flushing all corresponding items of the preq_queue in mesh_path_flush_pending(). This should take care of KASAN reports like this: unreferenced object 0xffff00000668d800 (size 128): comm "kworker/u8:4", pid 67, jiffies 4295419552 (age 1836.444s) hex dump (first 32 bytes): 00 1f 05 09 00 00 ff ff 00 d5 68 06 00 00 ff ff ..........h..... 8e 97 ea eb 3e b8 01 00 00 00 00 00 00 00 00 00 ....>........... backtrace: [<000000007302a0b6>] __kmem_cache_alloc_node+0x1e0/0x35c [<00000000049bd418>] kmalloc_trace+0x34/0x80 [<0000000000d792bb>] mesh_queue_preq+0x44/0x2a8 [<00000000c99c3696>] mesh_nexthop_resolve+0x198/0x19c [<00000000926bf598>] ieee80211_xmit+0x1d0/0x1f4 [<00000000fc8c2284>] __ieee80211_subif_start_xmit+0x30c/0x764 [<000000005926ee38>] ieee80211_subif_start_xmit+0x9c/0x7a4 [<000000004c86e916>] dev_hard_start_xmit+0x174/0x440 [<0000000023495647>] __dev_queue_xmit+0xe24/0x111c [<00000000cfe9ca78>] batadv_send_skb_packet+0x180/0x1e4 [<000000007bacc5d5>] batadv_v_elp_periodic_work+0x2f4/0x508 [<00000000adc3cd94>] process_one_work+0x4b8/0xa1c [<00000000b36425d1>] worker_thread+0x9c/0x634 [<0000000005852dd5>] kthread+0x1bc/0x1c4 [<000000005fccd770>] ret_from_fork+0x10/0x20 unreferenced object 0xffff000009051f00 (size 128): comm "kworker/u8:4", pid 67, jiffies 4295419553 (age 1836.440s) hex dump (first 32 bytes): 90 d6 92 0d 00 00 ff ff 00 d8 68 06 00 00 ff ff ..........h..... 36 27 92 e4 02 e0 01 00 00 58 79 06 00 00 ff ff 6'.......Xy..... backtrace: [<000000007302a0b6>] __kmem_cache_alloc_node+0x1e0/0x35c [<00000000049bd418>] kmalloc_trace+0x34/0x80 [<0000000000d792bb>] mesh_queue_preq+0x44/0x2a8 [<00000000c99c3696>] mesh_nexthop_resolve+0x198/0x19c [<00000000926bf598>] ieee80211_xmit+0x1d0/0x1f4 [<00000000fc8c2284>] __ieee80211_subif_start_xmit+0x30c/0x764 [<000000005926ee38>] ieee80211_subif_start_xmit+0x9c/0x7a4 [<000000004c86e916>] dev_hard_start_xmit+0x174/0x440 [<0000000023495647>] __dev_queue_xmit+0xe24/0x111c [<00000000cfe9ca78>] batadv_send_skb_packet+0x180/0x1e4 [<000000007bacc5d5>] batadv_v_elp_periodic_work+0x2f4/0x508 [<00000000adc3cd94>] process_one_work+0x4b8/0xa1c [<00000000b36425d1>] worker_thread+0x9c/0x634 [<0000000005852dd5>] kthread+0x1bc/0x1c4 [<000000005fccd770>] ret_from_fork+0x10/0x20

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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: wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects The hwmp code use objects of type mesh_preq_queue, added to a list in ieee80211_if_mesh, to keep track of mpath we need to resolve. If the mpath gets deleted, ex mesh interface is removed, the entries in that list will never get cleaned. Fix this by flushing all corresponding items of the preq_queue in mesh_path_flush_pending(). This should take care of KASAN reports like this: unreferenced object 0xffff00000668d800 (size 128): comm "kworker/u8:4", pid 67, jiffies 4295419552 (age 1836.444s) hex dump (first 32 bytes): 00 1f 05 09 00 00 ff ff 00 d5 68 06 00 00 ff ff ..........h..... 8e 97 ea eb 3e b8 01 00 00 00 00 00 00 00 00 00 ....>........... backtrace: [<000000007302a0b6>] __kmem_cache_alloc_node+0x1e0/0x35c [<00000000049bd418>] kmalloc_trace+0x34/0x80 [<0000000000d792bb>] mesh_queue_preq+0x44/0x2a8 [<00000000c99c3696>] mesh_nexthop_resolve+0x198/0x19c [<00000000926bf598>] ieee80211_xmit+0x1d0/0x1f4 [<00000000fc8c2284>] __ieee80211_subif_start_xmit+0x30c/0x764 [<000000005926ee38>] ieee80211_subif_start_xmit+0x9c/0x7a4 [<000000004c86e916>] dev_hard_start_xmit+0x174/0x440 [<0000000023495647>] __dev_queue_xmit+0xe24/0x111c [<00000000cfe9ca78>] batadv_send_skb_packet+0x180/0x1e4 [<000000007bacc5d5>] batadv_v_elp_periodic_work+0x2f4/0x508 [<00000000adc3cd94>] process_one_work+0x4b8/0xa1c [<00000000b36425d1>] worker_thread+0x9c/0x634 [<0000000005852dd5>] kthread+0x1bc/0x1c4 [<000000005fccd770>] ret_from_fork+0x10/0x20 unreferenced object 0xffff000009051f00 (size 128): comm "kworker/u8:4", pid 67, jiffies 4295419553 (age 1836.440s) hex dump (first 32 bytes): 90 d6 92 0d 00 00 ff ff 00 d8 68 06 00 00 ff ff ..........h..... 36 27 92 e4 02 e0 01 00 00 58 79 06 00 00 ff ff 6'.......Xy..... backtrace: [<000000007302a0b6>] __kmem_cache_alloc_node+0x1e0/0x35c [<00000000049bd418>] kmalloc_trace+0x34/0x80 [<0000000000d792bb>] mesh_queue_preq+0x44/0x2a8 [<00000000c99c3696>] mesh_nexthop_resolve+0x198/0x19c [<00000000926bf598>] ieee80211_xmit+0x1d0/0x1f4 [<00000000fc8c2284>] __ieee80211_subif_start_xmit+0x30c/0x764 [<000000005926ee38>] ieee80211_subif_start_xmit+0x9c/0x7a4 [<000000004c86e916>] dev_hard_start_xmit+0x174/0x440 [<0000000023495647>] __dev_queue_xmit+0xe24/0x111c [<00000000cfe9ca78>] batadv_send_skb_packet+0x180/0x1e4 [<000000007bacc5d5>] batadv_v_elp_periodic_work+0x2f4/0x508 [<00000000adc3cd94>] process_one_work+0x4b8/0xa1c [<00000000b36425d1>] worker_thread+0x9c/0x634 [<0000000005852dd5>] kthread+0x1bc/0x1c4 [<000000005fccd770>] ret_from_fork+0x10/0x20

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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 → Missing Release of Memory after Effective Lifetime → 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-401 ↗

CWE-401: Missing Release of Memory after Effective Lifetime. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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

Official authority intelligence

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

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

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

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

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

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

d?id=CVE-2024-40904 Référence CVE CVE-2024-40905 https://www.cve.org/CVERecord?id=CVE-2024-40905 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40916 https://www.cve.org/CVERecord?id=CVE-2024-40916 Référence CVE CVE-2024-40929 https://www.cve.org/CVERecord?id=CVE-2024-40929 Référence CVE CVE-2024-40931 https://www.cve.org/CVERecord?id=CVE-2024-40931 Référence CVE CVE-2024-40932 https://www.cve.org/CVERecord?id=CVE-2024-40932 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40942 https://www.cve.org/CVERecord?id=CVE-2024-40942 Référence CVE CVE-2024-40943 https://www.cve.org/CVERecord?id=CVE-2024-40943 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40958 https://www.cve.org/CVERecord?id=CVE-2024-40958 Référence CVE CVE-2024-40959 https://www.cve.org/CVERecord?id=CVE-2024-40959 Référence CVE CVE-2024-40960 https://www.cve.org/CVERecord?id=CVE-2024-40960 Référence CVE CVE-2024-40961 https://www.cve.org/CVERecord?id=CVE-2024-40961 Référence CVE CVE-2024-40963 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-40931 Référence CVE CVE-2024-40932 https://www.cve.org/CVERecord?id=CVE-2024-40932 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40935 https://www.cve.org/CVERecord?id=CVE-2024-40935 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-40938 https://www.cve.org/CVERecord?id=CVE-2024-40938 Référence CVE CVE-2024-40939 https://www.cve.org/CVERecord?id=CVE-2024-40939 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40942 https://www.cve.org/CVERecord?id=CVE-2024-40942 Référence CVE CVE-2024-40943 https://www.cve.org/CVERecord?id=CVE-2024-40943 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40953 https://www.cve.org/CVERecord?id=CVE-2024-40953 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40956 https://www.cve.org/CVERecord?id=CVE-2024-40956 Référence CVE CVE-2024-40957 https://www.cve.org/CVERecord?id=CVE-2024-40957 Référence CVE CVE-2024-40958 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40901 Référence CVE CVE-2024-40902 https://www.cve.org/CVERecord?id=CVE-2024-40902 Référence CVE CVE-2024-40904 https://www.cve.org/CVERecord?id=CVE-2024-40904 Référence CVE CVE-2024-40905 https://www.cve.org/CVERecord?id=CVE-2024-40905 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40916 https://www.cve.org/CVERecord?id=CVE-2024-40916 Référence CVE CVE-2024-40932 https://www.cve.org/CVERecord?id=CVE-2024-40932 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40942 https://www.cve.org/CVERecord?id=CVE-2024-40942 Référence CVE CVE-2024-40943 https://www.cve.org/CVERecord?id=CVE-2024-40943 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40958 https://www.cve.org/CVERecord?id=CVE-2024-40958 Référence CVE CVE-2024-40959 https://www.cve.org/CVERecord?id=CVE-2024-40959 Référence CVE CVE-2024-40960 https://www.cve.org/CVERecord?id=CVE-2024-40960 Référence CVE CVE-2024-40961 https://www.cve.org/CVERecord?id=CVE-2024-40961 Référence CVE CVE-2024-40963 https://www.cve.org/CVERecord?id=CVE-2024-40963 Référence CVE CVE-2024-40968 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40927 Référence CVE CVE-2024-40929 https://www.cve.org/CVERecord?id=CVE-2024-40929 Référence CVE CVE-2024-40930 https://www.cve.org/CVERecord?id=CVE-2024-40930 Référence CVE CVE-2024-40932 https://www.cve.org/CVERecord?id=CVE-2024-40932 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40936 https://www.cve.org/CVERecord?id=CVE-2024-40936 Référence CVE CVE-2024-40938 https://www.cve.org/CVERecord?id=CVE-2024-40938 Référence CVE CVE-2024-40939 https://www.cve.org/CVERecord?id=CVE-2024-40939 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40942 https://www.cve.org/CVERecord?id=CVE-2024-40942 Référence CVE CVE-2024-40943 https://www.cve.org/CVERecord?id=CVE-2024-40943 Référence CVE CVE-2024-40944 https://www.cve.org/CVERecord?id=CVE-2024-40944 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40956 https://www.cve.org/CVERecord?id=CVE-2024-40956 Référence CVE CVE-2024-40957 https://www.cve.org/CVERecord?id=CVE-2024-40957 Référence CVE CVE-2024-40958 https://www.cve.org/CVERecord?id=CVE-2024-40958 Référence CVE CVE-2024-40959 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40933 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40935 https://www.cve.org/CVERecord?id=CVE-2024-40935 Référence CVE CVE-2024-40936 https://www.cve.org/CVERecord?id=CVE-2024-40936 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-40938 https://www.cve.org/CVERecord?id=CVE-2024-40938 Référence CVE CVE-2024-40939 https://www.cve.org/CVERecord?id=CVE-2024-40939 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40942 https://www.cve.org/CVERecord?id=CVE-2024-40942 Référence CVE CVE-2024-40943 https://www.cve.org/CVERecord?id=CVE-2024-40943 Référence CVE CVE-2024-40944 https://www.cve.org/CVERecord?id=CVE-2024-40944 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40949 https://www.cve.org/CVERecord?id=CVE-2024-40949 Référence CVE CVE-2024-40951 https://www.cve.org/CVERecord?id=CVE-2024-40951 Référence CVE CVE-2024-40952 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40933 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40935 https://www.cve.org/CVERecord?id=CVE-2024-40935 Référence CVE CVE-2024-40936 https://www.cve.org/CVERecord?id=CVE-2024-40936 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-40938 https://www.cve.org/CVERecord?id=CVE-2024-40938 Référence CVE CVE-2024-40939 https://www.cve.org/CVERecord?id=CVE-2024-40939 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40942 https://www.cve.org/CVERecord?id=CVE-2024-40942 Référence CVE CVE-2024-40943 https://www.cve.org/CVERecord?id=CVE-2024-40943 Référence CVE CVE-2024-40944 https://www.cve.org/CVERecord?id=CVE-2024-40944 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40949 https://www.cve.org/CVERecord?id=CVE-2024-40949 Référence CVE CVE-2024-40951 https://www.cve.org/CVERecord?id=CVE-2024-40951 Référence CVE CVE-2024-40952 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40927 Référence CVE CVE-2024-40929 https://www.cve.org/CVERecord?id=CVE-2024-40929 Référence CVE CVE-2024-40930 https://www.cve.org/CVERecord?id=CVE-2024-40930 Référence CVE CVE-2024-40932 https://www.cve.org/CVERecord?id=CVE-2024-40932 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40936 https://www.cve.org/CVERecord?id=CVE-2024-40936 Référence CVE CVE-2024-40938 https://www.cve.org/CVERecord?id=CVE-2024-40938 Référence CVE CVE-2024-40939 https://www.cve.org/CVERecord?id=CVE-2024-40939 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40942 https://www.cve.org/CVERecord?id=CVE-2024-40942 Référence CVE CVE-2024-40943 https://www.cve.org/CVERecord?id=CVE-2024-40943 Référence CVE CVE-2024-40944 https://www.cve.org/CVERecord?id=CVE-2024-40944 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40956 https://www.cve.org/CVERecord?id=CVE-2024-40956 Référence CVE CVE-2024-40957 https://www.cve.org/CVERecord?id=CVE-2024-40957 Référence CVE CVE-2024-40958 https://www.cve.org/CVERecord?id=CVE-2024-40958 Référence CVE CVE-2024-40959 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40933 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40935 https://www.cve.org/CVERecord?id=CVE-2024-40935 Référence CVE CVE-2024-40936 https://www.cve.org/CVERecord?id=CVE-2024-40936 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-40938 https://www.cve.org/CVERecord?id=CVE-2024-40938 Référence CVE CVE-2024-40939 https://www.cve.org/CVERecord?id=CVE-2024-40939 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40942 https://www.cve.org/CVERecord?id=CVE-2024-40942 Référence CVE CVE-2024-40943 https://www.cve.org/CVERecord?id=CVE-2024-40943 Référence CVE CVE-2024-40944 https://www.cve.org/CVERecord?id=CVE-2024-40944 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40949 https://www.cve.org/CVERecord?id=CVE-2024-40949 Référence CVE CVE-2024-40951 https://www.cve.org/CVERecord?id=CVE-2024-40951 Référence CVE CVE-2024-40952 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40928 Référence CVE CVE-2024-40929 https://www.cve.org/CVERecord?id=CVE-2024-40929 Référence CVE CVE-2024-40931 https://www.cve.org/CVERecord?id=CVE-2024-40931 Référence CVE CVE-2024-40932 https://www.cve.org/CVERecord?id=CVE-2024-40932 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40935 https://www.cve.org/CVERecord?id=CVE-2024-40935 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40942 https://www.cve.org/CVERecord?id=CVE-2024-40942 Référence CVE CVE-2024-40943 https://www.cve.org/CVERecord?id=CVE-2024-40943 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40953 https://www.cve.org/CVERecord?id=CVE-2024-40953 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40956 https://www.cve.org/CVERecord?id=CVE-2024-40956 Référence CVE CVE-2024-40958 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40928 Référence CVE CVE-2024-40929 https://www.cve.org/CVERecord?id=CVE-2024-40929 Référence CVE CVE-2024-40931 https://www.cve.org/CVERecord?id=CVE-2024-40931 Référence CVE CVE-2024-40932 https://www.cve.org/CVERecord?id=CVE-2024-40932 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40935 https://www.cve.org/CVERecord?id=CVE-2024-40935 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40942 https://www.cve.org/CVERecord?id=CVE-2024-40942 Référence CVE CVE-2024-40943 https://www.cve.org/CVERecord?id=CVE-2024-40943 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40953 https://www.cve.org/CVERecord?id=CVE-2024-40953 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40956 https://www.cve.org/CVERecord?id=CVE-2024-40956 Référence CVE CVE-2024-40958 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40931 Référence CVE CVE-2024-40932 https://www.cve.org/CVERecord?id=CVE-2024-40932 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40935 https://www.cve.org/CVERecord?id=CVE-2024-40935 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-40938 https://www.cve.org/CVERecord?id=CVE-2024-40938 Référence CVE CVE-2024-40939 https://www.cve.org/CVERecord?id=CVE-2024-40939 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40942 https://www.cve.org/CVERecord?id=CVE-2024-40942 Référence CVE CVE-2024-40943 https://www.cve.org/CVERecord?id=CVE-2024-40943 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40953 https://www.cve.org/CVERecord?id=CVE-2024-40953 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40956 https://www.cve.org/CVERecord?id=CVE-2024-40956 Référence CVE CVE-2024-40957 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028110Linux の 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: < 2.6.26, 4.19.317 ≤ 4.19.*, 5.4.279 ≤ 5.4.*, 5.10.221 ≤ 5.10.*, 5.15.162 ≤ 5.15.*, 6.1.95 ≤ 6.1.*, 6.6.35 ≤ 6.6.*, 6.9.6 ≤ 6.9.*, 6.10 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 12 Jul 2024 · Last source change 12 May 2026, 11:55 UTC · CWE-401 · Missing Release of Memory after Effective Lifetime

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-38830
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-38830↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-40942 · cve.blacktree.nl