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

bpf: Prevent tail call between progs attached to different hooks

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 208 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 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.23% 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 208 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 19 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 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.135-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-1Debian Security Tracker ↗Source updated 5 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.

2 current
CVE-2024-50063 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: bpf: Prevent tail call between progs attached to different hooks
184 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 7
  • kernel as a component of Red Hat Enterprise Linux 7
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 7
  • kernel-debug as a component of Red Hat Enterprise Linux 7
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 7
  • kernel-devel as a component of Red Hat Enterprise Linux 7
  • kernel-doc as a component of Red Hat Enterprise Linux 7
  • kernel-headers as a component of Red Hat Enterprise Linux 7
  • kernel-kdump as a component of Red Hat Enterprise Linux 7
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 7
  • kernel-rt as a component of Red Hat Enterprise Linux 7
Summary
A flaw was found in the Linux kernel's Berkeley Packet Filter (BPF) subsystem. A privileged local attacker could exploit this by crafting BPF programs that improperly use "tail calls" to switch between different kernel function hooks. This bypasses critical security checks related to BPF program context or return values, potentially leading to information disclosure or privilege escalation.
Remediation
To mitigate this issue, ensure that unprivileged eBPF usage is disabled. This can be achieved by setting the `kernel.unprivileged_bpf_disabled` sysctl to 1. To check the current status: `cat /proc/sys/kernel/unprivileged_bpf_disabled` To disable unprivileged eBPF usage for the current session: `echo 1 > /proc/sys/kernel/unprivileged_bpf_disabled` To make this change persistent across reboots, create a file named `/etc/sysctl.d/99-disable-unprivileged-bpf.conf` with the following content: `kernel.unprivileged_bpf_disabled = 1` Then, apply the changes: `sysctl --system`
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Prevent tail call between progs attached to different hooks bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed. For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2's prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed. Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2's return value 1 will be used as the return value for prog1's hook file_alloc_security. That is, the return value rule is bypassed. This patch adds restriction for tail call to prevent such bypasses.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-44785

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf: Prevent tail call between progs attached to different hooks bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed. For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2's prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed. Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2's return value 1 will be used as the return value for prog1's hook file_alloc_security. That is, the return value rule is bypassed. This patch adds restriction for tail call to prevent such bypasses.

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 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 208 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: bpf: Prevent tail call between progs attached to different hooks bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed. For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2's prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed. Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2's return value 1 will be used as the return value for prog1's hook file_alloc_security. That is, the return value rule is bypassed. This patch adds restriction for tail call to prevent such bypasses.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Prevent tail call between progs attached to different hooks bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed. For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2's prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed. Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2's return value 1 will be used as the return value for prog1's hook file_alloc_security. That is, the return value rule is bypassed. This patch adds restriction for tail call to prevent such bypasses.

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: Prevent tail call between progs attached to different hooks bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed. For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2's prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed. Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2's return value 1 will be used as the return value for prog1's hook file_alloc_security. That is, the return value rule is bypassed. This patch adds restriction for tail call to prevent such bypasses.

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-44785Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf: Prevent tail call between progs attached to different hooks bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed. For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2's prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed. Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2's return value 1 will be used as the return value for prog1's hook file_alloc_security. That is, the return value rule is bypassed. This patch adds restriction for tail call to prevent such bypasses.

Official EUVD record ↗
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-2026-AVI-0880Multiples vulnérabilités dans les produits Siemens

nement de la politique de sécurité Déni de service à distance Exécution de code arbitraire à distance Non spécifié par l'éditeur Élévation de privilèges Systèmes affectés Desigo CC toutes versions Desigo CC toutes versions pour la vulnérabilité CVE-2025-15467 Desigo CC versions antérieures à 9.0.1 SIMATIC S7-1500 versions supérieures ou égales à 3.1.6 pour les vulnérabilités CVE-2021-41617, CVE-2023-28531, CVE-2023-51384, CVE-2023-52927, CVE-2024-26783, CVE-2024-27056, CVE-2024-28956, CVE-2024-36903, CVE-2024-36927, CVE-2024-42079, CVE-2024-46786, CVE-2024-47736, CVE-2024-47809, CVE-2024-49968, CVE-2024-49994, CVE-2024-49998, CVE-2024-50014, CVE-2024-50063, CVE-2024-50164, CVE-2024-50298, CVE-2024-53124, CVE-2024-53170, CVE-2024-54458, CVE-2024-56631, CVE-2024-56703, CVE-2024-56719, CVE-2024-57917, CVE-2024-57924, CVE-2024-57973, CVE-2024-57977, CVE-2024-57979, CVE-2024-58011, CVE-2024-58016, CVE-2024-58020, CVE-2024-58056, CVE-2024-58058, CVE-2024-58061, CVE-2024-58086, CVE-2025-21645, CVE-2025-21648, CVE-2025-21655, CVE-2025-21676, CVE-2025-21682, CVE-2025-21702, CVE-2025-21705, CVE-2025-21706, CVE-2025-21707, CVE-2025-21718, CVE-2025-21731, CVE-2025-21745, CVE-2025-21758, CVE-2025-21760, CVE-2025-21764, CVE-2025-21765, CVE-2025-21780, CVE-2025-21795, CVE-2025-21796, CVE-2025-21802, CVE-2025

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

