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

IB/core: Fix ib_cache_setup_one error flow cleanup

Linux · Linux

6.5MediumCVSS 3.1
Recommended action
Scheduled

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

Patch available
Distribution package intelligence

Ubuntu vendor package status

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

17 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 8 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 8 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 8 Sept 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 record ↗Source updated 8 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 8 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 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 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 8 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 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 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 record ↗Source updated 8 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 8 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 8 Sept 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 record ↗Source updated 8 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 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 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-42613

No EUVD known-exploited evidence

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

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

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

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: IB/core: Fix ib_cache_setup_one error flow cleanup When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below. Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue. WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff <0f> 0b 4c 8b 75 30 e9 54 ff ff ff 48 8 3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS: 00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? show_regs+0x94/0xa0 ? __warn+0x9e/0x1c0 ? gid_table_release_one+0x181/0x1a0 ? report_bug+0x1f9/0x340 ? gid_table_release_one+0x181/0x1a0 ? handle_bug+0xa2/0x110 ? exc_invalid_op+0x31/0xa0 ? asm_exc_invalid_op+0x16/0x20 ? __warn_printk+0xc7/0x180 ? __warn_printk+0xd4/0x180 ? gid_table_release_one+0x181/0x1a0 ib_device_release+0x71/0xe0 ? __pfx_ib_device_release+0x10/0x10 device_release+0x44/0xd0 kobject_put+0x135/0x3d0 put_device+0x20/0x30 rxe_net_add+0x7d/0xa0 rxe_newlink+0xd7/0x190 nldev_newlink+0x1b0/0x2a0 ? __pfx_nldev_newlink+0x10/0x10 rdma_nl_rcv_msg+0x1ad/0x2e0 rdma_nl_rcv_skb.constprop.0+0x176/0x210 netlink_unicast+0x2de/0x400 netlink_sendmsg+0x306/0x660 __sock_sendmsg+0x110/0x120 ____sys_sendmsg+0x30e/0x390 ___sys_sendmsg+0x9b/0xf0 ? kstrtouint+0x6e/0xa0 ? kstrtouint_from_user+0x7c/0xb0 ? get_pid_task+0xb0/0xd0 ? proc_fail_nth_write+0x5b/0x140 ? __fget_light+0x9a/0x200 ? preempt_count_add+0x47/0xa0 __sys_sendmsg+0x61/0xd0 do_syscall_64+0x50/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e

What

In the Linux kernel, the following vulnerability has been resolved: IB/core: Fix ib_cache_setup_one error flow cleanup When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below. Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue. WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff <0f> 0b 4c 8b 75 30 e9 54 ff ff ff 48 8 3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS: 00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? show_regs+0x94/0xa0 ? __warn+0x9e/0x1c0 ? gid_table_release_one+0x181/0x1a0 ? report_bug+0x1f9/0x340 ? gid_table_release_one+0x181/0x1a0 ? handle_bug+0xa2/0x110 ? exc_invalid_op+0x31/0xa0 ? asm_exc_invalid_op+0x16/0x20 ? __warn_printk+0xc7/0x180 ? __warn_printk+0xd4/0x180 ? gid_table_release_one+0x181/0x1a0 ib_device_release+0x71/0xe0 ? __pfx_ib_device_release+0x10/0x10 device_release+0x44/0xd0 kobject_put+0x135/0x3d0 put_device+0x20/0x30 rxe_net_add+0x7d/0xa0 rxe_newlink+0xd7/0x190 nldev_newlink+0x1b0/0x2a0 ? __pfx_nldev_newlink+0x10/0x10 rdma_nl_rcv_msg+0x1ad/0x2e0 rdma_nl_rcv_skb.constprop.0+0x176/0x210 netlink_unicast+0x2de/0x400 netlink_sendmsg+0x306/0x660 __sock_sendmsg+0x110/0x120 ____sys_sendmsg+0x30e/0x390 ___sys_sendmsg+0x9b/0xf0 ? kstrtouint+0x6e/0xa0 ? kstrtouint_from_user+0x7c/0xb0 ? get_pid_task+0xb0/0xd0 ? proc_fail_nth_write+0x5b/0x140 ? __fget_light+0x9a/0x200 ? preempt_count_add+0x47/0xa0 __sys_sendmsg+0x61/0xd0 do_syscall_64+0x50/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Why

