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

bpf: Fail verification for sign-extension of packet data/data_end/data_meta

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 15 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 3 Oct 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.21% 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 15 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.

19 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 15 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.2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).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.11.2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.2-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-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
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-47702 · CSAF 2.0 · revision 58 · interimSUSE Product Security TeamCVE-2024-47702
15 known affected

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

  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
  • SLES 15 SP1 CHOST Images for Microsoft Azure
  • SLES 15 SP2 CHOST Images for Microsoft Azure
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Fail verification for sign-extension of packet data/data_end/data_meta syzbot reported a kernel crash due to commit 1f1e864b6555 ("bpf: Handle sign-extenstin ctx member accesses"). The reason is due to sign-extension of 32-bit load for packet data/data_end/data_meta uapi field. The original code looks like: r2 = *(s32 *)(r1 + 76) /* load __sk_buff->data */ r3 = *(u32 *)(r1 + 80) /* load __sk_buff->data_end */ r0 = r2 r0 += 8 if r3 > r0 goto +1 ... Note that __sk_buff->data load has 32-bit sign extension. After verification and convert_ctx_accesses(), the final asm code looks like: r2 = *(u64 *)(r1 +208) r2 = (s32)r2 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 ... Note that 'r2 = (s32)r2' may make the kernel __sk_buff->data address invalid which may cause runtime failure. Currently, in C code, typically we have void *data = (void *)(long)skb->data; void *data_end = (void *)(long)skb->data_end; ... and it will generate r2 = *(u64 *)(r1 +208) r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 If we allow sign-extension, void *data = (void *)(long)(int)skb->data; void *data_end = (void *)(long)skb->data_end; ... the generated code looks like r2 = *(u64 *)(r1 +208) r2 >= 32 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 and this will cause verification failure since "r2 data */ this patch added additional checking in is_valid_access() callback function for packet data/data_end/data_meta access. If those accesses are with sign-extenstion, the verification will fail. [1] https://lore.kernel.org/bpf/000000000000c90eee061d236d37@google.com/
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-42622

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf: Fail verification for sign-extension of packet data/data_end/data_meta syzbot reported a kernel crash due to commit 1f1e864b6555 ("bpf: Handle sign-extenstin ctx member accesses"). The reason is due to sign-extension of 32-bit load for packet data/data_end/data_meta uapi field. The original code looks like: r2 = *(s32 *)(r1 + 76) /* load __sk_buff->data */ r3 = *(u32 *)(r1 + 80) /* load __sk_buff->data_end */ r0 = r2 r0 += 8 if r3 > r0 goto +1 ... Note that __sk_buff->data load has 32-bit sign extension. After verification and convert_ctx_accesses(), the final asm code looks like: r2 = *(u64 *)(r1 +208) r2 = (s32)r2 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 ... Note that 'r2 = (s32)r2' may make the kernel __sk_buff->data address invalid which may cause runtime failure. Currently, in C code, typically we have void *data = (void *)(long)skb->data; void *data_end = (void *)(long)skb->data_end; ... and it will generate r2 = *(u64 *)(r1 +208) r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 If we allow sign-extension, void *data = (void *)(long)(int)skb->data; void *data_end = (void *)(long)skb->data_end; ... the generated code looks like r2 = *(u64 *)(r1 +208) r2 <<= 32 r2 s>>= 32 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 and this will cause verification failure since "r2 <<= 32" is not allowed as "r2" is a packet pointer. To fix this issue for case r2 = *(s32 *)(r1 + 76) /* load __sk_buff->data */ this patch added additional checking in is_valid_access() callback function for packet data/data_end/data_meta access. If those accesses are with sign-extenstion, the verification will fail. [1] https://lore.kernel.org/bpf/000000000000c90eee061d236d37@google.com/

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 15 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: Fail verification for sign-extension of packet data/data_end/data_meta syzbot reported a kernel crash due to commit 1f1e864b6555 ("bpf: Handle sign-extenstin ctx member accesses"). The reason is due to sign-extension of 32-bit load for packet data/data_end/data_meta uapi field. The original code looks like: r2 = *(s32 *)(r1 + 76) /* load __sk_buff->data */ r3 = *(u32 *)(r1 + 80) /* load __sk_buff->data_end */ r0 = r2 r0 += 8 if r3 > r0 goto +1 ... Note that __sk_buff->data load has 32-bit sign extension. After verification and convert_ctx_accesses(), the final asm code looks like: r2 = *(u64 *)(r1 +208) r2 = (s32)r2 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 ... Note that 'r2 = (s32)r2' may make the kernel __sk_buff->data address invalid which may cause runtime failure. Currently, in C code, typically we have void *data = (void *)(long)skb->data; void *data_end = (void *)(long)skb->data_end; ... and it will generate r2 = *(u64 *)(r1 +208) r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 If we allow sign-extension, void *data = (void *)(long)(int)skb->data; void *data_end = (void *)(long)skb->data_end; ... the generated code looks like r2 = *(u64 *)(r1 +208) r2 <<= 32 r2 s>>= 32 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 and this will cause verification failure since "r2 <<= 32" is not allowed as "r2" is a packet pointer. To fix this issue for case r2 = *(s32 *)(r1 + 76) /* load __sk_buff->data */ this patch added additional checking in is_valid_access() callback function for packet data/data_end/data_meta access. If those accesses are with sign-extenstion, the verification will fail. [1] https://lore.kernel.org/bpf/000000000000c90eee061d236d37@google.com/

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Fail verification for sign-extension of packet data/data_end/data_meta syzbot reported a kernel crash due to commit 1f1e864b6555 ("bpf: Handle sign-extenstin ctx member accesses"). The reason is due to sign-extension of 32-bit load for packet data/data_end/data_meta uapi field. The original code looks like: r2 = *(s32 *)(r1 + 76) /* load __sk_buff->data */ r3 = *(u32 *)(r1 + 80) /* load __sk_buff->data_end */ r0 = r2 r0 += 8 if r3 > r0 goto +1 ... Note that __sk_buff->data load has 32-bit sign extension. After verification and convert_ctx_accesses(), the final asm code looks like: r2 = *(u64 *)(r1 +208) r2 = (s32)r2 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 ... Note that 'r2 = (s32)r2' may make the kernel __sk_buff->data address invalid which may cause runtime failure. Currently, in C code, typically we have void *data = (void *)(long)skb->data; void *data_end = (void *)(long)skb->data_end; ... and it will generate r2 = *(u64 *)(r1 +208) r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 If we allow sign-extension, void *data = (void *)(long)(int)skb->data; void *data_end = (void *)(long)skb->data_end; ... the generated code looks like r2 = *(u64 *)(r1 +208) r2 <<= 32 r2 s>>= 32 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 and this will cause verification failure since "r2 <<= 32" is not allowed as "r2" is a packet pointer. To fix this issue for case r2 = *(s32 *)(r1 + 76) /* load __sk_buff->data */ this patch added additional checking in is_valid_access() callback function for packet data/data_end/data_meta access. If those accesses are with sign-extenstion, the verification will fail. [1] https://lore.kernel.org/bpf/000000000000c90eee061d236d37@google.com/

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 disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Fail verification for sign-extension of packet data/data_end/data_meta syzbot reported a kernel crash due to commit 1f1e864b6555 ("bpf: Handle sign-extenstin ctx member accesses"). The reason is due to sign-extension of 32-bit load for packet data/data_end/data_meta uapi field. The original code looks like: r2 = *(s32 *)(r1 + 76) /* load __sk_buff->data */ r3 = *(u32 *)(r1 + 80) /* load __sk_buff->data_end */ r0 = r2 r0 += 8 if r3 > r0 goto +1 ... Note that __sk_buff->data load has 32-bit sign extension. After verification and convert_ctx_accesses(), the final asm code looks like: r2 = *(u64 *)(r1 +208) r2 = (s32)r2 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 ... Note that 'r2 = (s32)r2' may make the kernel __sk_buff->data address invalid which may cause runtime failure. Currently, in C code, typically we have void *data = (void *)(long)skb->data; void *data_end = (void *)(long)skb->data_end; ... and it will generate r2 = *(u64 *)(r1 +208) r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 If we allow sign-extension, void *data = (void *)(long)(int)skb->data; void *data_end = (void *)(long)skb->data_end; ... the generated code looks like r2 = *(u64 *)(r1 +208) r2 <<= 32 r2 s>>= 32 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 and this will cause verification failure since "r2 <<= 32" is not allowed as "r2" is a packet pointer. To fix this issue for case r2 = *(s32 *)(r1 + 76) /* load __sk_buff->data */ this patch added additional checking in is_valid_access() callback function for packet data/data_end/data_meta access. If those accesses are with sign-extenstion, the verification will fail. [1] https://lore.kernel.org/bpf/000000000000c90eee061d236d37@google.com/

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 disrupt the affected service.

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 → disrupt the affected service
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.
Denial of service
A