d?id=CVE-2024-50012 Référence CVE CVE-2024-50014 https://www.cve.org/CVERecord?id=CVE-2024-50014 Référence CVE CVE-2024-50017 https://www.cve.org/CVERecord?id=CVE-2024-50017 Référence CVE CVE-2024-50028 https://www.cve.org/CVERecord?id=CVE-2024-50028 Référence CVE CVE-2024-50034 https://www.cve.org/CVERecord?id=CVE-2024-50034 Référence CVE CVE-2024-50048 https://www.cve.org/CVERecord?id=CVE-2024-50048 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50098 https://www.cve.org/CVERecord?id=CVE-2024-50098 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-50112 https://www.cve.org/CVERecord?id=CVE-2024-50112 Référence CVE CVE-2024-50135 https://www.cve.org/CVERecord?id=CVE-2024-50135 Référence CVE CVE-2024-50138 https://www.cve.org/CVERecord?id=CVE-2024-50138 Référence CVE CVE-2024-50146 https://www.cve.org/CVERecord?id=CVE-2024-50146 Référence CVE CVE-2024-50164 https://www.cve.org/CVERecord?id=CVE-2024-50164 Référence CVE CVE-2024-50166 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-50012 Référence CVE CVE-2024-50014 https://www.cve.org/CVERecord?id=CVE-2024-50014 Référence CVE CVE-2024-50017 https://www.cve.org/CVERecord?id=CVE-2024-50017 Référence CVE CVE-2024-50028 https://www.cve.org/CVERecord?id=CVE-2024-50028 Référence CVE CVE-2024-50034 https://www.cve.org/CVERecord?id=CVE-2024-50034 Référence CVE CVE-2024-50048 https://www.cve.org/CVERecord?id=CVE-2024-50048 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50098 https://www.cve.org/CVERecord?id=CVE-2024-50098 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-50112 https://www.cve.org/CVERecord?id=CVE-2024-50112 Référence CVE CVE-2024-50135 https://www.cve.org/CVERecord?id=CVE-2024-50135 Référence CVE CVE-2024-50138 https://www.cve.org/CVERecord?id=CVE-2024-50138 Référence CVE CVE-2024-50146 https://www.cve.org/CVERecord?id=CVE-2024-50146 Référence CVE CVE-2024-50164 https://www.cve.org/CVERecord?id=CVE-2024-50164 Référence CVE CVE-2024-50166 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46821 Référence CVE CVE-2024-46823 https://www.cve.org/CVERecord?id=CVE-2024-46823 Référence CVE CVE-2024-47726 https://www.cve.org/CVERecord?id=CVE-2024-47726 Référence CVE CVE-2024-47730 https://www.cve.org/CVERecord?id=CVE-2024-47730 Référence CVE CVE-2024-47753 https://www.cve.org/CVERecord?id=CVE-2024-47753 Référence CVE CVE-2024-47754 https://www.cve.org/CVERecord?id=CVE-2024-47754 Référence CVE CVE-2024-49960 https://www.cve.org/CVERecord?id=CVE-2024-49960 Référence CVE CVE-2024-50047 https://www.cve.org/CVERecord?id=CVE-2024-50047 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50154 https://www.cve.org/CVERecord?id=CVE-2024-50154 Référence CVE CVE-2024-50246 https://www.cve.org/CVERecord?id=CVE-2024-50246 Référence CVE CVE-2024-50280 https://www.cve.org/CVERecord?id=CVE-2024-50280 Référence CVE CVE-2024-53144 https://www.cve.org/CVERecord?id=CVE-2024-53144 Référence CVE CVE-2024-53166 https://www.cve.org/CVERecord?id=CVE-2024-53166 Référence CVE CVE-2024-54458 https://www.cve.org/CVERecord?id=CVE-2024-54458 Référence CVE CVE-2024-56599 https://www.cve.org/CVERecord?id=CVE-2024-56599 Référence CVE CVE-2024-56608 https://www.cve.org/CVERecord?id=

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

