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

drm/amdgpu: fix use-after-free bug

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Within 7 days

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

Patch available
Distribution package intelligence

Ubuntu vendor package status

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

11 package states
Repository candidate not checked

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

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-23918

No EUVD known-exploited evidence

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

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

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

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix use-after-free bug The bug can be triggered by sending a single amdgpu_gem_userptr_ioctl to the AMDGPU DRM driver on any ASICs with an invalid address and size. The bug was reported by Joonkyo Jung <joonkyoj@yonsei.ac.kr>. For example the following code: static void Syzkaller1(int fd) { struct drm_amdgpu_gem_userptr arg; int ret; arg.addr = 0xffffffffffff0000; arg.size = 0x80000000; /*2 Gb*/ arg.flags = 0x7; ret = drmIoctl(fd, 0xc1186451/*amdgpu_gem_userptr_ioctl*/, &arg); } Due to the address and size are not valid there is a failure in amdgpu_hmm_register->mmu_interval_notifier_insert->__mmu_interval_notifier_insert-> check_shl_overflow, but we even the amdgpu_hmm_register failure we still call amdgpu_hmm_unregister into amdgpu_gem_object_free which causes access to a bad address. The following stack is below when the issue is reproduced when Kazan is enabled: [ +0.000014] Hardware name: ASUS System Product Name/ROG STRIX B550-F GAMING (WI-FI), BIOS 1401 12/03/2020 [ +0.000009] RIP: 0010:mmu_interval_notifier_remove+0x327/0x340 [ +0.000017] Code: ff ff 49 89 44 24 08 48 b8 00 01 00 00 00 00 ad de 4c 89 f7 49 89 47 40 48 83 c0 22 49 89 47 48 e8 ce d1 2d 01 e9 32 ff ff ff <0f> 0b e9 16 ff ff ff 4c 89 ef e8 fa 14 b3 ff e9 36 ff ff ff e8 80 [ +0.000014] RSP: 0018:ffffc90002657988 EFLAGS: 00010246 [ +0.000013] RAX: 0000000000000000 RBX: 1ffff920004caf35 RCX: ffffffff8160565b [ +0.000011] RDX: dffffc0000000000 RSI: 0000000000000004 RDI: ffff8881a9f78260 [ +0.000010] RBP: ffffc90002657a70 R08: 0000000000000001 R09: fffff520004caf25 [ +0.000010] R10: 0000000000000003 R11: ffffffff8161d1d6 R12: ffff88810e988c00 [ +0.000010] R13: ffff888126fb5a00 R14: ffff88810e988c0c R15: ffff8881a9f78260 [ +0.000011] FS: 00007ff9ec848540(0000) GS:ffff8883cc880000(0000) knlGS:0000000000000000 [ +0.000012] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ +0.000010] CR2: 000055b3f7e14328 CR3: 00000001b5770000 CR4: 0000000000350ef0 [ +0.000010] Call Trace: [ +0.000006] <TASK> [ +0.000007] ? show_regs+0x6a/0x80 [ +0.000018] ? __warn+0xa5/0x1b0 [ +0.000019] ? mmu_interval_notifier_remove+0x327/0x340 [ +0.000018] ? report_bug+0x24a/0x290 [ +0.000022] ? handle_bug+0x46/0x90 [ +0.000015] ? exc_invalid_op+0x19/0x50 [ +0.000016] ? asm_exc_invalid_op+0x1b/0x20 [ +0.000017] ? kasan_save_stack+0x26/0x50 [ +0.000017] ? mmu_interval_notifier_remove+0x23b/0x340 [ +0.000019] ? mmu_interval_notifier_remove+0x327/0x340 [ +0.000019] ? mmu_interval_notifier_remove+0x23b/0x340 [ +0.000020] ? __pfx_mmu_interval_notifier_remove+0x10/0x10 [ +0.000017] ? kasan_save_alloc_info+0x1e/0x30 [ +0.000018] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? __kasan_kmalloc+0xb1/0xc0 [ +0.000018] ? srso_return_thunk+0x5/0x5f [ +0.000013] ? __kasan_check_read+0x11/0x20 [ +0.000020] amdgpu_hmm_unregister+0x34/0x50 [amdgpu] [ +0.004695] amdgpu_gem_object_free+0x66/0xa0 [amdgpu] [ +0.004534] ? __pfx_amdgpu_gem_object_free+0x10/0x10 [amdgpu] [ +0.004291] ? do_syscall_64+0x5f/0xe0 [ +0.000023] ? srso_return_thunk+0x5/0x5f [ +0.000017] drm_gem_object_free+0x3b/0x50 [drm] [ +0.000489] amdgpu_gem_userptr_ioctl+0x306/0x500 [amdgpu] [ +0.004295] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004270] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? __this_cpu_preempt_check+0x13/0x20 [ +0.000015] ? srso_return_thunk+0x5/0x5f [ +0.000013] ? sysvec_apic_timer_interrupt+0x57/0xc0 [ +0.000020] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? asm_sysvec_apic_timer_interrupt+0x1b/0x20 [ +0.000022] ? drm_ioctl_kernel+0x17b/0x1f0 [drm] [ +0.000496] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004272] ? drm_ioctl_kernel+0x190/0x1f0 [drm] [ +0.000492] drm_ioctl_kernel+0x140/0x1f0 [drm] [ +0.000497] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004297] ? __pfx_drm_ioctl_kernel+0x10/0x10 [d ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix use-after-free bug The bug can be triggered by sending a single amdgpu_gem_userptr_ioctl to the AMDGPU DRM driver on any ASICs with an invalid address and size. The bug was reported by Joonkyo Jung <joonkyoj@yonsei.ac.kr>. For example the following code: static void Syzkaller1(int fd) { struct drm_amdgpu_gem_userptr arg; int ret; arg.addr = 0xffffffffffff0000; arg.size = 0x80000000; /*2 Gb*/ arg.flags = 0x7; ret = drmIoctl(fd, 0xc1186451/*amdgpu_gem_userptr_ioctl*/, &arg); } Due to the address and size are not valid there is a failure in amdgpu_hmm_register->mmu_interval_notifier_insert->__mmu_interval_notifier_insert-> check_shl_overflow, but we even the amdgpu_hmm_register failure we still call amdgpu_hmm_unregister into amdgpu_gem_object_free which causes access to a bad address. The following stack is below when the issue is reproduced when Kazan is enabled: [ +0.000014] Hardware name: ASUS System Product Name/ROG STRIX B550-F GAMING (WI-FI), BIOS 1401 12/03/2020 [ +0.000009] RIP: 0010:mmu_interval_notifier_remove+0x327/0x340 [ +0.000017] Code: ff ff 49 89 44 24 08 48 b8 00 01 00 00 00 00 ad de 4c 89 f7 49 89 47 40 48 83 c0 22 49 89 47 48 e8 ce d1 2d 01 e9 32 ff ff ff <0f> 0b e9 16 ff ff ff 4c 89 ef e8 fa 14 b3 ff e9 36 ff ff ff e8 80 [ +0.000014] RSP: 0018:ffffc90002657988 EFLAGS: 00010246 [ +0.000013] RAX: 0000000000000000 RBX: 1ffff920004caf35 RCX: ffffffff8160565b [ +0.000011] RDX: dffffc0000000000 RSI: 0000000000000004 RDI: ffff8881a9f78260 [ +0.000010] RBP: ffffc90002657a70 R08: 0000000000000001 R09: fffff520004caf25 [ +0.000010] R10: 0000000000000003 R11: ffffffff8161d1d6 R12: ffff88810e988c00 [ +0.000010] R13: ffff888126fb5a00 R14: ffff88810e988c0c R15: ffff8881a9f78260 [ +0.000011] FS: 00007ff9ec848540(0000) GS:ffff8883cc880000(0000) knlGS:0000000000000000 [ +0.000012] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ +0.000010] CR2: 000055b3f7e14328 CR3: 00000001b5770000 CR4: 0000000000350ef0 [ +0.000010] Call Trace: [ +0.000006] <TASK> [ +0.000007] ? show_regs+0x6a/0x80 [ +0.000018] ? __warn+0xa5/0x1b0 [ +0.000019] ? mmu_interval_notifier_remove+0x327/0x340 [ +0.000018] ? report_bug+0x24a/0x290 [ +0.000022] ? handle_bug+0x46/0x90 [ +0.000015] ? exc_invalid_op+0x19/0x50 [ +0.000016] ? asm_exc_invalid_op+0x1b/0x20 [ +0.000017] ? kasan_save_stack+0x26/0x50 [ +0.000017] ? mmu_interval_notifier_remove+0x23b/0x340 [ +0.000019] ? mmu_interval_notifier_remove+0x327/0x340 [ +0.000019] ? mmu_interval_notifier_remove+0x23b/0x340 [ +0.000020] ? __pfx_mmu_interval_notifier_remove+0x10/0x10 [ +0.000017] ? kasan_save_alloc_info+0x1e/0x30 [ +0.000018] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? __kasan_kmalloc+0xb1/0xc0 [ +0.000018] ? srso_return_thunk+0x5/0x5f [ +0.000013] ? __kasan_check_read+0x11/0x20 [ +0.000020] amdgpu_hmm_unregister+0x34/0x50 [amdgpu] [ +0.004695] amdgpu_gem_object_free+0x66/0xa0 [amdgpu] [ +0.004534] ? __pfx_amdgpu_gem_object_free+0x10/0x10 [amdgpu] [ +0.004291] ? do_syscall_64+0x5f/0xe0 [ +0.000023] ? srso_return_thunk+0x5/0x5f [ +0.000017] drm_gem_object_free+0x3b/0x50 [drm] [ +0.000489] amdgpu_gem_userptr_ioctl+0x306/0x500 [amdgpu] [ +0.004295] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004270] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? __this_cpu_preempt_check+0x13/0x20 [ +0.000015] ? srso_return_thunk+0x5/0x5f [ +0.000013] ? sysvec_apic_timer_interrupt+0x57/0xc0 [ +0.000020] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? asm_sysvec_apic_timer_interrupt+0x1b/0x20 [ +0.000022] ? drm_ioctl_kernel+0x17b/0x1f0 [drm] [ +0.000496] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004272] ? drm_ioctl_kernel+0x190/0x1f0 [drm] [ +0.000492] drm_ioctl_kernel+0x140/0x1f0 [drm] [ +0.000497] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004297] ? __pfx_drm_ioctl_kernel+0x10/0x10 [d ---truncated---

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: drm/amdgpu: fix use-after-free bug The bug can be triggered by sending a single amdgpu_gem_userptr_ioctl to the AMDGPU DRM driver on any ASICs with an invalid address and size. The bug was reported by Joonkyo Jung <joonkyoj@yonsei.ac.kr>. For example the following code: static void Syzkaller1(int fd) { struct drm_amdgpu_gem_userptr arg; int ret; arg.addr = 0xffffffffffff0000; arg.size = 0x80000000; /*2 Gb*/ arg.flags = 0x7; ret = drmIoctl(fd, 0xc1186451/*amdgpu_gem_userptr_ioctl*/, &arg); } Due to the address and size are not valid there is a failure in amdgpu_hmm_register->mmu_interval_notifier_insert->__mmu_interval_notifier_insert-> check_shl_overflow, but we even the amdgpu_hmm_register failure we still call amdgpu_hmm_unregister into amdgpu_gem_object_free which causes access to a bad address. The following stack is below when the issue is reproduced when Kazan is enabled: [ +0.000014] Hardware name: ASUS System Product Name/ROG STRIX B550-F GAMING (WI-FI), BIOS 1401 12/03/2020 [ +0.000009] RIP: 0010:mmu_interval_notifier_remove+0x327/0x340 [ +0.000017] Code: ff ff 49 89 44 24 08 48 b8 00 01 00 00 00 00 ad de 4c 89 f7 49 89 47 40 48 83 c0 22 49 89 47 48 e8 ce d1 2d 01 e9 32 ff ff ff <0f> 0b e9 16 ff ff ff 4c 89 ef e8 fa 14 b3 ff e9 36 ff ff ff e8 80 [ +0.000014] RSP: 0018:ffffc90002657988 EFLAGS: 00010246 [ +0.000013] RAX: 0000000000000000 RBX: 1ffff920004caf35 RCX: ffffffff8160565b [ +0.000011] RDX: dffffc0000000000 RSI: 0000000000000004 RDI: ffff8881a9f78260 [ +0.000010] RBP: ffffc90002657a70 R08: 0000000000000001 R09: fffff520004caf25 [ +0.000010] R10: 0000000000000003 R11: ffffffff8161d1d6 R12: ffff88810e988c00 [ +0.000010] R13: ffff888126fb5a00 R14: ffff88810e988c0c R15: ffff8881a9f78260 [ +0.000011] FS: 00007ff9ec848540(0000) GS:ffff8883cc880000(0000) knlGS:0000000000000000 [ +0.000012] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ +0.000010] CR2: 000055b3f7e14328 CR3: 00000001b5770000 CR4: 0000000000350ef0 [ +0.000010] Call Trace: [ +0.000006] <TASK> [ +0.000007] ? show_regs+0x6a/0x80 [ +0.000018] ? __warn+0xa5/0x1b0 [ +0.000019] ? mmu_interval_notifier_remove+0x327/0x340 [ +0.000018] ? report_bug+0x24a/0x290 [ +0.000022] ? handle_bug+0x46/0x90 [ +0.000015] ? exc_invalid_op+0x19/0x50 [ +0.000016] ? asm_exc_invalid_op+0x1b/0x20 [ +0.000017] ? kasan_save_stack+0x26/0x50 [ +0.000017] ? mmu_interval_notifier_remove+0x23b/0x340 [ +0.000019] ? mmu_interval_notifier_remove+0x327/0x340 [ +0.000019] ? mmu_interval_notifier_remove+0x23b/0x340 [ +0.000020] ? __pfx_mmu_interval_notifier_remove+0x10/0x10 [ +0.000017] ? kasan_save_alloc_info+0x1e/0x30 [ +0.000018] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? __kasan_kmalloc+0xb1/0xc0 [ +0.000018] ? srso_return_thunk+0x5/0x5f [ +0.000013] ? __kasan_check_read+0x11/0x20 [ +0.000020] amdgpu_hmm_unregister+0x34/0x50 [amdgpu] [ +0.004695] amdgpu_gem_object_free+0x66/0xa0 [amdgpu] [ +0.004534] ? __pfx_amdgpu_gem_object_free+0x10/0x10 [amdgpu] [ +0.004291] ? do_syscall_64+0x5f/0xe0 [ +0.000023] ? srso_return_thunk+0x5/0x5f [ +0.000017] drm_gem_object_free+0x3b/0x50 [drm] [ +0.000489] amdgpu_gem_userptr_ioctl+0x306/0x500 [amdgpu] [ +0.004295] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004270] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? __this_cpu_preempt_check+0x13/0x20 [ +0.000015] ? srso_return_thunk+0x5/0x5f [ +0.000013] ? sysvec_apic_timer_interrupt+0x57/0xc0 [ +0.000020] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? asm_sysvec_apic_timer_interrupt+0x1b/0x20 [ +0.000022] ? drm_ioctl_kernel+0x17b/0x1f0 [drm] [ +0.000496] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004272] ? drm_ioctl_kernel+0x190/0x1f0 [drm] [ +0.000492] drm_ioctl_kernel+0x140/0x1f0 [drm] [ +0.000497] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004297] ? __pfx_drm_ioctl_kernel+0x10/0x10 [d ---truncated---

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-W-2024-1905IBM QRadar SIEM: Mehrere Schwachstellen

Ein entfernter, anonymer oder lokaler Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, eine Man-in-the-Middle-Situation zu schaffen, Sicherheitsmaßnahmen zu umgehen oder eine Denial-of-Service-Situation zu schaffen.

Official advisory
BSI · German · WID-SEC-W-2024-0749Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service oder einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

cord?id=CVE-2024-2236 Référence CVE CVE-2024-24864 https://www.cve.org/CVERecord?id=CVE-2024-24864 Référence CVE CVE-2024-2511 https://www.cve.org/CVERecord?id=CVE-2024-2511 Référence CVE CVE-2024-25740 https://www.cve.org/CVERecord?id=CVE-2024-25740 Référence CVE CVE-2024-25743 https://www.cve.org/CVERecord?id=CVE-2024-25743 Référence CVE CVE-2024-26595 https://www.cve.org/CVERecord?id=CVE-2024-26595 Référence CVE CVE-2024-26605 https://www.cve.org/CVERecord?id=CVE-2024-26605 Référence CVE CVE-2024-26647 https://www.cve.org/CVERecord?id=CVE-2024-26647 Référence CVE CVE-2024-26648 https://www.cve.org/CVERecord?id=CVE-2024-26648 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26658 https://www.cve.org/CVERecord?id=CVE-2024-26658 Référence CVE CVE-2024-26662 https://www.cve.org/CVERecord?id=CVE-2024-26662 Référence CVE CVE-2024-26672 https://www.cve.org/CVERecord?id=CVE-2024-26672 Référence CVE CVE-2024-26691 https://www.cve.org/CVERecord?id=CVE-2024-26691 Référence CVE CVE-2024-26699 https://www.cve.org/CVERecord?id=CVE-2024-26699 Référence CVE CVE-2024-26714 https://www.cve.org/CVERecord?id=CVE-2024-26714 Référence CVE CVE-2024-26719 https://www.cve.org/CVERecord?id=CVE-2024-26719 Référence CVE CVE-2024-26740 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

cord?id=CVE-2024-2236 Référence CVE CVE-2024-24864 https://www.cve.org/CVERecord?id=CVE-2024-24864 Référence CVE CVE-2024-2511 https://www.cve.org/CVERecord?id=CVE-2024-2511 Référence CVE CVE-2024-25740 https://www.cve.org/CVERecord?id=CVE-2024-25740 Référence CVE CVE-2024-25743 https://www.cve.org/CVERecord?id=CVE-2024-25743 Référence CVE CVE-2024-26595 https://www.cve.org/CVERecord?id=CVE-2024-26595 Référence CVE CVE-2024-26605 https://www.cve.org/CVERecord?id=CVE-2024-26605 Référence CVE CVE-2024-26647 https://www.cve.org/CVERecord?id=CVE-2024-26647 Référence CVE CVE-2024-26648 https://www.cve.org/CVERecord?id=CVE-2024-26648 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26658 https://www.cve.org/CVERecord?id=CVE-2024-26658 Référence CVE CVE-2024-26662 https://www.cve.org/CVERecord?id=CVE-2024-26662 Référence CVE CVE-2024-26672 https://www.cve.org/CVERecord?id=CVE-2024-26672 Référence CVE CVE-2024-26691 https://www.cve.org/CVERecord?id=CVE-2024-26691 Référence CVE CVE-2024-26699 https://www.cve.org/CVERecord?id=CVE-2024-26699 Référence CVE CVE-2024-26714 https://www.cve.org/CVERecord?id=CVE-2024-26714 Référence CVE CVE-2024-26719 https://www.cve.org/CVERecord?id=CVE-2024-26719 Référence CVE CVE-2024-26740 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49728 Référence CVE CVE-2023-52572 https://www.cve.org/CVERecord?id=CVE-2023-52572 Référence CVE CVE-2023-52621 https://www.cve.org/CVERecord?id=CVE-2023-52621 Référence CVE CVE-2023-52752 https://www.cve.org/CVERecord?id=CVE-2023-52752 Référence CVE CVE-2023-52757 https://www.cve.org/CVERecord?id=CVE-2023-52757 Référence CVE CVE-2023-52857 https://www.cve.org/CVERecord?id=CVE-2023-52857 Référence CVE CVE-2023-52927 https://www.cve.org/CVERecord?id=CVE-2023-52927 Référence CVE CVE-2023-53034 https://www.cve.org/CVERecord?id=CVE-2023-53034 Référence CVE CVE-2024-24855 https://www.cve.org/CVERecord?id=CVE-2024-24855 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26686 https://www.cve.org/CVERecord?id=CVE-2024-26686 Référence CVE CVE-2024-26739 https://www.cve.org/CVERecord?id=CVE-2024-26739 Référence CVE CVE-2024-26767 https://www.cve.org/CVERecord?id=CVE-2024-26767 Référence CVE CVE-2024-26928 https://www.cve.org/CVERecord?id=CVE-2024-26928 Référence CVE CVE-2024-26982 https://www.cve.org/CVERecord?id=CVE-2024-26982 Référence CVE CVE-2024-27056 https://www.cve.org/CVERecord?id=CVE-2024-27056 Référence CVE CVE-2024-35866 https://www.cve.org/CVERecord?id=CVE-2024-35866 Référence CVE CVE-2024-35867 https://www.cve.org/CVERecord?id=

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

an. Elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et un déni de service. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian DSA-5900-1 du 12 avril 2025 https://lists.debian.org/debian-security-announce/2025/msg00062.html Référence CVE CVE-2023-52857 https://www.cve.org/CVERecord?id=CVE-2023-52857 Référence CVE CVE-2023-52927 https://www.cve.org/CVERecord?id=CVE-2023-52927 Référence CVE CVE-2024-24855 https://www.cve.org/CVERecord?id=CVE-2024-24855 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26767 https://www.cve.org/CVERecord?id=CVE-2024-26767 Référence CVE CVE-2024-26982 https://www.cve.org/CVERecord?id=CVE-2024-26982 Référence CVE CVE-2024-27056 https://www.cve.org/CVERecord?id=CVE-2024-27056 Référence CVE CVE-2024-35866 https://www.cve.org/CVERecord?id=CVE-2024-35866 Référence CVE CVE-2024-38611 https://www.cve.org/CVERecord?id=CVE-2024-38611 Référence CVE CVE-2024-40973 https://www.cve.org/CVERecord?id=CVE-2024-40973 Référence CVE CVE-2024-42129 https://www.cve.org/CVERecord?id=CVE-2024-42129 Référence CVE CVE-2024-43831 https://www.cve.org/CVERecord?id=

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

de sécurité Red Hat RHSA-2024:9500 du 13 novembre 2024 https://access.redhat.com/errata/RHSA-2024:9500 Bulletin de sécurité Red Hat RHSA-2024:9546 du 13 novembre 2024 https://access.redhat.com/errata/RHSA-2024:9546 Bulletin de sécurité Red Hat RHSA-2024:9605 du 14 novembre 2024 https://access.redhat.com/errata/RHSA-2024:9605 Référence CVE CVE-2022-48695 https://www.cve.org/CVERecord?id=CVE-2022-48695 Référence CVE CVE-2023-52522 https://www.cve.org/CVERecord?id=CVE-2023-52522 Référence CVE CVE-2023-52749 https://www.cve.org/CVERecord?id=CVE-2023-52749 Référence CVE CVE-2024-26640 https://www.cve.org/CVERecord?id=CVE-2024-26640 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26772 https://www.cve.org/CVERecord?id=CVE-2024-26772 Référence CVE CVE-2024-26837 https://www.cve.org/CVERecord?id=CVE-2024-26837 Référence CVE CVE-2024-26870 https://www.cve.org/CVERecord?id=CVE-2024-26870 Référence CVE CVE-2024-26906 https://www.cve.org/CVERecord?id=CVE-2024-26906 Référence CVE CVE-2024-26984 https://www.cve.org/CVERecord?id=CVE-2024-26984 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-35950 https://www.cve.org/CVERecord?id=CVE-2024-35950 Référence CVE CVE-2024-38564 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-22195 Référence CVE CVE-2024-22354 https://www.cve.org/CVERecord?id=CVE-2024-22354 Référence CVE CVE-2024-23944 https://www.cve.org/CVERecord?id=CVE-2024-23944 Référence CVE CVE-2024-25629 https://www.cve.org/CVERecord?id=CVE-2024-25629 Référence CVE CVE-2024-25710 https://www.cve.org/CVERecord?id=CVE-2024-25710 Référence CVE CVE-2024-26308 https://www.cve.org/CVERecord?id=CVE-2024-26308 Référence CVE CVE-2024-26583 https://www.cve.org/CVERecord?id=CVE-2024-26583 Référence CVE CVE-2024-26584 https://www.cve.org/CVERecord?id=CVE-2024-26584 Référence CVE CVE-2024-26585 https://www.cve.org/CVERecord?id=CVE-2024-26585 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26735 https://www.cve.org/CVERecord?id=CVE-2024-26735 Référence CVE CVE-2024-26759 https://www.cve.org/CVERecord?id=CVE-2024-26759 Référence CVE CVE-2024-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26826 https://www.cve.org/CVERecord?id=CVE-2024-26826 Référence CVE CVE-2024-26859 https://www.cve.org/CVERecord?id=CVE-2024-26859 Référence CVE CVE-2024-26906 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2024-AVI-0741Multiples vulnérabilités dans Juniper Secure Analytics

d?id=CVE-2024-26583 Référence CVE CVE-2024-26584 https://www.cve.org/CVERecord?id=CVE-2024-26584 Référence CVE CVE-2024-26585 https://www.cve.org/CVERecord?id=CVE-2024-26585 Référence CVE CVE-2024-26593 https://www.cve.org/CVERecord?id=CVE-2024-26593 Référence CVE CVE-2024-26603 https://www.cve.org/CVERecord?id=CVE-2024-26603 Référence CVE CVE-2024-26610 https://www.cve.org/CVERecord?id=CVE-2024-26610 Référence CVE CVE-2024-26615 https://www.cve.org/CVERecord?id=CVE-2024-26615 Référence CVE CVE-2024-26642 https://www.cve.org/CVERecord?id=CVE-2024-26642 Référence CVE CVE-2024-26643 https://www.cve.org/CVERecord?id=CVE-2024-26643 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26659 https://www.cve.org/CVERecord?id=CVE-2024-26659 Référence CVE CVE-2024-26664 https://www.cve.org/CVERecord?id=CVE-2024-26664 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26693 https://www.cve.org/CVERecord?id=CVE-2024-26693 Référence CVE CVE-2024-26694 https://www.cve.org/CVERecord?id=CVE-2024-26694 Référence CVE CVE-2024-26735 https://www.cve.org/CVERecord?id=CVE-2024-26735 Référence CVE CVE-2024-26743 https://www.cve.org/CVERecord?id=CVE-2024-26743 Référence CVE CVE-2024-26744 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2024-AVI-0720Multiples vulnérabilités dans IBM QRadar SIEM

ecord?id=CVE-2023-52877 Référence CVE CVE-2023-52878 https://www.cve.org/CVERecord?id=CVE-2023-52878 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2023-7008 https://www.cve.org/CVERecord?id=CVE-2023-7008 Référence CVE CVE-2024-1048 https://www.cve.org/CVERecord?id=CVE-2024-1048 Référence CVE CVE-2024-22365 https://www.cve.org/CVERecord?id=CVE-2024-22365 Référence CVE CVE-2024-26583 https://www.cve.org/CVERecord?id=CVE-2024-26583 Référence CVE CVE-2024-26584 https://www.cve.org/CVERecord?id=CVE-2024-26584 Référence CVE CVE-2024-26585 https://www.cve.org/CVERecord?id=CVE-2024-26585 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26735 https://www.cve.org/CVERecord?id=CVE-2024-26735 Référence CVE CVE-2024-26759 https://www.cve.org/CVERecord?id=CVE-2024-26759 Référence CVE CVE-2024-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26826 https://www.cve.org/CVERecord?id=CVE-2024-26826 Référence CVE CVE-2024-26859 https://www.cve.org/CVERecord?id=CVE-2024-26859 Référence CVE CVE-2024-26906 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-26635 Référence CVE CVE-2024-26636 https://www.cve.org/CVERecord?id=CVE-2024-26636 Référence CVE CVE-2024-26638 https://www.cve.org/CVERecord?id=CVE-2024-26638 Référence CVE CVE-2024-26641 https://www.cve.org/CVERecord?id=CVE-2024-26641 Référence CVE CVE-2024-26642 https://www.cve.org/CVERecord?id=CVE-2024-26642 Référence CVE CVE-2024-26643 https://www.cve.org/CVERecord?id=CVE-2024-26643 Référence CVE CVE-2024-26650 https://www.cve.org/CVERecord?id=CVE-2024-26650 Référence CVE CVE-2024-26652 https://www.cve.org/CVERecord?id=CVE-2024-26652 Référence CVE CVE-2024-26654 https://www.cve.org/CVERecord?id=CVE-2024-26654 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26657 https://www.cve.org/CVERecord?id=CVE-2024-26657 Référence CVE CVE-2024-26659 https://www.cve.org/CVERecord?id=CVE-2024-26659 Référence CVE CVE-2024-26661 https://www.cve.org/CVERecord?id=CVE-2024-26661 Référence CVE CVE-2024-26663 https://www.cve.org/CVERecord?id=CVE-2024-26663 Référence CVE CVE-2024-26665 https://www.cve.org/CVERecord?id=CVE-2024-26665 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26674 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2023-52835 Référence CVE CVE-2023-52877 https://www.cve.org/CVERecord?id=CVE-2023-52877 Référence CVE CVE-2023-52878 https://www.cve.org/CVERecord?id=CVE-2023-52878 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2024-0193 https://www.cve.org/CVERecord?id=CVE-2024-0193 Référence CVE CVE-2024-26583 https://www.cve.org/CVERecord?id=CVE-2024-26583 Référence CVE CVE-2024-26584 https://www.cve.org/CVERecord?id=CVE-2024-26584 Référence CVE CVE-2024-26585 https://www.cve.org/CVERecord?id=CVE-2024-26585 Référence CVE CVE-2024-26598 https://www.cve.org/CVERecord?id=CVE-2024-26598 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26735 https://www.cve.org/CVERecord?id=CVE-2024-26735 Référence CVE CVE-2024-26759 https://www.cve.org/CVERecord?id=CVE-2024-26759 Référence CVE CVE-2024-26801 https://www.cve.org/CVERecord?id=CVE-2024-26801 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Référence CVE CVE-2024-26826 https://www.cve.org/CVERecord?id=CVE-2024-26826 Référence CVE CVE-2024-26859 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26585 Référence CVE CVE-2024-26601 https://www.cve.org/CVERecord?id=CVE-2024-26601 Référence CVE CVE-2024-26603 https://www.cve.org/CVERecord?id=CVE-2024-26603 Référence CVE CVE-2024-26642 https://www.cve.org/CVERecord?id=CVE-2024-26642 Référence CVE CVE-2024-26643 https://www.cve.org/CVERecord?id=CVE-2024-26643 Référence CVE CVE-2024-26651 https://www.cve.org/CVERecord?id=CVE-2024-26651 Référence CVE CVE-2024-26653 https://www.cve.org/CVERecord?id=CVE-2024-26653 Référence CVE CVE-2024-26654 https://www.cve.org/CVERecord?id=CVE-2024-26654 Référence CVE CVE-2024-26655 https://www.cve.org/CVERecord?id=CVE-2024-26655 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26657 https://www.cve.org/CVERecord?id=CVE-2024-26657 Référence CVE CVE-2024-26659 https://www.cve.org/CVERecord?id=CVE-2024-26659 Référence CVE CVE-2024-26688 https://www.cve.org/CVERecord?id=CVE-2024-26688 Référence CVE CVE-2024-26720 https://www.cve.org/CVERecord?id=CVE-2024-26720 Référence CVE CVE-2024-26733 https://www.cve.org/CVERecord?id=CVE-2024-26733 Référence CVE CVE-2024-26735 https://www.cve.org/CVERecord?id=CVE-2024-26735 Référence CVE CVE-2024-26736 https://www.cve.org/CVERecord?id=CVE-2024-26736 Référence CVE CVE-2024-26737 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26614 Référence CVE CVE-2024-26622 https://www.cve.org/CVERecord?id=CVE-2024-26622 Référence CVE CVE-2024-26625 https://www.cve.org/CVERecord?id=CVE-2024-26625 Référence CVE CVE-2024-26632 https://www.cve.org/CVERecord?id=CVE-2024-26632 Référence CVE CVE-2024-26638 https://www.cve.org/CVERecord?id=CVE-2024-26638 Référence CVE CVE-2024-26642 https://www.cve.org/CVERecord?id=CVE-2024-26642 Référence CVE CVE-2024-26643 https://www.cve.org/CVERecord?id=CVE-2024-26643 Référence CVE CVE-2024-26652 https://www.cve.org/CVERecord?id=CVE-2024-26652 Référence CVE CVE-2024-26654 https://www.cve.org/CVERecord?id=CVE-2024-26654 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26657 https://www.cve.org/CVERecord?id=CVE-2024-26657 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26674 https://www.cve.org/CVERecord?id=CVE-2024-26674 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26684 https://www.cve.org/CVERecord?id=CVE-2024-26684 Référence CVE CVE-2024-26685 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-24855 Référence CVE CVE-2024-24861 https://www.cve.org/CVERecord?id=CVE-2024-24861 Référence CVE CVE-2024-25742 https://www.cve.org/CVERecord?id=CVE-2024-25742 Référence CVE CVE-2024-26601 https://www.cve.org/CVERecord?id=CVE-2024-26601 Référence CVE CVE-2024-26610 https://www.cve.org/CVERecord?id=CVE-2024-26610 Référence CVE CVE-2024-26614 https://www.cve.org/CVERecord?id=CVE-2024-26614 Référence CVE CVE-2024-26622 https://www.cve.org/CVERecord?id=CVE-2024-26622 Référence CVE CVE-2024-26642 https://www.cve.org/CVERecord?id=CVE-2024-26642 Référence CVE CVE-2024-26651 https://www.cve.org/CVERecord?id=CVE-2024-26651 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26660 https://www.cve.org/CVERecord?id=CVE-2024-26660 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26680 https://www.cve.org/CVERecord?id=CVE-2024-26680 Référence CVE CVE-2024-26681 https://www.cve.org/CVERecord?id=CVE-2024-26681 Référence CVE CVE-2024-26684 https://www.cve.org/CVERecord?id=

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
d38ceaf99ed015f2a0b9af3499791bd3a3daae21 < 2e13f88e01ae7e28a7e831bf5c2409c4748e0a60; d38ceaf99ed015f2a0b9af3499791bd3a3daae21 < e87e08c94c9541b4e18c4c13f2f605935f512605; d38ceaf99ed015f2a0b9af3499791bd3a3daae21 < af054a5fb24a144f99895afce9519d709891894c; d38ceaf99ed015f2a0b9af3499791bd3a3daae21 < 22f665ecfd1225afa1309ace623157d12bb9bb0c; d38ceaf99ed015f2a0b9af3499791bd3a3daae21 < 22207fd5c80177b860279653d017474b2812af5e; 4.2
Fixed
< 4.2; 6.1.132 ≤ 6.1.*; 6.6.24 ≤ 6.6.*; 6.7.12 ≤ 6.7.*; 6.8.3 ≤ 6.8.*; 6.9 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 2 Apr 2024 · Last source change 5 Aug 2026, 11:26 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-23918
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates →

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

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