The product does not properly clean up and remove temporary or supporting resources after they have been used.

How

An attacker operating through a network path 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: IB/core: Fix ib_cache_setup_one error flow cleanup When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below. Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue. WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff <0f> 0b 4c 8b 75 30 e9 54 ff ff ff 48 8 3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS: 00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? show_regs+0x94/0xa0 ? __warn+0x9e/0x1c0 ? gid_table_release_one+0x181/0x1a0 ? report_bug+0x1f9/0x340 ? gid_table_release_one+0x181/0x1a0 ? handle_bug+0xa2/0x110 ? exc_invalid_op+0x31/0xa0 ? asm_exc_invalid_op+0x16/0x20 ? __warn_printk+0xc7/0x180 ? __warn_printk+0xd4/0x180 ? gid_table_release_one+0x181/0x1a0 ib_device_release+0x71/0xe0 ? __pfx_ib_device_release+0x10/0x10 device_release+0x44/0xd0 kobject_put+0x135/0x3d0 put_device+0x20/0x30 rxe_net_add+0x7d/0xa0 rxe_newlink+0xd7/0x190 nldev_newlink+0x1b0/0x2a0 ? __pfx_nldev_newlink+0x10/0x10 rdma_nl_rcv_msg+0x1ad/0x2e0 rdma_nl_rcv_skb.constprop.0+0x176/0x210 netlink_unicast+0x2de/0x400 netlink_sendmsg+0x306/0x660 __sock_sendmsg+0x110/0x120 ____sys_sendmsg+0x30e/0x390 ___sys_sendmsg+0x9b/0xf0 ? kstrtouint+0x6e/0xa0 ? kstrtouint_from_user+0x7c/0xb0 ? get_pid_task+0xb0/0xd0 ? proc_fail_nth_write+0x5b/0x140 ? __fget_light+0x9a/0x200 ? preempt_count_add+0x47/0xa0 __sys_sendmsg+0x61/0xd0 do_syscall_64+0x50/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Why

The product does not properly clean up and remove temporary or supporting resources after they have been used.

How

An attacker operating through a network path 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
a network path → Incomplete Cleanup → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
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-459

CWE-459: Incomplete Cleanup. The product does not properly clean up and remove temporary or supporting resources after they have been used.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/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.

AVNetworkAttack vector: The vulnerable component can be reached over a network.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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkCWE-459
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-3251Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..

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

