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

iommufd: Protect against overflow of ALIGN() during iova allocation

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.

15 package states
Repository candidate not checked

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

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.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 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-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 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-42638

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: iommufd: Protect against overflow of ALIGN() during iova allocation Userspace can supply an iova and uptr such that the target iova alignment becomes really big and ALIGN() overflows which corrupts the selected area range during allocation. CONFIG_IOMMUFD_TEST can detect this: WARNING: CPU: 1 PID: 5092 at drivers/iommu/iommufd/io_pagetable.c:268 iopt_alloc_area_pages drivers/iommu/iommufd/io_pagetable.c:268 [inline] WARNING: CPU: 1 PID: 5092 at drivers/iommu/iommufd/io_pagetable.c:268 iopt_map_pages+0xf95/0x1050 drivers/iommu/iommufd/io_pagetable.c:352 Modules linked in: CPU: 1 PID: 5092 Comm: syz-executor294 Not tainted 6.10.0-rc5-syzkaller-00294-g3ffea9a7a6f7 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024 RIP: 0010:iopt_alloc_area_pages drivers/iommu/iommufd/io_pagetable.c:268 [inline] RIP: 0010:iopt_map_pages+0xf95/0x1050 drivers/iommu/iommufd/io_pagetable.c:352 Code: fc e9 a4 f3 ff ff e8 1a 8b 4c fc 41 be e4 ff ff ff e9 8a f3 ff ff e8 0a 8b 4c fc 90 0f 0b 90 e9 37 f5 ff ff e8 fc 8a 4c fc 90 <0f> 0b 90 e9 68 f3 ff ff 48 c7 c1 ec 82 ad 8f 80 e1 07 80 c1 03 38 RSP: 0018:ffffc90003ebf9e0 EFLAGS: 00010293 RAX: ffffffff85499fa4 RBX: 00000000ffffffef RCX: ffff888079b49e00 RDX: 0000000000000000 RSI: 00000000ffffffef RDI: 0000000000000000 RBP: ffffc90003ebfc50 R08: ffffffff85499b30 R09: ffffffff85499942 R10: 0000000000000002 R11: ffff888079b49e00 R12: ffff8880228e0010 R13: 0000000000000000 R14: 1ffff920007d7f68 R15: ffffc90003ebfd00 FS: 000055557d760380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000005fdeb8 CR3: 000000007404a000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> iommufd_ioas_copy+0x610/0x7b0 drivers/iommu/iommufd/ioas.c:274 iommufd_fops_ioctl+0x4d9/0x5a0 drivers/iommu/iommufd/main.c:421 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Cap the automatic alignment to the huge page size, which is probably a better idea overall. Huge automatic alignments can fragment and chew up the available IOVA space without any reason.

What

