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

RDMA/mlx5: Move events notifier registration to be after device registration

Linux · Linux

8.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 20 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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.33% 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: Within 30 daysRemediation target: Within 180 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 20 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.

23 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 20 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.12.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.3-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-nvidia-tegraAffected, 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-raspi-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-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-53224 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: RDMA/mlx5: Move events notifier registration to be after device registration
112 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel's mlx5 InfiniBand driver. This flaw allows a local user to cause a Denial of Service (DoS) by triggering a system crash. A race condition between device deregistration and background event handling can cause tasks to execute after the hardware device has been unregistered, resulting in a null-pointer dereference and kernel panic.
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-51896

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 20 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: RDMA/mlx5: Move events notifier registration to be after device registration Move pkey change work initialization and cleanup from device resources stage to notifier stage, since this is the stage which handles this work events. Fix a race between the device deregistration and pkey change work by moving MLX5_IB_STAGE_DEVICE_NOTIFIER to be after MLX5_IB_STAGE_IB_REG in order to ensure that the notifier is deregistered before the device during cleanup. Which ensures there are no works that are being executed after the device has already unregistered which can cause the panic below. BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 630071 Comm: kworker/1:2 Kdump: loaded Tainted: G W OE --------- --- 5.14.0-162.6.1.el9_1.x86_64 #1 Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 02/27/2023 Workqueue: events pkey_change_handler [mlx5_ib] RIP: 0010:setup_qp+0x38/0x1f0 [mlx5_ib] Code: ee 41 54 45 31 e4 55 89 f5 53 48 89 fb 48 83 ec 20 8b 77 08 65 48 8b 04 25 28 00 00 00 48 89 44 24 18 48 8b 07 48 8d 4c 24 16 <4c> 8b 38 49 8b 87 80 0b 00 00 4c 89 ff 48 8b 80 08 05 00 00 8b 40 RSP: 0018:ffffbcc54068be20 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff954054494128 RCX: ffffbcc54068be36 RDX: ffff954004934000 RSI: 0000000000000001 RDI: ffff954054494128 RBP: 0000000000000023 R08: ffff954001be2c20 R09: 0000000000000001 R10: ffff954001be2c20 R11: ffff9540260133c0 R12: 0000000000000000 R13: 0000000000000023 R14: 0000000000000000 R15: ffff9540ffcb0905 FS: 0000000000000000(0000) GS:ffff9540ffc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 000000010625c001 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: mlx5_ib_gsi_pkey_change+0x20/0x40 [mlx5_ib] process_one_work+0x1e8/0x3c0 worker_thread+0x50/0x3b0 ? rescuer_thread+0x380/0x380 kthread+0x149/0x170 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x22/0x30 Modules linked in: rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) mlx5_fwctl(OE) fwctl(OE) ib_uverbs(OE) mlx5_core(OE) mlxdevm(OE) ib_core(OE) mlx_compat(OE) psample mlxfw(OE) tls knem(OE) netconsole nfsv3 nfs_acl nfs lockd grace fscache netfs qrtr rfkill sunrpc intel_rapl_msr intel_rapl_common rapl hv_balloon hv_utils i2c_piix4 pcspkr joydev fuse ext4 mbcache jbd2 sr_mod sd_mod cdrom t10_pi sg ata_generic pci_hyperv pci_hyperv_intf hyperv_drm drm_shmem_helper drm_kms_helper hv_storvsc syscopyarea hv_netvsc sysfillrect sysimgblt hid_hyperv fb_sys_fops scsi_transport_fc hyperv_keyboard drm ata_piix crct10dif_pclmul crc32_pclmul crc32c_intel libata ghash_clmulni_intel hv_vmbus serio_raw [last unloaded: ib_core] CR2: 0000000000000000 ---[ end trace f6f8be4eae12f7bc ]---

What