Official authority intelligence

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

ENISA EUVD · EUVD-2024-42622Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf: Fail verification for sign-extension of packet data/data_end/data_meta syzbot reported a kernel crash due to commit 1f1e864b6555 ("bpf: Handle sign-extenstin ctx member accesses"). The reason is due to sign-extension of 32-bit load for packet data/data_end/data_meta uapi field. The original code looks like: r2 = *(s32 *)(r1 + 76) /* load __sk_buff->data */ r3 = *(u32 *)(r1 + 80) /* load __sk_buff->data_end */ r0 = r2 r0 += 8 if r3 > r0 goto +1 ... Note that __sk_buff->data load has 32-bit sign extension. After verification and convert_ctx_accesses(), the final asm code looks like: r2 = *(u64 *)(r1 +208) r2 = (s32)r2 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 ... Note that 'r2 = (s32)r2' may make the kernel __sk_buff->data address invalid which may cause runtime failure. Currently, in C code, typically we have void *data = (void *)(long)skb->data; void *data_end = (void *)(long)skb->data_end; ... and it will generate r2 = *(u64 *)(r1 +208) r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 If we allow sign-extension, void *data = (void *)(long)(int)skb->data; void *data_end = (void *)(long)skb->data_end; ... the generated code looks like r2 = *(u64 *)(r1 +208) r2 <<= 32 r2 s>>= 32 r3 = *(u64 *)(r1 +80) r0 = r2 r0 += 8 if r3 > r0 goto pc+1 and this will cause verification failure since "r2 <<= 32" is not allowed as "r2" is a packet pointer. To fix this issue for case r2 = *(s32 *)(r1 + 76) /* load __sk_buff->data */ this patch added additional checking in is_valid_access() callback function for packet data/data_end/data_meta access. If those accesses are with sign-extenstion, the verification will fail. [1] https://lore.kernel.org/bpf/000000000000c90eee061d236d37@google.com/

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