In the Linux kernel, the following vulnerability has been resolved: iommufd: Protect against overflow of ALIGN() during iova allocation Userspace can supply an iova and uptr such that the target iova alignment becomes really big and ALIGN() overflows which corrupts the selected area range during allocation. CONFIG_IOMMUFD_TEST can detect this: WARNING: CPU: 1 PID: 5092 at drivers/iommu/iommufd/io_pagetable.c:268 iopt_alloc_area_pages drivers/iommu/iommufd/io_pagetable.c:268 [inline] WARNING: CPU: 1 PID: 5092 at drivers/iommu/iommufd/io_pagetable.c:268 iopt_map_pages+0xf95/0x1050 drivers/iommu/iommufd/io_pagetable.c:352 Modules linked in: CPU: 1 PID: 5092 Comm: syz-executor294 Not tainted 6.10.0-rc5-syzkaller-00294-g3ffea9a7a6f7 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024 RIP: 0010:iopt_alloc_area_pages drivers/iommu/iommufd/io_pagetable.c:268 [inline] RIP: 0010:iopt_map_pages+0xf95/0x1050 drivers/iommu/iommufd/io_pagetable.c:352 Code: fc e9 a4 f3 ff ff e8 1a 8b 4c fc 41 be e4 ff ff ff e9 8a f3 ff ff e8 0a 8b 4c fc 90 0f 0b 90 e9 37 f5 ff ff e8 fc 8a 4c fc 90 <0f> 0b 90 e9 68 f3 ff ff 48 c7 c1 ec 82 ad 8f 80 e1 07 80 c1 03 38 RSP: 0018:ffffc90003ebf9e0 EFLAGS: 00010293 RAX: ffffffff85499fa4 RBX: 00000000ffffffef RCX: ffff888079b49e00 RDX: 0000000000000000 RSI: 00000000ffffffef RDI: 0000000000000000 RBP: ffffc90003ebfc50 R08: ffffffff85499b30 R09: ffffffff85499942 R10: 0000000000000002 R11: ffff888079b49e00 R12: ffff8880228e0010 R13: 0000000000000000 R14: 1ffff920007d7f68 R15: ffffc90003ebfd00 FS: 000055557d760380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000005fdeb8 CR3: 000000007404a000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> iommufd_ioas_copy+0x610/0x7b0 drivers/iommu/iommufd/ioas.c:274 iommufd_fops_ioctl+0x4d9/0x5a0 drivers/iommu/iommufd/main.c:421 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Cap the automatic alignment to the huge page size, which is probably a better idea overall. Huge automatic alignments can fragment and chew up the available IOVA space without any reason.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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: iommufd: Protect against overflow of ALIGN() during iova allocation Userspace can supply an iova and uptr such that the target iova alignment becomes really big and ALIGN() overflows which corrupts the selected area range during allocation. CONFIG_IOMMUFD_TEST can detect this: WARNING: CPU: 1 PID: 5092 at drivers/iommu/iommufd/io_pagetable.c:268 iopt_alloc_area_pages drivers/iommu/iommufd/io_pagetable.c:268 [inline] WARNING: CPU: 1 PID: 5092 at drivers/iommu/iommufd/io_pagetable.c:268 iopt_map_pages+0xf95/0x1050 drivers/iommu/iommufd/io_pagetable.c:352 Modules linked in: CPU: 1 PID: 5092 Comm: syz-executor294 Not tainted 6.10.0-rc5-syzkaller-00294-g3ffea9a7a6f7 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024 RIP: 0010:iopt_alloc_area_pages drivers/iommu/iommufd/io_pagetable.c:268 [inline] RIP: 0010:iopt_map_pages+0xf95/0x1050 drivers/iommu/iommufd/io_pagetable.c:352 Code: fc e9 a4 f3 ff ff e8 1a 8b 4c fc 41 be e4 ff ff ff e9 8a f3 ff ff e8 0a 8b 4c fc 90 0f 0b 90 e9 37 f5 ff ff e8 fc 8a 4c fc 90 <0f> 0b 90 e9 68 f3 ff ff 48 c7 c1 ec 82 ad 8f 80 e1 07 80 c1 03 38 RSP: 0018:ffffc90003ebf9e0 EFLAGS: 00010293 RAX: ffffffff85499fa4 RBX: 00000000ffffffef RCX: ffff888079b49e00 RDX: 0000000000000000 RSI: 00000000ffffffef RDI: 0000000000000000 RBP: ffffc90003ebfc50 R08: ffffffff85499b30 R09: ffffffff85499942 R10: 0000000000000002 R11: ffff888079b49e00 R12: ffff8880228e0010 R13: 0000000000000000 R14: 1ffff920007d7f68 R15: ffffc90003ebfd00 FS: 000055557d760380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000005fdeb8 CR3: 000000007404a000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> iommufd_ioas_copy+0x610/0x7b0 drivers/iommu/iommufd/ioas.c:274 iommufd_fops_ioctl+0x4d9/0x5a0 drivers/iommu/iommufd/main.c:421 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Cap the automatic alignment to the huge page size, which is probably a better idea overall. Huge automatic alignments can fragment and chew up the available IOVA space without any reason.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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 → Out-of-bounds Write → 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-787

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

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

Official authority intelligence

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

BSI · German · WID-SEC-W-2025-2855IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand zu verursachen oder andere, nicht spezifizierte Angriffe durchzuführen.

Official advisory
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-1057Multiples vulnérabilités dans les produits VMware