In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Move events notifier registration to be after device registration Move pkey change work initialization and cleanup from device resources stage to notifier stage, since this is the stage which handles this work events. Fix a race between the device deregistration and pkey change work by moving MLX5_IB_STAGE_DEVICE_NOTIFIER to be after MLX5_IB_STAGE_IB_REG in order to ensure that the notifier is deregistered before the device during cleanup. Which ensures there are no works that are being executed after the device has already unregistered which can cause the panic below. BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 630071 Comm: kworker/1:2 Kdump: loaded Tainted: G W OE --------- --- 5.14.0-162.6.1.el9_1.x86_64 #1 Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 02/27/2023 Workqueue: events pkey_change_handler [mlx5_ib] RIP: 0010:setup_qp+0x38/0x1f0 [mlx5_ib] Code: ee 41 54 45 31 e4 55 89 f5 53 48 89 fb 48 83 ec 20 8b 77 08 65 48 8b 04 25 28 00 00 00 48 89 44 24 18 48 8b 07 48 8d 4c 24 16 <4c> 8b 38 49 8b 87 80 0b 00 00 4c 89 ff 48 8b 80 08 05 00 00 8b 40 RSP: 0018:ffffbcc54068be20 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff954054494128 RCX: ffffbcc54068be36 RDX: ffff954004934000 RSI: 0000000000000001 RDI: ffff954054494128 RBP: 0000000000000023 R08: ffff954001be2c20 R09: 0000000000000001 R10: ffff954001be2c20 R11: ffff9540260133c0 R12: 0000000000000000 R13: 0000000000000023 R14: 0000000000000000 R15: ffff9540ffcb0905 FS: 0000000000000000(0000) GS:ffff9540ffc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 000000010625c001 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: mlx5_ib_gsi_pkey_change+0x20/0x40 [mlx5_ib] process_one_work+0x1e8/0x3c0 worker_thread+0x50/0x3b0 ? rescuer_thread+0x380/0x380 kthread+0x149/0x170 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x22/0x30 Modules linked in: rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) mlx5_fwctl(OE) fwctl(OE) ib_uverbs(OE) mlx5_core(OE) mlxdevm(OE) ib_core(OE) mlx_compat(OE) psample mlxfw(OE) tls knem(OE) netconsole nfsv3 nfs_acl nfs lockd grace fscache netfs qrtr rfkill sunrpc intel_rapl_msr intel_rapl_common rapl hv_balloon hv_utils i2c_piix4 pcspkr joydev fuse ext4 mbcache jbd2 sr_mod sd_mod cdrom t10_pi sg ata_generic pci_hyperv pci_hyperv_intf hyperv_drm drm_shmem_helper drm_kms_helper hv_storvsc syscopyarea hv_netvsc sysfillrect sysimgblt hid_hyperv fb_sys_fops scsi_transport_fc hyperv_keyboard drm ata_piix crct10dif_pclmul crc32_pclmul crc32c_intel libata ghash_clmulni_intel hv_vmbus serio_raw [last unloaded: ib_core] CR2: 0000000000000000 ---[ end trace f6f8be4eae12f7bc ]---

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. 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: RDMA/mlx5: Move events notifier registration to be after device registration Move pkey change work initialization and cleanup from device resources stage to notifier stage, since this is the stage which handles this work events. Fix a race between the device deregistration and pkey change work by moving MLX5_IB_STAGE_DEVICE_NOTIFIER to be after MLX5_IB_STAGE_IB_REG in order to ensure that the notifier is deregistered before the device during cleanup. Which ensures there are no works that are being executed after the device has already unregistered which can cause the panic below. BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 630071 Comm: kworker/1:2 Kdump: loaded Tainted: G W OE --------- --- 5.14.0-162.6.1.el9_1.x86_64 #1 Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 02/27/2023 Workqueue: events pkey_change_handler [mlx5_ib] RIP: 0010:setup_qp+0x38/0x1f0 [mlx5_ib] Code: ee 41 54 45 31 e4 55 89 f5 53 48 89 fb 48 83 ec 20 8b 77 08 65 48 8b 04 25 28 00 00 00 48 89 44 24 18 48 8b 07 48 8d 4c 24 16 <4c> 8b 38 49 8b 87 80 0b 00 00 4c 89 ff 48 8b 80 08 05 00 00 8b 40 RSP: 0018:ffffbcc54068be20 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff954054494128 RCX: ffffbcc54068be36 RDX: ffff954004934000 RSI: 0000000000000001 RDI: ffff954054494128 RBP: 0000000000000023 R08: ffff954001be2c20 R09: 0000000000000001 R10: ffff954001be2c20 R11: ffff9540260133c0 R12: 0000000000000000 R13: 0000000000000023 R14: 0000000000000000 R15: ffff9540ffcb0905 FS: 0000000000000000(0000) GS:ffff9540ffc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 000000010625c001 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: mlx5_ib_gsi_pkey_change+0x20/0x40 [mlx5_ib] process_one_work+0x1e8/0x3c0 worker_thread+0x50/0x3b0 ? rescuer_thread+0x380/0x380 kthread+0x149/0x170 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x22/0x30 Modules linked in: rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) mlx5_fwctl(OE) fwctl(OE) ib_uverbs(OE) mlx5_core(OE) mlxdevm(OE) ib_core(OE) mlx_compat(OE) psample mlxfw(OE) tls knem(OE) netconsole nfsv3 nfs_acl nfs lockd grace fscache netfs qrtr rfkill sunrpc intel_rapl_msr intel_rapl_common rapl hv_balloon hv_utils i2c_piix4 pcspkr joydev fuse ext4 mbcache jbd2 sr_mod sd_mod cdrom t10_pi sg ata_generic pci_hyperv pci_hyperv_intf hyperv_drm drm_shmem_helper drm_kms_helper hv_storvsc syscopyarea hv_netvsc sysfillrect sysimgblt hid_hyperv fb_sys_fops scsi_transport_fc hyperv_keyboard drm ata_piix crct10dif_pclmul crc32_pclmul crc32c_intel libata ghash_clmulni_intel hv_vmbus serio_raw [last unloaded: ib_core] CR2: 0000000000000000 ---[ end trace f6f8be4eae12f7bc ]---

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. 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
an adjacent network → NULL Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Adjacent
Privileges required
None: unauthenticated exploitation is possible
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-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
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.
UnauthenticatedCWE-476
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-3762Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250101Security Bulletin 01 Jan 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 01 Jan 2025, published on 1 January 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2024-53187 Référence CVE CVE-2024-53190 https://www.cve.org/CVERecord?id=CVE-2024-53190 Référence CVE CVE-2024-53195 https://www.cve.org/CVERecord?id=CVE-2024-53195 Référence CVE CVE-2024-53196 https://www.cve.org/CVERecord?id=CVE-2024-53196 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53216 https://www.cve.org/CVERecord?id=CVE-2024-53216 Référence CVE CVE-2024-53219 https://www.cve.org/CVERecord?id=CVE-2024-53219 Référence CVE CVE-2024-53220 https://www.cve.org/CVERecord?id=CVE-2024-53220 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53234 https://www.cve.org/CVERecord?id=CVE-2024-53234 Référence CVE CVE-2024-53240 https://www.cve.org/CVERecord?id=CVE-2024-53240 Référence CVE CVE-2024-53241 https://www.cve.org/CVERecord?id=CVE-2024-53241 Référence CVE CVE-2024-53687 https://www.cve.org/CVERecord?id=CVE-2024-53687 Référence CVE CVE-2024-54456 https://www.cve.org/CVERecord?id=CVE-2024-54456 Référence CVE CVE-2024-54683 https://www.cve.org/CVERecord?id=CVE-2024-54683 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-5569 https://www.cve.org/CVERecord?id=CVE

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

