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

platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 17 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.24% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 17 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

21 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.115-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

1 current
CVE-2024-49886 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug
70 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 8
  • kernel as a component of Red Hat Enterprise Linux 8
  • kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8
  • kernel-core as a component of Red Hat Enterprise Linux 8
  • kernel-cross-headers as a component of Red Hat Enterprise Linux 8
  • kernel-debug as a component of Red Hat Enterprise Linux 8
  • kernel-debug-core as a component of Red Hat Enterprise Linux 8
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8
Summary
A flaw was found in the Linux kernel. A local attacker with privileges to manage virtual machines could exploit this vulnerability by attaching a specific Intel Speed Select Technology (ISST) PCI device to a virtual machine. This action triggers a memory error known as a slab-out-of-bounds, which can cause the system to crash. The primary consequence of this flaw is a denial of service, making the system unavailable.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
Optional official sources

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

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2024-43586

No EUVD known-exploited evidence

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

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 17 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug Attaching SST PCI device to VM causes "BUG: KASAN: slab-out-of-bounds". kasan report: [ 19.411889] ================================================================== [ 19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [ 19.417368] [ 19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G E 6.9.0 #10 [ 19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [ 19.422687] Call Trace: [ 19.424091] <TASK> [ 19.425448] dump_stack_lvl+0x5d/0x80 [ 19.426963] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.428694] print_report+0x19d/0x52e [ 19.430206] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 19.431837] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.433539] kasan_report+0xf0/0x170 [ 19.435019] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.436709] _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.438379] ? __pfx_sched_clock_cpu+0x10/0x10 [ 19.439910] isst_if_cpu_online+0x406/0x58f [isst_if_common] [ 19.441573] ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [ 19.443263] ? ttwu_queue_wakelist+0x2c1/0x360 [ 19.444797] cpuhp_invoke_callback+0x221/0xec0 [ 19.446337] cpuhp_thread_fun+0x21b/0x610 [ 19.447814] ? __pfx_cpuhp_thread_fun+0x10/0x10 [ 19.449354] smpboot_thread_fn+0x2e7/0x6e0 [ 19.450859] ? __pfx_smpboot_thread_fn+0x10/0x10 [ 19.452405] kthread+0x29c/0x350 [ 19.453817] ? __pfx_kthread+0x10/0x10 [ 19.455253] ret_from_fork+0x31/0x70 [ 19.456685] ? __pfx_kthread+0x10/0x10 [ 19.458114] ret_from_fork_asm+0x1a/0x30 [ 19.459573] </TASK> [ 19.460853] [ 19.462055] Allocated by task 1198: [ 19.463410] kasan_save_stack+0x30/0x50 [ 19.464788] kasan_save_track+0x14/0x30 [ 19.466139] __kasan_kmalloc+0xaa/0xb0 [ 19.467465] __kmalloc+0x1cd/0x470 [ 19.468748] isst_if_cdev_register+0x1da/0x350 [isst_if_common] [ 19.470233] isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [ 19.471670] do_one_initcall+0xa4/0x380 [ 19.472903] do_init_module+0x238/0x760 [ 19.474105] load_module+0x5239/0x6f00 [ 19.475285] init_module_from_file+0xd1/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.478920] do_syscall_64+0x82/0x160 [ 19.480036] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 19.481292] [ 19.482205] The buggy address belongs to the object at ffff888829e65000 which belongs to the cache kmalloc-512 of size 512 [ 19.484818] The buggy address is located 0 bytes to the right of allocated 512-byte region [ffff888829e65000, ffff888829e65200) [ 19.487447] [ 19.488328] The buggy address belongs to the physical page: [ 19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [ 19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [ 19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [ 19.493914] page_type: 0xffffffff() [ 19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [ 19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [ 19.503784] page dumped because: k ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug Attaching SST PCI device to VM causes "BUG: KASAN: slab-out-of-bounds". kasan report: [ 19.411889] ================================================================== [ 19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [ 19.417368] [ 19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G E 6.9.0 #10 [ 19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [ 19.422687] Call Trace: [ 19.424091] <TASK> [ 19.425448] dump_stack_lvl+0x5d/0x80 [ 19.426963] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.428694] print_report+0x19d/0x52e [ 19.430206] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 19.431837] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.433539] kasan_report+0xf0/0x170 [ 19.435019] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.436709] _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.438379] ? __pfx_sched_clock_cpu+0x10/0x10 [ 19.439910] isst_if_cpu_online+0x406/0x58f [isst_if_common] [ 19.441573] ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [ 19.443263] ? ttwu_queue_wakelist+0x2c1/0x360 [ 19.444797] cpuhp_invoke_callback+0x221/0xec0 [ 19.446337] cpuhp_thread_fun+0x21b/0x610 [ 19.447814] ? __pfx_cpuhp_thread_fun+0x10/0x10 [ 19.449354] smpboot_thread_fn+0x2e7/0x6e0 [ 19.450859] ? __pfx_smpboot_thread_fn+0x10/0x10 [ 19.452405] kthread+0x29c/0x350 [ 19.453817] ? __pfx_kthread+0x10/0x10 [ 19.455253] ret_from_fork+0x31/0x70 [ 19.456685] ? __pfx_kthread+0x10/0x10 [ 19.458114] ret_from_fork_asm+0x1a/0x30 [ 19.459573] </TASK> [ 19.460853] [ 19.462055] Allocated by task 1198: [ 19.463410] kasan_save_stack+0x30/0x50 [ 19.464788] kasan_save_track+0x14/0x30 [ 19.466139] __kasan_kmalloc+0xaa/0xb0 [ 19.467465] __kmalloc+0x1cd/0x470 [ 19.468748] isst_if_cdev_register+0x1da/0x350 [isst_if_common] [ 19.470233] isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [ 19.471670] do_one_initcall+0xa4/0x380 [ 19.472903] do_init_module+0x238/0x760 [ 19.474105] load_module+0x5239/0x6f00 [ 19.475285] init_module_from_file+0xd1/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.478920] do_syscall_64+0x82/0x160 [ 19.480036] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 19.481292] [ 19.482205] The buggy address belongs to the object at ffff888829e65000 which belongs to the cache kmalloc-512 of size 512 [ 19.484818] The buggy address is located 0 bytes to the right of allocated 512-byte region [ffff888829e65000, ffff888829e65200) [ 19.487447] [ 19.488328] The buggy address belongs to the physical page: [ 19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [ 19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [ 19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [ 19.493914] page_type: 0xffffffff() [ 19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [ 19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [ 19.503784] page dumped because: k ---truncated---

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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: platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug Attaching SST PCI device to VM causes "BUG: KASAN: slab-out-of-bounds". kasan report: [ 19.411889] ================================================================== [ 19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [ 19.417368] [ 19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G E 6.9.0 #10 [ 19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [ 19.422687] Call Trace: [ 19.424091] <TASK> [ 19.425448] dump_stack_lvl+0x5d/0x80 [ 19.426963] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.428694] print_report+0x19d/0x52e [ 19.430206] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 19.431837] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.433539] kasan_report+0xf0/0x170 [ 19.435019] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.436709] _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.438379] ? __pfx_sched_clock_cpu+0x10/0x10 [ 19.439910] isst_if_cpu_online+0x406/0x58f [isst_if_common] [ 19.441573] ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [ 19.443263] ? ttwu_queue_wakelist+0x2c1/0x360 [ 19.444797] cpuhp_invoke_callback+0x221/0xec0 [ 19.446337] cpuhp_thread_fun+0x21b/0x610 [ 19.447814] ? __pfx_cpuhp_thread_fun+0x10/0x10 [ 19.449354] smpboot_thread_fn+0x2e7/0x6e0 [ 19.450859] ? __pfx_smpboot_thread_fn+0x10/0x10 [ 19.452405] kthread+0x29c/0x350 [ 19.453817] ? __pfx_kthread+0x10/0x10 [ 19.455253] ret_from_fork+0x31/0x70 [ 19.456685] ? __pfx_kthread+0x10/0x10 [ 19.458114] ret_from_fork_asm+0x1a/0x30 [ 19.459573] </TASK> [ 19.460853] [ 19.462055] Allocated by task 1198: [ 19.463410] kasan_save_stack+0x30/0x50 [ 19.464788] kasan_save_track+0x14/0x30 [ 19.466139] __kasan_kmalloc+0xaa/0xb0 [ 19.467465] __kmalloc+0x1cd/0x470 [ 19.468748] isst_if_cdev_register+0x1da/0x350 [isst_if_common] [ 19.470233] isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [ 19.471670] do_one_initcall+0xa4/0x380 [ 19.472903] do_init_module+0x238/0x760 [ 19.474105] load_module+0x5239/0x6f00 [ 19.475285] init_module_from_file+0xd1/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.478920] do_syscall_64+0x82/0x160 [ 19.480036] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 19.481292] [ 19.482205] The buggy address belongs to the object at ffff888829e65000 which belongs to the cache kmalloc-512 of size 512 [ 19.484818] The buggy address is located 0 bytes to the right of allocated 512-byte region [ffff888829e65000, ffff888829e65200) [ 19.487447] [ 19.488328] The buggy address belongs to the physical page: [ 19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [ 19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [ 19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [ 19.493914] page_type: 0xffffffff() [ 19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [ 19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [ 19.503784] page dumped because: k ---truncated---

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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 → vulnerable operation → 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.
CWE not yet assigned
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.
A

Official authority intelligence

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

BSI · German · WID-SEC-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-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 ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241023Security Bulletin 23 Oct 2024

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

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

d?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=CVE-2024-49864 Référence CVE CVE-2024-49866 https://www.cve.org/CVERecord?id=CVE-2024-49866 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49885 https://www.cve.org/CVERecord?id=CVE-2024-49885 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49946 https://www.cve.org/CVERecord?id=CVE-2024-49946 Référence CVE CVE-2024-49951 https://www.cve.org/CVERecord?id=CVE-2024-49951 Référence CVE CVE-2024-49953 https://www.cve.org/CVERecord?id=CVE-2024-49953 Référence CVE CVE-2024-49976 https://www.cve.org/CVERecord?id=CVE-2024-49976 Référence CVE CVE-2024-49977 https://www.cve.org/CVERecord?id=CVE-2024-49977 Référence CVE CVE-2024-49999 https://www.cve.org/CVERecord?id=CVE-2024-49999 Référence CVE CVE-2024-50000 https://www.cve.org/CVERecord?id=CVE-2024-50000 Référence CVE CVE-2024-50019 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49893 https://www.cve.org/CVERecord?id=CVE-2024-49893 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 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-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49885 https://www.cve.org/CVERecord?id=CVE-2024-49885 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49893 https://www.cve.org/CVERecord?id=CVE-2024-49893 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 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-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49885 https://www.cve.org/CVERecord?id=CVE-2024-49885 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49887 https://www.cve.org/CVERecord?id=CVE-2024-49887 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 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-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49885 https://www.cve.org/CVERecord?id=CVE-2024-49885 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 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-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49885 https://www.cve.org/CVERecord?id=CVE-2024-49885 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49887 https://www.cve.org/CVERecord?id=CVE-2024-49887 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49893 https://www.cve.org/CVERecord?id=CVE-2024-49893 Référence CVE CVE-2024-49894 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-49871 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=CVE-2024-49896 Référence CVE CVE-2024-49900 https://www.cve.org/CVERecord?id=CVE-2024-49900 Référence CVE CVE-2024-49902 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-49871 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=CVE-2024-49896 Référence CVE CVE-2024-49900 https://www.cve.org/CVERecord?id=CVE-2024-49900 Référence CVE CVE-2024-49902 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-49871 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=CVE-2024-49896 Référence CVE CVE-2024-49900 https://www.cve.org/CVERecord?id=CVE-2024-49900 Référence CVE CVE-2024-49902 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-49871 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=CVE-2024-49896 Référence CVE CVE-2024-49900 https://www.cve.org/CVERecord?id=CVE-2024-49900 Référence CVE CVE-2024-49902 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-49871 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49889 https://www.cve.org/CVERecord?id=CVE-2024-49889 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49893 https://www.cve.org/CVERecord?id=CVE-2024-49893 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=CVE-2024-49896 Référence CVE CVE-2024-49897 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-49874 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=CVE-2024-49896 Référence CVE CVE-2024-49897 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-49871 Référence CVE CVE-2024-49874 https://www.cve.org/CVERecord?id=CVE-2024-49874 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=CVE-2024-49883 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49890 https://www.cve.org/CVERecord?id=CVE-2024-49890 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49892 https://www.cve.org/CVERecord?id=CVE-2024-49892 Référence CVE CVE-2024-49894 https://www.cve.org/CVERecord?id=CVE-2024-49894 Référence CVE CVE-2024-49895 https://www.cve.org/CVERecord?id=CVE-2024-49895 Référence CVE CVE-2024-49896 https://www.cve.org/CVERecord?id=CVE-2024-49896 Référence CVE CVE-2024-49897 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-012592Linux の Linux Kernel における脆弱性

Linux の Linux Kernel には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 21 Oct 2024 · Last source change 5 Aug 2026, 11:40 UTC · CWE not yet assigned

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-43586
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

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

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