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

bpf: Remove tst_run from lwt_seg6local_prog_ops.

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Within 7 days

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

Patch available
Distribution package intelligence

Ubuntu vendor package status

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

15 package states
Repository candidate not checked

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

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

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2024-42015

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf: Remove tst_run from lwt_seg6local_prog_ops. The syzbot reported that the lwt_seg6 related BPF ops can be invoked via bpf_test_run() without without entering input_action_end_bpf() first. Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL probably didn't work since it was introduced in commit 04d4b274e2a ("ipv6: sr: Add seg6local action End.BPF"). The reason is that the per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self test case but each BPF function expects it. Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.

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
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

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

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: bpf: Remove tst_run from lwt_seg6local_prog_ops. The syzbot reported that the lwt_seg6 related BPF ops can be invoked via bpf_test_run() without without entering input_action_end_bpf() first. Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL probably didn't work since it was introduced in commit 04d4b274e2a ("ipv6: sr: Add seg6local action End.BPF"). The reason is that the per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self test case but each BPF function expects it. Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Remove tst_run from lwt_seg6local_prog_ops. The syzbot reported that the lwt_seg6 related BPF ops can be invoked via bpf_test_run() without without entering input_action_end_bpf() first. Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL probably didn't work since it was introduced in commit 04d4b274e2a ("ipv6: sr: Add seg6local action End.BPF"). The reason is that the per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self test case but each BPF function expects it. Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.

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: bpf: Remove tst_run from lwt_seg6local_prog_ops. The syzbot reported that the lwt_seg6 related BPF ops can be invoked via bpf_test_run() without without entering input_action_end_bpf() first. Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL probably didn't work since it was introduced in commit 04d4b274e2a ("ipv6: sr: Add seg6local action End.BPF"). The reason is that the per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self test case but each BPF function expects it. Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.

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.

ENISA EUVD · EUVD-2024-42015Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf: Remove tst_run from lwt_seg6local_prog_ops. The syzbot reported that the lwt_seg6 related BPF ops can be invoked via bpf_test_run() without without entering input_action_end_bpf() first. Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL probably didn't work since it was introduced in commit 04d4b274e2a ("ipv6: sr: Add seg6local action End.BPF"). The reason is that the per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self test case but each BPF function expects it. Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.

Official EUVD record
BSI · German · WID-SEC-W-2024-2173Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen unspezifischen Angriff durchzuführen.

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