d?id=CVE-2024-53187 Référence CVE CVE-2024-53190 https://www.cve.org/CVERecord?id=CVE-2024-53190 Référence CVE CVE-2024-53195 https://www.cve.org/CVERecord?id=CVE-2024-53195 Référence CVE CVE-2024-53196 https://www.cve.org/CVERecord?id=CVE-2024-53196 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53216 https://www.cve.org/CVERecord?id=CVE-2024-53216 Référence CVE CVE-2024-53219 https://www.cve.org/CVERecord?id=CVE-2024-53219 Référence CVE CVE-2024-53220 https://www.cve.org/CVERecord?id=CVE-2024-53220 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53234 https://www.cve.org/CVERecord?id=CVE-2024-53234 Référence CVE CVE-2024-53240 https://www.cve.org/CVERecord?id=CVE-2024-53240 Référence CVE CVE-2024-53241 https://www.cve.org/CVERecord?id=CVE-2024-53241 Référence CVE CVE-2024-53687 https://www.cve.org/CVERecord?id=CVE-2024-53687 Référence CVE CVE-2024-54456 https://www.cve.org/CVERecord?id=CVE-2024-54456 Référence CVE CVE-2024-54683 https://www.cve.org/CVERecord?id=CVE-2024-54683 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-5569 https://www.cve.org/CVERecord?id=CVE

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