d?id=CVE-2024-47673 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47679 https://www.cve.org/CVERecord?id=CVE-2024-47679 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47689 https://www.cve.org/CVERecord?id=CVE-2024-47689 Référence CVE CVE-2024-47690 https://www.cve.org/CVERecord?id=CVE-2024-47690 Référence CVE CVE-2024-47691 https://www.cve.org/CVERecord?id=CVE-2024-47691 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47703 https://www.cve.org/CVERecord?id=CVE-2024-47703 Référence CVE CVE-2024-47704 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-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47686 https://www.cve.org/CVERecord?id=CVE-2024-47686 Référence CVE CVE-2024-47687 https://www.cve.org/CVERecord?id=CVE-2024-47687 Référence CVE CVE-2024-47688 https://www.cve.org/CVERecord?id=CVE-2024-47688 Référence CVE CVE-2024-47689 https://www.cve.org/CVERecord?id=CVE-2024-47689 Référence CVE CVE-2024-47690 https://www.cve.org/CVERecord?id=CVE-2024-47690 Référence CVE CVE-2024-47691 https://www.cve.org/CVERecord?id=CVE-2024-47691 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47700 https://www.cve.org/CVERecord?id=CVE-2024-47700 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47702 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47686 https://www.cve.org/CVERecord?id=CVE-2024-47686 Référence CVE CVE-2024-47687 https://www.cve.org/CVERecord?id=CVE-2024-47687 Référence CVE CVE-2024-47688 https://www.cve.org/CVERecord?id=CVE-2024-47688 Référence CVE CVE-2024-47689 https://www.cve.org/CVERecord?id=CVE-2024-47689 Référence CVE CVE-2024-47690 https://www.cve.org/CVERecord?id=CVE-2024-47690 Référence CVE CVE-2024-47691 https://www.cve.org/CVERecord?id=CVE-2024-47691 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47694 https://www.cve.org/CVERecord?id=CVE-2024-47694 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47700 https://www.cve.org/CVERecord?id=CVE-2024-47700 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47686 https://www.cve.org/CVERecord?id=CVE-2024-47686 Référence CVE CVE-2024-47687 https://www.cve.org/CVERecord?id=CVE-2024-47687 Référence CVE CVE-2024-47688 https://www.cve.org/CVERecord?id=CVE-2024-47688 Référence CVE CVE-2024-47689 https://www.cve.org/CVERecord?id=CVE-2024-47689 Référence CVE CVE-2024-47690 https://www.cve.org/CVERecord?id=CVE-2024-47690 Référence CVE CVE-2024-47691 https://www.cve.org/CVERecord?id=CVE-2024-47691 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47700 https://www.cve.org/CVERecord?id=CVE-2024-47700 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47702 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47686 https://www.cve.org/CVERecord?id=CVE-2024-47686 Référence CVE CVE-2024-47687 https://www.cve.org/CVERecord?id=CVE-2024-47687 Référence CVE CVE-2024-47688 https://www.cve.org/CVERecord?id=CVE-2024-47688 Référence CVE CVE-2024-47689 https://www.cve.org/CVERecord?id=CVE-2024-47689 Référence CVE CVE-2024-47690 https://www.cve.org/CVERecord?id=CVE-2024-47690 Référence CVE CVE-2024-47691 https://www.cve.org/CVERecord?id=CVE-2024-47691 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47694 https://www.cve.org/CVERecord?id=CVE-2024-47694 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47700 https://www.cve.org/CVERecord?id=CVE-2024-47700 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47671 Référence CVE CVE-2024-47672 https://www.cve.org/CVERecord?id=CVE-2024-47672 Référence CVE CVE-2024-47673 https://www.cve.org/CVERecord?id=CVE-2024-47673 Référence CVE CVE-2024-47674 https://www.cve.org/CVERecord?id=CVE-2024-47674 Référence CVE CVE-2024-47679 https://www.cve.org/CVERecord?id=CVE-2024-47679 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47690 https://www.cve.org/CVERecord?id=CVE-2024-47690 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47705 https://www.cve.org/CVERecord?id=CVE-2024-47705 Référence CVE CVE-2024-47706 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47672 Référence CVE CVE-2024-47673 https://www.cve.org/CVERecord?id=CVE-2024-47673 Référence CVE CVE-2024-47674 https://www.cve.org/CVERecord?id=CVE-2024-47674 Référence CVE CVE-2024-47679 https://www.cve.org/CVERecord?id=CVE-2024-47679 Référence CVE CVE-2024-47683 https://www.cve.org/CVERecord?id=CVE-2024-47683 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47690 https://www.cve.org/CVERecord?id=CVE-2024-47690 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47705 https://www.cve.org/CVERecord?id=CVE-2024-47705 Référence CVE CVE-2024-47706 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-47678 Référence CVE CVE-2024-47679 https://www.cve.org/CVERecord?id=CVE-2024-47679 Référence CVE CVE-2024-47682 https://www.cve.org/CVERecord?id=CVE-2024-47682 Référence CVE CVE-2024-47683 https://www.cve.org/CVERecord?id=CVE-2024-47683 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47686 https://www.cve.org/CVERecord?id=CVE-2024-47686 Référence CVE CVE-2024-47690 https://www.cve.org/CVERecord?id=CVE-2024-47690 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47705 https://www.cve.org/CVERecord?id=CVE-2024-47705 Référence CVE CVE-2024-47706 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47671 Référence CVE CVE-2024-47672 https://www.cve.org/CVERecord?id=CVE-2024-47672 Référence CVE CVE-2024-47673 https://www.cve.org/CVERecord?id=CVE-2024-47673 Référence CVE CVE-2024-47674 https://www.cve.org/CVERecord?id=CVE-2024-47674 Référence CVE CVE-2024-47679 https://www.cve.org/CVERecord?id=CVE-2024-47679 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47690 https://www.cve.org/CVERecord?id=CVE-2024-47690 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47705 https://www.cve.org/CVERecord?id=CVE-2024-47705 Référence CVE CVE-2024-47706 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47679 Référence CVE CVE-2024-47681 https://www.cve.org/CVERecord?id=CVE-2024-47681 Référence CVE CVE-2024-47682 https://www.cve.org/CVERecord?id=CVE-2024-47682 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47686 https://www.cve.org/CVERecord?id=CVE-2024-47686 Référence CVE CVE-2024-47687 https://www.cve.org/CVERecord?id=CVE-2024-47687 Référence CVE CVE-2024-47688 https://www.cve.org/CVERecord?id=CVE-2024-47688 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47702 https://www.cve.org/CVERecord?id=CVE-2024-47702 Référence CVE CVE-2024-47703 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47671 Référence CVE CVE-2024-47672 https://www.cve.org/CVERecord?id=CVE-2024-47672 Référence CVE CVE-2024-47673 https://www.cve.org/CVERecord?id=CVE-2024-47673 Référence CVE CVE-2024-47674 https://www.cve.org/CVERecord?id=CVE-2024-47674 Référence CVE CVE-2024-47679 https://www.cve.org/CVERecord?id=CVE-2024-47679 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47690 https://www.cve.org/CVERecord?id=CVE-2024-47690 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47704 https://www.cve.org/CVERecord?id=CVE-2024-47704 Référence CVE CVE-2024-47705 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47675 Référence CVE CVE-2024-47681 https://www.cve.org/CVERecord?id=CVE-2024-47681 Référence CVE CVE-2024-47682 https://www.cve.org/CVERecord?id=CVE-2024-47682 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47686 https://www.cve.org/CVERecord?id=CVE-2024-47686 Référence CVE CVE-2024-47687 https://www.cve.org/CVERecord?id=CVE-2024-47687 Référence CVE CVE-2024-47688 https://www.cve.org/CVERecord?id=CVE-2024-47688 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47702 https://www.cve.org/CVERecord?id=CVE-2024-47702 Référence CVE CVE-2024-47704 https://www.cve.org/CVERecord?id=CVE-2024-47704 Référence CVE CVE-2024-47705 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
1901b91f99821955eac2bd48fe25ee983385dc00 < 1730d47d1865af89efd01cf0469a9a739cbf60f2; 1901b91f99821955eac2bd48fe25ee983385dc00 < 45f63f4bb9a7128a6209d766c2fc02b3d42fbf3e; 1901b91f99821955eac2bd48fe25ee983385dc00 < d08754be993f270e3d296d8f5d8e071fe6638651; 1901b91f99821955eac2bd48fe25ee983385dc00 < af633fd9d9fff59e31c804f47ca0c8a784977773; 1901b91f99821955eac2bd48fe25ee983385dc00 < 290fe42fe0165205c4451334d8833a9202ae1d52; 1901b91f99821955eac2bd48fe25ee983385dc00 < 1403c8b14765eab805377dd3b75e96ace8747aed; ee7ce7d7e7c76d5ec4c8067d32bbee9728dc9d29; 2a5968f266c7b9dc13917ac573af8d7b7da4023c
Fixed
< 5.7; 5.15.168 ≤ 5.15.*; 6.1.113 ≤ 6.1.*; 6.6.54 ≤ 6.6.*; 6.10.13 ≤ 6.10.*; 6.11.2 ≤ 6.11.*; 6.12 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 21 Oct 2024 · Last source change 23 May 2026, 15:53 UTC · CWE-459 · Incomplete Cleanup

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