/2025/msg00069.html Référence CVE CVE-2023-53034 https://www.cve.org/CVERecord?id=CVE-2023-53034 Référence CVE CVE-2024-36908 https://www.cve.org/CVERecord?id=CVE-2024-36908 Référence CVE CVE-2024-46733 https://www.cve.org/CVERecord?id=CVE-2024-46733 Référence CVE CVE-2024-46742 https://www.cve.org/CVERecord?id=CVE-2024-46742 Référence CVE CVE-2024-46753 https://www.cve.org/CVERecord?id=CVE-2024-46753 Référence CVE CVE-2024-46774 https://www.cve.org/CVERecord?id=CVE-2024-46774 Référence CVE CVE-2024-46816 https://www.cve.org/CVERecord?id=CVE-2024-46816 Référence CVE CVE-2024-46823 https://www.cve.org/CVERecord?id=CVE-2024-46823 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-22025 https://www.cve.org/CVERecord?id=CVE-2025-22025 Référence CVE CVE-2025-22027 https://www.cve.org/CVERecord?id=CVE-2025-22027 Référence CVE CVE-2025-22033 https://www.cve.org/CVERecord?id=CVE-2025-22033 Référence CVE CVE-2025-22035 https://www.cve.org/CVERecord?id=CVE-2025-22035 Référence CVE CVE-2025-22038 https://www.cve.org/CVERecord?id=CVE-2025-22038 Référence CVE CVE-2025-22040 https://www.cve.org/CVERecord?id=CVE-2025-22040 Référence CVE CVE-2025-22041 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-50051 Référence CVE CVE-2024-50055 https://www.cve.org/CVERecord?id=CVE-2024-50055 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50058 https://www.cve.org/CVERecord?id=CVE-2024-50058 Référence CVE CVE-2024-50059 https://www.cve.org/CVERecord?id=CVE-2024-50059 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50061 https://www.cve.org/CVERecord?id=CVE-2024-50061 Référence CVE CVE-2024-50062 https://www.cve.org/CVERecord?id=CVE-2024-50062 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50064 https://www.cve.org/CVERecord?id=CVE-2024-50064 Référence CVE CVE-2024-50065 https://www.cve.org/CVERecord?id=CVE-2024-50065 Référence CVE CVE-2024-50066 https://www.cve.org/CVERecord?id=CVE-2024-50066 Référence CVE CVE-2024-50067 https://www.cve.org/CVERecord?id=CVE-2024-50067 Référence CVE CVE-2024-50068 https://www.cve.org/CVERecord?id=CVE-2024-50068 Référence CVE CVE-2024-50069 https://www.cve.org/CVERecord?id=CVE-2024-50069 Référence CVE CVE-2024-50070 https://www.cve.org/CVERecord?id=CVE-2024-50070 Référence CVE CVE-2024-50072 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-50051 Référence CVE CVE-2024-50055 https://www.cve.org/CVERecord?id=CVE-2024-50055 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50058 https://www.cve.org/CVERecord?id=CVE-2024-50058 Référence CVE CVE-2024-50059 https://www.cve.org/CVERecord?id=CVE-2024-50059 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50061 https://www.cve.org/CVERecord?id=CVE-2024-50061 Référence CVE CVE-2024-50062 https://www.cve.org/CVERecord?id=CVE-2024-50062 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50064 https://www.cve.org/CVERecord?id=CVE-2024-50064 Référence CVE CVE-2024-50065 https://www.cve.org/CVERecord?id=CVE-2024-50065 Référence CVE CVE-2024-50066 https://www.cve.org/CVERecord?id=CVE-2024-50066 Référence CVE CVE-2024-50067 https://www.cve.org/CVERecord?id=CVE-2024-50067 Référence CVE CVE-2024-50068 https://www.cve.org/CVERecord?id=CVE-2024-50068 Référence CVE CVE-2024-50069 https://www.cve.org/CVERecord?id=CVE-2024-50069 Référence CVE CVE-2024-50070 https://www.cve.org/CVERecord?id=CVE-2024-50070 Référence CVE CVE-2024-50072 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-50051 Référence CVE CVE-2024-50055 https://www.cve.org/CVERecord?id=CVE-2024-50055 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50058 https://www.cve.org/CVERecord?id=CVE-2024-50058 Référence CVE CVE-2024-50059 https://www.cve.org/CVERecord?id=CVE-2024-50059 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50061 https://www.cve.org/CVERecord?id=CVE-2024-50061 Référence CVE CVE-2024-50062 https://www.cve.org/CVERecord?id=CVE-2024-50062 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50064 https://www.cve.org/CVERecord?id=CVE-2024-50064 Référence CVE CVE-2024-50065 https://www.cve.org/CVERecord?id=CVE-2024-50065 Référence CVE CVE-2024-50066 https://www.cve.org/CVERecord?id=CVE-2024-50066 Référence CVE CVE-2024-50068 https://www.cve.org/CVERecord?id=CVE-2024-50068 Référence CVE CVE-2024-50069 https://www.cve.org/CVERecord?id=CVE-2024-50069 Référence CVE CVE-2024-50070 https://www.cve.org/CVERecord?id=CVE-2024-50070 Référence CVE CVE-2024-50072 https://www.cve.org/CVERecord?id=CVE-2024-50072 Référence CVE CVE-2024-50073 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-50049 Référence CVE CVE-2024-50055 https://www.cve.org/CVERecord?id=CVE-2024-50055 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50058 https://www.cve.org/CVERecord?id=CVE-2024-50058 Référence CVE CVE-2024-50059 https://www.cve.org/CVERecord?id=CVE-2024-50059 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50061 https://www.cve.org/CVERecord?id=CVE-2024-50061 Référence CVE CVE-2024-50062 https://www.cve.org/CVERecord?id=CVE-2024-50062 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50064 https://www.cve.org/CVERecord?id=CVE-2024-50064 Référence CVE CVE-2024-50065 https://www.cve.org/CVERecord?id=CVE-2024-50065 Référence CVE CVE-2024-50066 https://www.cve.org/CVERecord?id=CVE-2024-50066 Référence CVE CVE-2024-50067 https://www.cve.org/CVERecord?id=CVE-2024-50067 Référence CVE CVE-2024-50068 https://www.cve.org/CVERecord?id=CVE-2024-50068 Référence CVE CVE-2024-50069 https://www.cve.org/CVERecord?id=CVE-2024-50069 Référence CVE CVE-2024-50070 https://www.cve.org/CVERecord?id=CVE-2024-50070 Référence CVE CVE-2024-50071 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-50049 Référence CVE CVE-2024-50055 https://www.cve.org/CVERecord?id=CVE-2024-50055 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50058 https://www.cve.org/CVERecord?id=CVE-2024-50058 Référence CVE CVE-2024-50059 https://www.cve.org/CVERecord?id=CVE-2024-50059 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50061 https://www.cve.org/CVERecord?id=CVE-2024-50061 Référence CVE CVE-2024-50062 https://www.cve.org/CVERecord?id=CVE-2024-50062 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50064 https://www.cve.org/CVERecord?id=CVE-2024-50064 Référence CVE CVE-2024-50065 https://www.cve.org/CVERecord?id=CVE-2024-50065 Référence CVE CVE-2024-50066 https://www.cve.org/CVERecord?id=CVE-2024-50066 Référence CVE CVE-2024-50067 https://www.cve.org/CVERecord?id=CVE-2024-50067 Référence CVE CVE-2024-50068 https://www.cve.org/CVERecord?id=CVE-2024-50068 Référence CVE CVE-2024-50069 https://www.cve.org/CVERecord?id=CVE-2024-50069 Référence CVE CVE-2024-50070 https://www.cve.org/CVERecord?id=CVE-2024-50070 Référence CVE CVE-2024-50071 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-50047 Référence CVE CVE-2024-50048 https://www.cve.org/CVERecord?id=CVE-2024-50048 Référence CVE CVE-2024-50049 https://www.cve.org/CVERecord?id=CVE-2024-50049 Référence CVE CVE-2024-50055 https://www.cve.org/CVERecord?id=CVE-2024-50055 Référence CVE CVE-2024-50058 https://www.cve.org/CVERecord?id=CVE-2024-50058 Référence CVE CVE-2024-50059 https://www.cve.org/CVERecord?id=CVE-2024-50059 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50061 https://www.cve.org/CVERecord?id=CVE-2024-50061 Référence CVE CVE-2024-50062 https://www.cve.org/CVERecord?id=CVE-2024-50062 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50064 https://www.cve.org/CVERecord?id=CVE-2024-50064 Référence CVE CVE-2024-50067 https://www.cve.org/CVERecord?id=CVE-2024-50067 Référence CVE CVE-2024-50069 https://www.cve.org/CVERecord?id=CVE-2024-50069 Référence CVE CVE-2024-50073 https://www.cve.org/CVERecord?id=CVE-2024-50073 Référence CVE CVE-2024-50074 https://www.cve.org/CVERecord?id=CVE-2024-50074 Référence CVE CVE-2024-50075 https://www.cve.org/CVERecord?id=CVE-2024-50075 Référence CVE CVE-2024-50076 https://www.cve.org/CVERecord?id=CVE-2024-50076 Référence CVE CVE-2024-50077 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-50047 Référence CVE CVE-2024-50048 https://www.cve.org/CVERecord?id=CVE-2024-50048 Référence CVE CVE-2024-50049 https://www.cve.org/CVERecord?id=CVE-2024-50049 Référence CVE CVE-2024-50055 https://www.cve.org/CVERecord?id=CVE-2024-50055 Référence CVE CVE-2024-50058 https://www.cve.org/CVERecord?id=CVE-2024-50058 Référence CVE CVE-2024-50059 https://www.cve.org/CVERecord?id=CVE-2024-50059 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50061 https://www.cve.org/CVERecord?id=CVE-2024-50061 Référence CVE CVE-2024-50062 https://www.cve.org/CVERecord?id=CVE-2024-50062 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50064 https://www.cve.org/CVERecord?id=CVE-2024-50064 Référence CVE CVE-2024-50069 https://www.cve.org/CVERecord?id=CVE-2024-50069 Référence CVE CVE-2024-50073 https://www.cve.org/CVERecord?id=CVE-2024-50073 Référence CVE CVE-2024-50074 https://www.cve.org/CVERecord?id=CVE-2024-50074 Référence CVE CVE-2024-50075 https://www.cve.org/CVERecord?id=CVE-2024-50075 Référence CVE CVE-2024-50076 https://www.cve.org/CVERecord?id=CVE-2024-50076 Référence CVE CVE-2024-50077 https://www.cve.org/CVERecord?id=CVE-2024-50077 Référence CVE CVE-2024-50078 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-013344Linux の 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
Linux: < 5.5, 6.1.135 ≤ 6.1.*, 6.6.57 ≤ 6.6.*, 6.11.4 ≤ 6.11.*, 6.12 ≤ *
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
To mitigate this issue, ensure that unprivileged eBPF usage is disabled. This can be achieved by setting the `kernel.unprivileged_bpf_disabled` sysctl to 1. To check the current status: `cat /proc/sys/kernel/unprivileged_bpf_disabled` To disable unprivileged eBPF usage for the current session: `echo 1 > /proc/sys/kernel/unprivileged_bpf_disabled` To make this change persistent across reboots, create a file named `/etc/sysctl.d/99-disable-unprivileged-bpf.conf` with the following content: `kernel.unprivileged_bpf_disabled = 1` Then, apply the changes: `sysctl --system`
04