d?id=CVE-2024-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53218 https://www.cve.org/CVERecord?id=CVE-2024-53218 Référence CVE CVE-2024-53219 https://www.cve.org/CVERecord?id=CVE-2024-53219 Référence CVE CVE-2024-53220 https://www.cve.org/CVERecord?id=CVE-2024-53220 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-53222 https://www.cve.org/CVERecord?id=CVE-2024-53222 Référence CVE CVE-2024-53223 https://www.cve.org/CVERecord?id=CVE-2024-53223 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53226 https://www.cve.org/CVERecord?id=CVE-2024-53226 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53228 https://www.cve.org/CVERecord?id=CVE-2024-53228 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53230 https://www.cve.org/CVERecord?id=CVE-2024-53230 Référence CVE CVE-2024-53231 https://www.cve.org/CVERecord?id=CVE-2024-53231 Référence CVE CVE-2024-53232 https://www.cve.org/CVERecord?id=CVE-2024-53232 Référence CVE CVE-2024-53233 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53218 https://www.cve.org/CVERecord?id=CVE-2024-53218 Référence CVE CVE-2024-53219 https://www.cve.org/CVERecord?id=CVE-2024-53219 Référence CVE CVE-2024-53220 https://www.cve.org/CVERecord?id=CVE-2024-53220 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-53222 https://www.cve.org/CVERecord?id=CVE-2024-53222 Référence CVE CVE-2024-53223 https://www.cve.org/CVERecord?id=CVE-2024-53223 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53226 https://www.cve.org/CVERecord?id=CVE-2024-53226 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53228 https://www.cve.org/CVERecord?id=CVE-2024-53228 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53230 https://www.cve.org/CVERecord?id=CVE-2024-53230 Référence CVE CVE-2024-53231 https://www.cve.org/CVERecord?id=CVE-2024-53231 Référence CVE CVE-2024-53232 https://www.cve.org/CVERecord?id=CVE-2024-53232 Référence CVE CVE-2024-53233 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53179 Référence CVE CVE-2024-53206 https://www.cve.org/CVERecord?id=CVE-2024-53206 Référence CVE CVE-2024-53208 https://www.cve.org/CVERecord?id=CVE-2024-53208 Référence CVE CVE-2024-53209 https://www.cve.org/CVERecord?id=CVE-2024-53209 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53213 https://www.cve.org/CVERecord?id=CVE-2024-53213 Référence CVE CVE-2024-53214 https://www.cve.org/CVERecord?id=CVE-2024-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53226 https://www.cve.org/CVERecord?id=CVE-2024-53226 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=CVE-2024-53239 Référence CVE CVE-2024-53240 https://www.cve.org/CVERecord?id=CVE-2024-53240 Référence CVE CVE-2024-53241 https://www.cve.org/CVERecord?id=CVE-2024-53241 Référence CVE CVE-2024-53690 https://www.cve.org/CVERecord?id=CVE-2024-53690 Référence CVE CVE-2024-54680 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-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53216 https://www.cve.org/CVERecord?id=CVE-2024-53216 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53218 https://www.cve.org/CVERecord?id=CVE-2024-53218 Référence CVE CVE-2024-53219 https://www.cve.org/CVERecord?id=CVE-2024-53219 Référence CVE CVE-2024-53220 https://www.cve.org/CVERecord?id=CVE-2024-53220 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-53223 https://www.cve.org/CVERecord?id=CVE-2024-53223 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53226 https://www.cve.org/CVERecord?id=CVE-2024-53226 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53228 https://www.cve.org/CVERecord?id=CVE-2024-53228 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53230 https://www.cve.org/CVERecord?id=CVE-2024-53230 Référence CVE CVE-2024-53231 https://www.cve.org/CVERecord?id=CVE-2024-53231 Référence CVE CVE-2024-53232 https://www.cve.org/CVERecord?id=CVE-2024-53232 Référence CVE CVE-2024-53233 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-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53216 https://www.cve.org/CVERecord?id=CVE-2024-53216 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53218 https://www.cve.org/CVERecord?id=CVE-2024-53218 Référence CVE CVE-2024-53219 https://www.cve.org/CVERecord?id=CVE-2024-53219 Référence CVE CVE-2024-53220 https://www.cve.org/CVERecord?id=CVE-2024-53220 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-53223 https://www.cve.org/CVERecord?id=CVE-2024-53223 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53226 https://www.cve.org/CVERecord?id=CVE-2024-53226 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53228 https://www.cve.org/CVERecord?id=CVE-2024-53228 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53230 https://www.cve.org/CVERecord?id=CVE-2024-53230 Référence CVE CVE-2024-53231 https://www.cve.org/CVERecord?id=CVE-2024-53231 Référence CVE CVE-2024-53232 https://www.cve.org/CVERecord?id=CVE-2024-53232 Référence CVE CVE-2024-53233 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53195 Référence CVE CVE-2024-53196 https://www.cve.org/CVERecord?id=CVE-2024-53196 Référence CVE CVE-2024-53197 https://www.cve.org/CVERecord?id=CVE-2024-53197 Référence CVE CVE-2024-53198 https://www.cve.org/CVERecord?id=CVE-2024-53198 Référence CVE CVE-2024-53203 https://www.cve.org/CVERecord?id=CVE-2024-53203 Référence CVE CVE-2024-53208 https://www.cve.org/CVERecord?id=CVE-2024-53208 Référence CVE CVE-2024-53209 https://www.cve.org/CVERecord?id=CVE-2024-53209 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53230 https://www.cve.org/CVERecord?id=CVE-2024-53230 Référence CVE CVE-2024-53231 https://www.cve.org/CVERecord?id=CVE-2024-53231 Référence CVE CVE-2024-53232 https://www.cve.org/CVERecord?id=CVE-2024-53232 Référence CVE CVE-2024-53233 https://www.cve.org/CVERecord?id=CVE-2024-53233 Référence CVE CVE-2024-53236 https://www.cve.org/CVERecord?id=CVE-2024-53236 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53208 Référence CVE CVE-2024-53209 https://www.cve.org/CVERecord?id=CVE-2024-53209 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53213 https://www.cve.org/CVERecord?id=CVE-2024-53213 Référence CVE CVE-2024-53214 https://www.cve.org/CVERecord?id=CVE-2024-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53216 https://www.cve.org/CVERecord?id=CVE-2024-53216 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53222 https://www.cve.org/CVERecord?id=CVE-2024-53222 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53230 https://www.cve.org/CVERecord?id=CVE-2024-53230 Référence CVE CVE-2024-53231 https://www.cve.org/CVERecord?id=CVE-2024-53231 Référence CVE CVE-2024-53232 https://www.cve.org/CVERecord?id=CVE-2024-53232 Référence CVE CVE-2024-53233 https://www.cve.org/CVERecord?id=CVE-2024-53233 Référence CVE CVE-2024-53234 https://www.cve.org/CVERecord?id=CVE-2024-53234 Référence CVE CVE-2024-53236 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53208 Référence CVE CVE-2024-53209 https://www.cve.org/CVERecord?id=CVE-2024-53209 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53213 https://www.cve.org/CVERecord?id=CVE-2024-53213 Référence CVE CVE-2024-53214 https://www.cve.org/CVERecord?id=CVE-2024-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53216 https://www.cve.org/CVERecord?id=CVE-2024-53216 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53222 https://www.cve.org/CVERecord?id=CVE-2024-53222 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53234 https://www.cve.org/CVERecord?id=CVE-2024-53234 Référence CVE CVE-2024-53237 https://www.cve.org/CVERecord?id=CVE-2024-53237 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=CVE-2024-53239 Référence CVE CVE-2024-53240 https://www.cve.org/CVERecord?id=CVE-2024-53240 Référence CVE CVE-2024-53241 https://www.cve.org/CVERecord?id=CVE-2024-53241 Référence CVE CVE-2024-56536 https://www.cve.org/CVERecord?id=CVE-2024-56536 Référence CVE CVE-2024-56539 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53208 Référence CVE CVE-2024-53209 https://www.cve.org/CVERecord?id=CVE-2024-53209 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53213 https://www.cve.org/CVERecord?id=CVE-2024-53213 Référence CVE CVE-2024-53214 https://www.cve.org/CVERecord?id=CVE-2024-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53216 https://www.cve.org/CVERecord?id=CVE-2024-53216 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53222 https://www.cve.org/CVERecord?id=CVE-2024-53222 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53234 https://www.cve.org/CVERecord?id=CVE-2024-53234 Référence CVE CVE-2024-53237 https://www.cve.org/CVERecord?id=CVE-2024-53237 Référence CVE CVE-2024-53240 https://www.cve.org/CVERecord?id=CVE-2024-53240 Référence CVE CVE-2024-53241 https://www.cve.org/CVERecord?id=CVE-2024-53241 Référence CVE CVE-2024-56536 https://www.cve.org/CVERecord?id=CVE-2024-56536 Référence CVE CVE-2024-56539 https://www.cve.org/CVERecord?id=CVE-2024-56539 Référence CVE CVE-2024-56549 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-018000Linux の Linux Kernel における NULL ポインタデリファレンスに関する脆弱性

Linux の Linux Kernel には、NULL ポインタデリファレンスに関する脆弱性が存在します。

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 27 Dec 2024 · Last source change 5 Aug 2026, 11:44 UTC · CWE-476 · NULL Pointer Dereference

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

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

Material change intelligence

What changed after publication

View recent updates ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-51896↗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-53224 · cve.blacktree.nl