ord?id=CVE-2024-46864 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2024-47672 https://www.cve.org/CVERecord?id=CVE-2024-47672 Référence CVE CVE-2024-47675 https://www.cve.org/CVERecord?id=CVE-2024-47675 Référence CVE CVE-2024-47682 https://www.cve.org/CVERecord?id=CVE-2024-47682 Référence CVE CVE-2024-47687 https://www.cve.org/CVERecord?id=CVE-2024-47687 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47700 https://www.cve.org/CVERecord?id=CVE-2024-47700 Référence CVE CVE-2024-47702 https://www.cve.org/CVERecord?id=CVE-2024-47702 Référence CVE CVE-2024-47715 https://www.cve.org/CVERecord?id=CVE-2024-47715 Référence CVE CVE-2024-47719 https://www.cve.org/CVERecord?id=CVE-2024-47719 Référence CVE CVE-2024-47727 https://www.cve.org/CVERecord?id=CVE-2024-47727 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48876 https://www.cve.org/CVERecord?id=CVE-2024-48876 Référence CVE CVE-2024-49855 https://www.cve.org/CVERecord?id=CVE-2024-49855 Référence CVE CVE-2024-49856 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47700 https://www.cve.org/CVERecord?id=CVE-2024-47700 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47702 https://www.cve.org/CVERecord?id=CVE-2024-47702 Référence CVE CVE-2024-47703 https://www.cve.org/CVERecord?id=CVE-2024-47703 Référence CVE CVE-2024-47704 https://www.cve.org/CVERecord?id=CVE-2024-47704 Référence CVE CVE-2024-47705 https://www.cve.org/CVERecord?id=CVE-2024-47705 Référence CVE CVE-2024-47706 https://www.cve.org/CVERecord?id=CVE-2024-47706 Référence CVE CVE-2024-47707 https://www.cve.org/CVERecord?id=CVE-2024-47707 Référence CVE CVE-2024-47709 https://www.cve.org/CVERecord?id=CVE-2024-47709 Référence CVE CVE-2024-47710 https://www.cve.org/CVERecord?id=CVE-2024-47710 Référence CVE CVE-2024-47711 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-47693 Référence CVE CVE-2024-47694 https://www.cve.org/CVERecord?id=CVE-2024-47694 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47700 https://www.cve.org/CVERecord?id=CVE-2024-47700 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47702 https://www.cve.org/CVERecord?id=CVE-2024-47702 Référence CVE CVE-2024-47703 https://www.cve.org/CVERecord?id=CVE-2024-47703 Référence CVE CVE-2024-47704 https://www.cve.org/CVERecord?id=CVE-2024-47704 Référence CVE CVE-2024-47705 https://www.cve.org/CVERecord?id=CVE-2024-47705 Référence CVE CVE-2024-47706 https://www.cve.org/CVERecord?id=CVE-2024-47706 Référence CVE CVE-2024-47707 https://www.cve.org/CVERecord?id=CVE-2024-47707 Référence CVE CVE-2024-47708 https://www.cve.org/CVERecord?id=CVE-2024-47708 Référence CVE CVE-2024-47709 https://www.cve.org/CVERecord?id=CVE-2024-47709 Référence CVE CVE-2024-47710 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47700 https://www.cve.org/CVERecord?id=CVE-2024-47700 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47702 https://www.cve.org/CVERecord?id=CVE-2024-47702 Référence CVE CVE-2024-47703 https://www.cve.org/CVERecord?id=CVE-2024-47703 Référence CVE CVE-2024-47704 https://www.cve.org/CVERecord?id=CVE-2024-47704 Référence CVE CVE-2024-47705 https://www.cve.org/CVERecord?id=CVE-2024-47705 Référence CVE CVE-2024-47706 https://www.cve.org/CVERecord?id=CVE-2024-47706 Référence CVE CVE-2024-47707 https://www.cve.org/CVERecord?id=CVE-2024-47707 Référence CVE CVE-2024-47709 https://www.cve.org/CVERecord?id=CVE-2024-47709 Référence CVE CVE-2024-47710 https://www.cve.org/CVERecord?id=CVE-2024-47710 Référence CVE CVE-2024-47712 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47693 Référence CVE CVE-2024-47694 https://www.cve.org/CVERecord?id=CVE-2024-47694 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47700 https://www.cve.org/CVERecord?id=CVE-2024-47700 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47702 https://www.cve.org/CVERecord?id=CVE-2024-47702 Référence CVE CVE-2024-47703 https://www.cve.org/CVERecord?id=CVE-2024-47703 Référence CVE CVE-2024-47704 https://www.cve.org/CVERecord?id=CVE-2024-47704 Référence CVE CVE-2024-47705 https://www.cve.org/CVERecord?id=CVE-2024-47705 Référence CVE CVE-2024-47706 https://www.cve.org/CVERecord?id=CVE-2024-47706 Référence CVE CVE-2024-47707 https://www.cve.org/CVERecord?id=CVE-2024-47707 Référence CVE CVE-2024-47708 https://www.cve.org/CVERecord?id=CVE-2024-47708 Référence CVE CVE-2024-47709 https://www.cve.org/CVERecord?id=CVE-2024-47709 Référence CVE CVE-2024-47710 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47688 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-47702 https://www.cve.org/CVERecord?id=CVE-2024-47702 Référence CVE CVE-2024-47703 https://www.cve.org/CVERecord?id=CVE-2024-47703 Référence CVE CVE-2024-47704 https://www.cve.org/CVERecord?id=CVE-2024-47704 Référence CVE CVE-2024-47705 https://www.cve.org/CVERecord?id=CVE-2024-47705 Référence CVE CVE-2024-47706 https://www.cve.org/CVERecord?id=CVE-2024-47706 Référence CVE CVE-2024-47707 https://www.cve.org/CVERecord?id=CVE-2024-47707 Référence CVE CVE-2024-47709 https://www.cve.org/CVERecord?id=CVE-2024-47709 Référence CVE CVE-2024-47710 https://www.cve.org/CVERecord?id=CVE-2024-47710 Référence CVE CVE-2024-47712 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47687 Référence CVE CVE-2024-47688 https://www.cve.org/CVERecord?id=CVE-2024-47688 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=CVE-2024-47693 Référence CVE CVE-2024-47695 https://www.cve.org/CVERecord?id=CVE-2024-47695 Référence CVE CVE-2024-47696 https://www.cve.org/CVERecord?id=CVE-2024-47696 Référence CVE CVE-2024-47697 https://www.cve.org/CVERecord?id=CVE-2024-47697 Référence CVE CVE-2024-47698 https://www.cve.org/CVERecord?id=CVE-2024-47698 Référence CVE CVE-2024-47699 https://www.cve.org/CVERecord?id=CVE-2024-47699 Référence CVE CVE-2024-47702 https://www.cve.org/CVERecord?id=CVE-2024-47702 Référence CVE CVE-2024-47704 https://www.cve.org/CVERecord?id=CVE-2024-47704 Référence CVE CVE-2024-47705 https://www.cve.org/CVERecord?id=CVE-2024-47705 Référence CVE CVE-2024-47706 https://www.cve.org/CVERecord?id=CVE-2024-47706 Référence CVE CVE-2024-47707 https://www.cve.org/CVERecord?id=CVE-2024-47707 Référence CVE CVE-2024-47709 https://www.cve.org/CVERecord?id=CVE-2024-47709 Référence CVE CVE-2024-47710 https://www.cve.org/CVERecord?id=CVE-2024-47710 Référence CVE CVE-2024-47712 https://www.cve.org/CVERecord?id=CVE-2024-47712 Référence CVE CVE-2024-47713 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-011386Linux の 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: < 6.6, 6.6.158 ≤ 6.6.*, 6.10.13 ≤ 6.10.*, 6.11.2 ≤ 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
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 21 Oct 2024 · Last source change 3 Oct 2026, 10:55 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-42622
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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
    1f1e864b65554e33fe74e3377e58b12f4302f2eb < f1620c93a1ec950d87ef327a565d3907736d3340; 1f1e864b65554e33fe74e3377e58b12f4302f2eb < f09757fe97a225ae505886eac572e4cbfba96537; 1f1e864b65554e33fe74e3377e58b12f4302f2eb < 92de36080c93296ef9005690705cba260b9bd68a; 6.6 · Fixed: < 6.6; 6.10.13 ≤ 6.10.*; 6.11.2 ≤ 6.11.*; 6.12 ≤ *
    After
    Linux: 1f1e864b65554e33fe74e3377e58b12f4302f2eb < 4b48228eebce2ab1b01e3133da822164472b7e46, 1f1e864b65554e33fe74e3377e58b12f4302f2eb < f1620c93a1ec950d87ef327a565d3907736d3340, 1f1e864b65554e33fe74e3377e58b12f4302f2eb < f09757fe97a225ae505886eac572e4cbfba96537, 1f1e864b65554e33fe74e3377e58b12f4302f2eb < 92de36080c93296ef9005690705cba260b9bd68a, 6.6 · Fixed: Linux: < 6.6, 6.6.158 ≤ 6.6.*, 6.10.13 ≤ 6.10.*, 6.11.2 ≤ 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-42622↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗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-47702 · cve.blacktree.nl