Evidence and provenance

Published 21 Oct 2024 · Last source change 8 Sept 2026, 08:39 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-44785
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6 < d9a807fb7cbfad4328824186e2e4bee28f72169b; f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6 < 5d5e3b4cbe8ee16b7bf96fd73a421c92a9da3ca1; f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6 < 88c2a10e6c176c2860cd0659f4c0e9d20b3f64d1; f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6 < 28ead3eaabc16ecc907cfb71876da028080f6356; 5.5 · Fixed: < 5.5; 6.1.135 ≤ 6.1.*; 6.6.57 ≤ 6.6.*; 6.11.4 ≤ 6.11.*; 6.12 ≤ *
    After
    Linux: f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6 < d9a807fb7cbfad4328824186e2e4bee28f72169b, f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6 < 5d5e3b4cbe8ee16b7bf96fd73a421c92a9da3ca1, f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6 < 88c2a10e6c176c2860cd0659f4c0e9d20b3f64d1, f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6 < 28ead3eaabc16ecc907cfb71876da028080f6356, 5.5 · Fixed: Linux: < 5.5, 6.1.135 ≤ 6.1.*, 6.6.57 ≤ 6.6.*, 6.11.4 ≤ 6.11.*, 6.12 ≤ *
    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-44785↗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-50063 · cve.blacktree.nl