d?id=CVE-2024-46720 Référence CVE CVE-2024-46726 https://www.cve.org/CVERecord?id=CVE-2024-46726 Référence CVE CVE-2024-46727 https://www.cve.org/CVERecord?id=CVE-2024-46727 Référence CVE CVE-2024-46728 https://www.cve.org/CVERecord?id=CVE-2024-46728 Référence CVE CVE-2024-46729 https://www.cve.org/CVERecord?id=CVE-2024-46729 Référence CVE CVE-2024-46730 https://www.cve.org/CVERecord?id=CVE-2024-46730 Référence CVE CVE-2024-46733 https://www.cve.org/CVERecord?id=CVE-2024-46733 Référence CVE CVE-2024-46748 https://www.cve.org/CVERecord?id=CVE-2024-46748 Référence CVE CVE-2024-46749 https://www.cve.org/CVERecord?id=CVE-2024-46749 Référence CVE CVE-2024-46754 https://www.cve.org/CVERecord?id=CVE-2024-46754 Référence CVE CVE-2024-46762 https://www.cve.org/CVERecord?id=CVE-2024-46762 Référence CVE CVE-2024-46765 https://www.cve.org/CVERecord?id=CVE-2024-46765 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-46775 https://www.cve.org/CVERecord?id=CVE-2024-46775 Référence CVE CVE-2024-46802 https://www.cve.org/CVERecord?id=CVE-2024-46802 Référence CVE CVE-2024-46803 https://www.cve.org/CVERecord?id=CVE-2024-46803 Référence CVE CVE-2024-46806 https://www.cve.org/CVERecord?id=CVE-2024-46806 Référence CVE CVE-2024-46808 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46720 Référence CVE CVE-2024-46726 https://www.cve.org/CVERecord?id=CVE-2024-46726 Référence CVE CVE-2024-46727 https://www.cve.org/CVERecord?id=CVE-2024-46727 Référence CVE CVE-2024-46728 https://www.cve.org/CVERecord?id=CVE-2024-46728 Référence CVE CVE-2024-46729 https://www.cve.org/CVERecord?id=CVE-2024-46729 Référence CVE CVE-2024-46730 https://www.cve.org/CVERecord?id=CVE-2024-46730 Référence CVE CVE-2024-46733 https://www.cve.org/CVERecord?id=CVE-2024-46733 Référence CVE CVE-2024-46748 https://www.cve.org/CVERecord?id=CVE-2024-46748 Référence CVE CVE-2024-46749 https://www.cve.org/CVERecord?id=CVE-2024-46749 Référence CVE CVE-2024-46754 https://www.cve.org/CVERecord?id=CVE-2024-46754 Référence CVE CVE-2024-46762 https://www.cve.org/CVERecord?id=CVE-2024-46762 Référence CVE CVE-2024-46765 https://www.cve.org/CVERecord?id=CVE-2024-46765 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-46775 https://www.cve.org/CVERecord?id=CVE-2024-46775 Référence CVE CVE-2024-46802 https://www.cve.org/CVERecord?id=CVE-2024-46802 Référence CVE CVE-2024-46803 https://www.cve.org/CVERecord?id=CVE-2024-46803 Référence CVE CVE-2024-46806 https://www.cve.org/CVERecord?id=CVE-2024-46806 Référence CVE CVE-2024-46808 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-46744 Référence CVE CVE-2024-46745 https://www.cve.org/CVERecord?id=CVE-2024-46745 Référence CVE CVE-2024-46746 https://www.cve.org/CVERecord?id=CVE-2024-46746 Référence CVE CVE-2024-46747 https://www.cve.org/CVERecord?id=CVE-2024-46747 Référence CVE CVE-2024-46749 https://www.cve.org/CVERecord?id=CVE-2024-46749 Référence CVE CVE-2024-46750 https://www.cve.org/CVERecord?id=CVE-2024-46750 Référence CVE CVE-2024-46751 https://www.cve.org/CVERecord?id=CVE-2024-46751 Référence CVE CVE-2024-46752 https://www.cve.org/CVERecord?id=CVE-2024-46752 Référence CVE CVE-2024-46753 https://www.cve.org/CVERecord?id=CVE-2024-46753 Référence CVE CVE-2024-46754 https://www.cve.org/CVERecord?id=CVE-2024-46754 Référence CVE CVE-2024-46755 https://www.cve.org/CVERecord?id=CVE-2024-46755 Référence CVE CVE-2024-46756 https://www.cve.org/CVERecord?id=CVE-2024-46756 Référence CVE CVE-2024-46757 https://www.cve.org/CVERecord?id=CVE-2024-46757 Référence CVE CVE-2024-46758 https://www.cve.org/CVERecord?id=CVE-2024-46758 Référence CVE CVE-2024-46759 https://www.cve.org/CVERecord?id=CVE-2024-46759 Référence CVE CVE-2024-46760 https://www.cve.org/CVERecord?id=CVE-2024-46760 Référence CVE CVE-2024-46761 https://www.cve.org/CVERecord?id=CVE-2024-46761 Référence CVE CVE-2024-46762 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-44995 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45025 https://www.cve.org/CVERecord?id=CVE-2024-45025 Référence CVE CVE-2024-46678 https://www.cve.org/CVERecord?id=CVE-2024-46678 Référence CVE CVE-2024-46680 https://www.cve.org/CVERecord?id=CVE-2024-46680 Référence CVE CVE-2024-46681 https://www.cve.org/CVERecord?id=CVE-2024-46681 Référence CVE CVE-2024-46716 https://www.cve.org/CVERecord?id=CVE-2024-46716 Référence CVE CVE-2024-46719 https://www.cve.org/CVERecord?id=CVE-2024-46719 Référence CVE CVE-2024-46721 https://www.cve.org/CVERecord?id=CVE-2024-46721 Référence CVE CVE-2024-46754 https://www.cve.org/CVERecord?id=CVE-2024-46754 Référence CVE CVE-2024-46765 https://www.cve.org/CVERecord?id=CVE-2024-46765 Référence CVE CVE-2024-46766 https://www.cve.org/CVERecord?id=CVE-2024-46766 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46775 https://www.cve.org/CVERecord?id=CVE-2024-46775 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46788 https://www.cve.org/CVERecord?id=CVE-2024-46788 Référence CVE CVE-2024-46797 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46744 Référence CVE CVE-2024-46745 https://www.cve.org/CVERecord?id=CVE-2024-46745 Référence CVE CVE-2024-46746 https://www.cve.org/CVERecord?id=CVE-2024-46746 Référence CVE CVE-2024-46747 https://www.cve.org/CVERecord?id=CVE-2024-46747 Référence CVE CVE-2024-46749 https://www.cve.org/CVERecord?id=CVE-2024-46749 Référence CVE CVE-2024-46750 https://www.cve.org/CVERecord?id=CVE-2024-46750 Référence CVE CVE-2024-46751 https://www.cve.org/CVERecord?id=CVE-2024-46751 Référence CVE CVE-2024-46752 https://www.cve.org/CVERecord?id=CVE-2024-46752 Référence CVE CVE-2024-46753 https://www.cve.org/CVERecord?id=CVE-2024-46753 Référence CVE CVE-2024-46754 https://www.cve.org/CVERecord?id=CVE-2024-46754 Référence CVE CVE-2024-46755 https://www.cve.org/CVERecord?id=CVE-2024-46755 Référence CVE CVE-2024-46756 https://www.cve.org/CVERecord?id=CVE-2024-46756 Référence CVE CVE-2024-46757 https://www.cve.org/CVERecord?id=CVE-2024-46757 Référence CVE CVE-2024-46758 https://www.cve.org/CVERecord?id=CVE-2024-46758 Référence CVE CVE-2024-46759 https://www.cve.org/CVERecord?id=CVE-2024-46759 Référence CVE CVE-2024-46760 https://www.cve.org/CVERecord?id=CVE-2024-46760 Référence CVE CVE-2024-46761 https://www.cve.org/CVERecord?id=CVE-2024-46761 Référence CVE CVE-2024-46762 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-44947 Référence CVE CVE-2024-44958 https://www.cve.org/CVERecord?id=CVE-2024-44958 Référence CVE CVE-2024-44964 https://www.cve.org/CVERecord?id=CVE-2024-44964 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45025 https://www.cve.org/CVERecord?id=CVE-2024-45025 Référence CVE CVE-2024-46678 https://www.cve.org/CVERecord?id=CVE-2024-46678 Référence CVE CVE-2024-46716 https://www.cve.org/CVERecord?id=CVE-2024-46716 Référence CVE CVE-2024-46719 https://www.cve.org/CVERecord?id=CVE-2024-46719 Référence CVE CVE-2024-46721 https://www.cve.org/CVERecord?id=CVE-2024-46721 Référence CVE CVE-2024-46754 https://www.cve.org/CVERecord?id=CVE-2024-46754 Référence CVE CVE-2024-46766 https://www.cve.org/CVERecord?id=CVE-2024-46766 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-46775 https://www.cve.org/CVERecord?id=CVE-2024-46775 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46797 https://www.cve.org/CVERecord?id=CVE-2024-46797 Référence CVE CVE-2024-46802 https://www.cve.org/CVERecord?id=CVE-2024-46802 Référence CVE CVE-2024-46803 https://www.cve.org/CVERecord?id=CVE-2024-46803 Référence CVE CVE-2024-46804 https://www.cve.org/CVERecord?id=

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
004d4b274e2a1a895a0e5dc66158b90a7d463d44 < ea3fae6984ba0f054550e4da22219489c12cd8d4; 004d4b274e2a1a895a0e5dc66158b90a7d463d44 < a675524cfbe88fd49c05ff8807a08646983e687c; 004d4b274e2a1a895a0e5dc66158b90a7d463d44 < b05c2e25a5c168dbb46b6f7fcb741fd4e4f3b54a; 004d4b274e2a1a895a0e5dc66158b90a7d463d44 < e217492f6fa2228ad703ee3006d8fc4e5969fbd4; 004d4b274e2a1a895a0e5dc66158b90a7d463d44 < 9cd15511de7c619bbd0f54bb3f28e6e720ded5d6; 004d4b274e2a1a895a0e5dc66158b90a7d463d44 < c13fda93aca118b8e5cd202e339046728ee7dddb; 4.18
Fixed
< 4.18; 5.10.269 ≤ 5.10.*; 5.15.220 ≤ 5.15.*; 6.1.187 ≤ 6.1.*; 6.6.156 ≤ 6.6.*; 6.10.10 ≤ 6.10.*; 6.11 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 18 Sept 2024 · Last source change 2 Sept 2026, 12:49 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-42015
Product sourceCNA
Remediation sourceCVE/CNA references
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 →
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    004d4b274e2a1a895a0e5dc66158b90a7d463d44 < 9cd15511de7c619bbd0f54bb3f28e6e720ded5d6; 004d4b274e2a1a895a0e5dc66158b90a7d463d44 < c13fda93aca118b8e5cd202e339046728ee7dddb; 4.18 · Fixed: < 4.18; 6.10.10 ≤ 6.10.*; 6.11 ≤ *
    After
    004d4b274e2a1a895a0e5dc66158b90a7d463d44 < ea3fae6984ba0f054550e4da22219489c12cd8d4; 004d4b274e2a1a895a0e5dc66158b90a7d463d44 < a675524cfbe88fd49c05ff8807a08646983e687c; 004d4b274e2a1a895a0e5dc66158b90a7d463d44 < b05c2e25a5c168dbb46b6f7fcb741fd4e4f3b54a; 004d4b274e2a1a895a0e5dc66158b90a7d463d44 < e217492f6fa2228ad703ee3006d8fc4e5969fbd4; 004d4b274e2a1a895a0e5dc66158b90a7d463d44 < 9cd15511de7c619bbd0f54bb3f28e6e720ded5d6; 004d4b274e2a1a895a0e5dc66158b90a7d463d44 < c13fda93aca118b8e5cd202e339046728ee7dddb; 4.18 · Fixed: < 4.18; 5.10.269 ≤ 5.10.*; 5.15.220 ≤ 5.15.*; 6.1.187 ≤ 6.1.*; 6.6.156 ≤ 6.6.*; 6.10.10 ≤ 6.10.*; 6.11 ≤ *
    CNA ↗
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-42015↗Patch or update reference↗Patch or update reference↗CVE authority or vendor 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-46754 · cve.blacktree.nl