rd?id=CVE-2024-4741 Référence CVE CVE-2024-47672 https://www.cve.org/CVERecord?id=CVE-2024-47672 Référence CVE CVE-2024-47675 https://www.cve.org/CVERecord?id=CVE-2024-47675 Référence CVE CVE-2024-47682 https://www.cve.org/CVERecord?id=CVE-2024-47682 Référence CVE CVE-2024-47687 https://www.cve.org/CVERecord?id=CVE-2024-47687 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47700 https://www.cve.org/CVERecord?id=CVE-2024-47700 Référence CVE CVE-2024-47702 https://www.cve.org/CVERecord?id=CVE-2024-47702 Référence CVE CVE-2024-47715 https://www.cve.org/CVERecord?id=CVE-2024-47715 Référence CVE CVE-2024-47719 https://www.cve.org/CVERecord?id=CVE-2024-47719 Référence CVE CVE-2024-47727 https://www.cve.org/CVERecord?id=CVE-2024-47727 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48876 https://www.cve.org/CVERecord?id=CVE-2024-48876 Référence CVE CVE-2024-49855 https://www.cve.org/CVERecord?id=CVE-2024-49855 Référence CVE CVE-2024-49856 https://www.cve.org/CVERecord?id=CVE-2024-49856 Référence CVE CVE-2024-49862 https://www.cve.org/CVERecord?id=CVE-2024-49862 Référence CVE CVE-2024-49864 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-47709 Référence CVE CVE-2024-47710 https://www.cve.org/CVERecord?id=CVE-2024-47710 Référence CVE CVE-2024-47711 https://www.cve.org/CVERecord?id=CVE-2024-47711 Référence CVE CVE-2024-47712 https://www.cve.org/CVERecord?id=CVE-2024-47712 Référence CVE CVE-2024-47713 https://www.cve.org/CVERecord?id=CVE-2024-47713 Référence CVE CVE-2024-47714 https://www.cve.org/CVERecord?id=CVE-2024-47714 Référence CVE CVE-2024-47715 https://www.cve.org/CVERecord?id=CVE-2024-47715 Référence CVE CVE-2024-47716 https://www.cve.org/CVERecord?id=CVE-2024-47716 Référence CVE CVE-2024-47718 https://www.cve.org/CVERecord?id=CVE-2024-47718 Référence CVE CVE-2024-47719 https://www.cve.org/CVERecord?id=CVE-2024-47719 Référence CVE CVE-2024-47720 https://www.cve.org/CVERecord?id=CVE-2024-47720 Référence CVE CVE-2024-47723 https://www.cve.org/CVERecord?id=CVE-2024-47723 Référence CVE CVE-2024-47726 https://www.cve.org/CVERecord?id=CVE-2024-47726 Référence CVE CVE-2024-47727 https://www.cve.org/CVERecord?id=CVE-2024-47727 Référence CVE CVE-2024-47728 https://www.cve.org/CVERecord?id=CVE-2024-47728 Référence CVE CVE-2024-47730 https://www.cve.org/CVERecord?id=CVE-2024-47730 Référence CVE CVE-2024-47731 https://www.cve.org/CVERecord?id=CVE-2024-47731 Référence CVE CVE-2024-47732 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-47710 Référence CVE CVE-2024-47711 https://www.cve.org/CVERecord?id=CVE-2024-47711 Référence CVE CVE-2024-47712 https://www.cve.org/CVERecord?id=CVE-2024-47712 Référence CVE CVE-2024-47713 https://www.cve.org/CVERecord?id=CVE-2024-47713 Référence CVE CVE-2024-47714 https://www.cve.org/CVERecord?id=CVE-2024-47714 Référence CVE CVE-2024-47715 https://www.cve.org/CVERecord?id=CVE-2024-47715 Référence CVE CVE-2024-47716 https://www.cve.org/CVERecord?id=CVE-2024-47716 Référence CVE CVE-2024-47717 https://www.cve.org/CVERecord?id=CVE-2024-47717 Référence CVE CVE-2024-47718 https://www.cve.org/CVERecord?id=CVE-2024-47718 Référence CVE CVE-2024-47719 https://www.cve.org/CVERecord?id=CVE-2024-47719 Référence CVE CVE-2024-47720 https://www.cve.org/CVERecord?id=CVE-2024-47720 Référence CVE CVE-2024-47721 https://www.cve.org/CVERecord?id=CVE-2024-47721 Référence CVE CVE-2024-47723 https://www.cve.org/CVERecord?id=CVE-2024-47723 Référence CVE CVE-2024-47724 https://www.cve.org/CVERecord?id=CVE-2024-47724 Référence CVE CVE-2024-47726 https://www.cve.org/CVERecord?id=CVE-2024-47726 Référence CVE CVE-2024-47727 https://www.cve.org/CVERecord?id=CVE-2024-47727 Référence CVE CVE-2024-47728 https://www.cve.org/CVERecord?id=CVE-2024-47728 Référence CVE CVE-2024-47730 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-47707 Référence CVE CVE-2024-47709 https://www.cve.org/CVERecord?id=CVE-2024-47709 Référence CVE CVE-2024-47710 https://www.cve.org/CVERecord?id=CVE-2024-47710 Référence CVE CVE-2024-47712 https://www.cve.org/CVERecord?id=CVE-2024-47712 Référence CVE CVE-2024-47713 https://www.cve.org/CVERecord?id=CVE-2024-47713 Référence CVE CVE-2024-47714 https://www.cve.org/CVERecord?id=CVE-2024-47714 Référence CVE CVE-2024-47715 https://www.cve.org/CVERecord?id=CVE-2024-47715 Référence CVE CVE-2024-47716 https://www.cve.org/CVERecord?id=CVE-2024-47716 Référence CVE CVE-2024-47718 https://www.cve.org/CVERecord?id=CVE-2024-47718 Référence CVE CVE-2024-47719 https://www.cve.org/CVERecord?id=CVE-2024-47719 Référence CVE CVE-2024-47720 https://www.cve.org/CVERecord?id=CVE-2024-47720 Référence CVE CVE-2024-47723 https://www.cve.org/CVERecord?id=CVE-2024-47723 Référence CVE CVE-2024-47727 https://www.cve.org/CVERecord?id=CVE-2024-47727 Référence CVE CVE-2024-47728 https://www.cve.org/CVERecord?id=CVE-2024-47728 Référence CVE CVE-2024-47730 https://www.cve.org/CVERecord?id=CVE-2024-47730 Référence CVE CVE-2024-47731 https://www.cve.org/CVERecord?id=CVE-2024-47731 Référence CVE CVE-2024-47732 https://www.cve.org/CVERecord?id=CVE-2024-47732 Référence CVE CVE-2024-47733 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-47710 Référence CVE CVE-2024-47711 https://www.cve.org/CVERecord?id=CVE-2024-47711 Référence CVE CVE-2024-47712 https://www.cve.org/CVERecord?id=CVE-2024-47712 Référence CVE CVE-2024-47713 https://www.cve.org/CVERecord?id=CVE-2024-47713 Référence CVE CVE-2024-47714 https://www.cve.org/CVERecord?id=CVE-2024-47714 Référence CVE CVE-2024-47715 https://www.cve.org/CVERecord?id=CVE-2024-47715 Référence CVE CVE-2024-47716 https://www.cve.org/CVERecord?id=CVE-2024-47716 Référence CVE CVE-2024-47717 https://www.cve.org/CVERecord?id=CVE-2024-47717 Référence CVE CVE-2024-47718 https://www.cve.org/CVERecord?id=CVE-2024-47718 Référence CVE CVE-2024-47719 https://www.cve.org/CVERecord?id=CVE-2024-47719 Référence CVE CVE-2024-47720 https://www.cve.org/CVERecord?id=CVE-2024-47720 Référence CVE CVE-2024-47721 https://www.cve.org/CVERecord?id=CVE-2024-47721 Référence CVE CVE-2024-47723 https://www.cve.org/CVERecord?id=CVE-2024-47723 Référence CVE CVE-2024-47724 https://www.cve.org/CVERecord?id=CVE-2024-47724 Référence CVE CVE-2024-47726 https://www.cve.org/CVERecord?id=CVE-2024-47726 Référence CVE CVE-2024-47727 https://www.cve.org/CVERecord?id=CVE-2024-47727 Référence CVE CVE-2024-47728 https://www.cve.org/CVERecord?id=CVE-2024-47728 Référence CVE CVE-2024-47730 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-47706 Référence CVE CVE-2024-47707 https://www.cve.org/CVERecord?id=CVE-2024-47707 Référence CVE CVE-2024-47709 https://www.cve.org/CVERecord?id=CVE-2024-47709 Référence CVE CVE-2024-47710 https://www.cve.org/CVERecord?id=CVE-2024-47710 Référence CVE CVE-2024-47712 https://www.cve.org/CVERecord?id=CVE-2024-47712 Référence CVE CVE-2024-47713 https://www.cve.org/CVERecord?id=CVE-2024-47713 Référence CVE CVE-2024-47714 https://www.cve.org/CVERecord?id=CVE-2024-47714 Référence CVE CVE-2024-47715 https://www.cve.org/CVERecord?id=CVE-2024-47715 Référence CVE CVE-2024-47718 https://www.cve.org/CVERecord?id=CVE-2024-47718 Référence CVE CVE-2024-47719 https://www.cve.org/CVERecord?id=CVE-2024-47719 Référence CVE CVE-2024-47720 https://www.cve.org/CVERecord?id=CVE-2024-47720 Référence CVE CVE-2024-47723 https://www.cve.org/CVERecord?id=CVE-2024-47723 Référence CVE CVE-2024-47727 https://www.cve.org/CVERecord?id=CVE-2024-47727 Référence CVE CVE-2024-47728 https://www.cve.org/CVERecord?id=CVE-2024-47728 Référence CVE CVE-2024-47730 https://www.cve.org/CVERecord?id=CVE-2024-47730 Référence CVE CVE-2024-47731 https://www.cve.org/CVERecord?id=CVE-2024-47731 Référence CVE CVE-2024-47732 https://www.cve.org/CVERecord?id=CVE-2024-47732 Référence CVE CVE-2024-47735 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-47706 Référence CVE CVE-2024-47707 https://www.cve.org/CVERecord?id=CVE-2024-47707 Référence CVE CVE-2024-47709 https://www.cve.org/CVERecord?id=CVE-2024-47709 Référence CVE CVE-2024-47710 https://www.cve.org/CVERecord?id=CVE-2024-47710 Référence CVE CVE-2024-47712 https://www.cve.org/CVERecord?id=CVE-2024-47712 Référence CVE CVE-2024-47713 https://www.cve.org/CVERecord?id=CVE-2024-47713 Référence CVE CVE-2024-47714 https://www.cve.org/CVERecord?id=CVE-2024-47714 Référence CVE CVE-2024-47715 https://www.cve.org/CVERecord?id=CVE-2024-47715 Référence CVE CVE-2024-47718 https://www.cve.org/CVERecord?id=CVE-2024-47718 Référence CVE CVE-2024-47719 https://www.cve.org/CVERecord?id=CVE-2024-47719 Référence CVE CVE-2024-47720 https://www.cve.org/CVERecord?id=CVE-2024-47720 Référence CVE CVE-2024-47723 https://www.cve.org/CVERecord?id=CVE-2024-47723 Référence CVE CVE-2024-47727 https://www.cve.org/CVERecord?id=CVE-2024-47727 Référence CVE CVE-2024-47728 https://www.cve.org/CVERecord?id=CVE-2024-47728 Référence CVE CVE-2024-47730 https://www.cve.org/CVERecord?id=CVE-2024-47730 Référence CVE CVE-2024-47731 https://www.cve.org/CVERecord?id=CVE-2024-47731 Référence CVE CVE-2024-47732 https://www.cve.org/CVERecord?id=CVE-2024-47732 Référence CVE CVE-2024-47735 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
51fe6141f0f64ae0bbc096a41a07572273e8c0ef < cd6dd564ae7d99967ef50078216929418160b30e; 51fe6141f0f64ae0bbc096a41a07572273e8c0ef < a6e9f9fd14772c0b23c6d1d7002d98f9d27cb1f6; 51fe6141f0f64ae0bbc096a41a07572273e8c0ef < 72b78287ce92802e8ba678181a34b84ae844a112; 51fe6141f0f64ae0bbc096a41a07572273e8c0ef < 8f6887349b2f829a4121c518aeb064fc922714e4; 6.2
Fixed
< 6.2; 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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 21 Oct 2024 · Last source change 11 May 2026, 20:39 UTC · CWE-787 · Out-of-bounds Write

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-42638
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD enriched

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