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

netfilter: bridge: replace physindev with physinif in nf_bridge_info

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Within 7 days

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

Patch available
R
Operational reassessment

Published severity in operational context

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

Evidence used

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

Distribution package intelligence

Release-specific package status

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

4 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.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.76-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.15-1Debian Security Tracker ↗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-35839 · CSAF 2.0 · revision 136 · interimSUSE Product Security TeamCVE-2024-35839
416 known affected

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

  • kernel-default as component of SUSE Enterprise Storage 7.1
  • kernel-default-devel as component of SUSE Enterprise Storage 7.1
  • kernel-devel as component of SUSE Enterprise Storage 7.1
  • kernel-macros as component of SUSE Enterprise Storage 7.1
  • kernel-source as component of SUSE Enterprise Storage 7.1
  • reiserfs-kmp-default as component of SUSE Enterprise Storage 7.1
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex instead of net_device link. To peek into the original net_device we will use dev_get_by_index_rcu(). Thus either we get device and are safe to use it or we don't get it and drop skb.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2024-35839 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: netfilter: bridge: replace physindev with physinif in nf_bridge_info
50 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
CVE-2024-35839 is a flaw in the Linux kernel's Netfilter bridge functionality. It occurs when bridging certain packets, such as those involving destination NAT between virtual Ethernet interfaces. A mismatch between the network device associated with a packet and the neighbor's device can lead to incorrect handling, including references to freed memory. This issue could cause system crashes. The problem has been fixed by using safer methods to retrieve the network device during packet processing. Users should update their kernels to a patched version to avoid this vulnerability.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2024-35656

No EUVD known-exploited evidence

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

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended 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: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex instead of net_device link. To peek into the original net_device we will use dev_get_by_index_rcu(). Thus either we get device and are safe to use it or we don't get it and drop skb.

What

In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex instead of net_device link. To peek into the original net_device we will use dev_get_by_index_rcu(). Thus either we get device and are safe to use it or we don't get it and drop skb.

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: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex instead of net_device link. To peek into the original net_device we will use dev_get_by_index_rcu(). Thus either we get device and are safe to use it or we don't get it and drop skb.

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.

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

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240522Security Bulletin 22 May 2024

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

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

d?id=CVE-2024-35801 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35810 https://www.cve.org/CVERecord?id=CVE-2024-35810 Référence CVE CVE-2024-35814 https://www.cve.org/CVERecord?id=CVE-2024-35814 Référence CVE CVE-2024-35823 https://www.cve.org/CVERecord?id=CVE-2024-35823 Référence CVE CVE-2024-35824 https://www.cve.org/CVERecord?id=CVE-2024-35824 Référence CVE CVE-2024-35835 https://www.cve.org/CVERecord?id=CVE-2024-35835 Référence CVE CVE-2024-35838 https://www.cve.org/CVERecord?id=CVE-2024-35838 Référence CVE CVE-2024-35839 https://www.cve.org/CVERecord?id=CVE-2024-35839 Référence CVE CVE-2024-35845 https://www.cve.org/CVERecord?id=CVE-2024-35845 Référence CVE CVE-2024-35847 https://www.cve.org/CVERecord?id=CVE-2024-35847 Référence CVE CVE-2024-35852 https://www.cve.org/CVERecord?id=CVE-2024-35852 Référence CVE CVE-2024-35853 https://www.cve.org/CVERecord?id=CVE-2024-35853 Référence CVE CVE-2024-35854 https://www.cve.org/CVERecord?id=CVE-2024-35854 Référence CVE CVE-2024-35855 https://www.cve.org/CVERecord?id=CVE-2024-35855 Référence CVE CVE-2024-35877 https://www.cve.org/CVERecord?id=CVE-2024-35877 Référence CVE CVE-2024-35884 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35195 Référence CVE CVE-2024-35784 https://www.cve.org/CVERecord?id=CVE-2024-35784 Référence CVE CVE-2024-35794 https://www.cve.org/CVERecord?id=CVE-2024-35794 Référence CVE CVE-2024-35799 https://www.cve.org/CVERecord?id=CVE-2024-35799 Référence CVE CVE-2024-35801 https://www.cve.org/CVERecord?id=CVE-2024-35801 Référence CVE CVE-2024-35803 https://www.cve.org/CVERecord?id=CVE-2024-35803 Référence CVE CVE-2024-35808 https://www.cve.org/CVERecord?id=CVE-2024-35808 Référence CVE CVE-2024-35826 https://www.cve.org/CVERecord?id=CVE-2024-35826 Référence CVE CVE-2024-35832 https://www.cve.org/CVERecord?id=CVE-2024-35832 Référence CVE CVE-2024-35839 https://www.cve.org/CVERecord?id=CVE-2024-35839 Référence CVE CVE-2024-35843 https://www.cve.org/CVERecord?id=CVE-2024-35843 Référence CVE CVE-2024-35862 https://www.cve.org/CVERecord?id=CVE-2024-35862 Référence CVE CVE-2024-35865 https://www.cve.org/CVERecord?id=CVE-2024-35865 Référence CVE CVE-2024-35868 https://www.cve.org/CVERecord?id=CVE-2024-35868 Référence CVE CVE-2024-35870 https://www.cve.org/CVERecord?id=CVE-2024-35870 Référence CVE CVE-2024-35875 https://www.cve.org/CVERecord?id=CVE-2024-35875 Référence CVE CVE-2024-35878 https://www.cve.org/CVERecord?id=CVE-2024-35878 Référence CVE CVE-2024-35908 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-35195 Référence CVE CVE-2024-35784 https://www.cve.org/CVERecord?id=CVE-2024-35784 Référence CVE CVE-2024-35794 https://www.cve.org/CVERecord?id=CVE-2024-35794 Référence CVE CVE-2024-35799 https://www.cve.org/CVERecord?id=CVE-2024-35799 Référence CVE CVE-2024-35801 https://www.cve.org/CVERecord?id=CVE-2024-35801 Référence CVE CVE-2024-35803 https://www.cve.org/CVERecord?id=CVE-2024-35803 Référence CVE CVE-2024-35808 https://www.cve.org/CVERecord?id=CVE-2024-35808 Référence CVE CVE-2024-35826 https://www.cve.org/CVERecord?id=CVE-2024-35826 Référence CVE CVE-2024-35832 https://www.cve.org/CVERecord?id=CVE-2024-35832 Référence CVE CVE-2024-35839 https://www.cve.org/CVERecord?id=CVE-2024-35839 Référence CVE CVE-2024-35843 https://www.cve.org/CVERecord?id=CVE-2024-35843 Référence CVE CVE-2024-35862 https://www.cve.org/CVERecord?id=CVE-2024-35862 Référence CVE CVE-2024-35865 https://www.cve.org/CVERecord?id=CVE-2024-35865 Référence CVE CVE-2024-35868 https://www.cve.org/CVERecord?id=CVE-2024-35868 Référence CVE CVE-2024-35870 https://www.cve.org/CVERecord?id=CVE-2024-35870 Référence CVE CVE-2024-35875 https://www.cve.org/CVERecord?id=CVE-2024-35875 Référence CVE CVE-2024-35878 https://www.cve.org/CVERecord?id=CVE-2024-35878 Référence CVE CVE-2024-35908 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26825 Référence CVE CVE-2024-26831 https://www.cve.org/CVERecord?id=CVE-2024-26831 Référence CVE CVE-2024-26872 https://www.cve.org/CVERecord?id=CVE-2024-26872 Référence CVE CVE-2024-26875 https://www.cve.org/CVERecord?id=CVE-2024-26875 Référence CVE CVE-2024-26924 https://www.cve.org/CVERecord?id=CVE-2024-26924 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-28956 https://www.cve.org/CVERecord?id=CVE-2024-28956 Référence CVE CVE-2024-35790 https://www.cve.org/CVERecord?id=CVE-2024-35790 Référence CVE CVE-2024-35839 https://www.cve.org/CVERecord?id=CVE-2024-35839 Référence CVE CVE-2024-35840 https://www.cve.org/CVERecord?id=CVE-2024-35840 Référence CVE CVE-2024-36959 https://www.cve.org/CVERecord?id=CVE-2024-36959 Référence CVE CVE-2024-36978 https://www.cve.org/CVERecord?id=CVE-2024-36978 Référence CVE CVE-2024-38588 https://www.cve.org/CVERecord?id=CVE-2024-38588 Référence CVE CVE-2024-41085 https://www.cve.org/CVERecord?id=CVE-2024-41085 Référence CVE CVE-2024-43869 https://www.cve.org/CVERecord?id=CVE-2024-43869 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-49568 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0401Multiples vulnérabilités dans Juniper Networks Secure Analytics

d?id=CVE-2024-24857 Référence CVE CVE-2024-26851 https://www.cve.org/CVERecord?id=CVE-2024-26851 Référence CVE CVE-2024-26924 https://www.cve.org/CVERecord?id=CVE-2024-26924 Référence CVE CVE-2024-26976 https://www.cve.org/CVERecord?id=CVE-2024-26976 Référence CVE CVE-2024-27017 https://www.cve.org/CVERecord?id=CVE-2024-27017 Référence CVE CVE-2024-27062 https://www.cve.org/CVERecord?id=CVE-2024-27062 Référence CVE CVE-2024-29736 https://www.cve.org/CVERecord?id=CVE-2024-29736 Référence CVE CVE-2024-32007 https://www.cve.org/CVERecord?id=CVE-2024-32007 Référence CVE CVE-2024-35195 https://www.cve.org/CVERecord?id=CVE-2024-35195 Référence CVE CVE-2024-35839 https://www.cve.org/CVERecord?id=CVE-2024-35839 Référence CVE CVE-2024-35898 https://www.cve.org/CVERecord?id=CVE-2024-35898 Référence CVE CVE-2024-35939 https://www.cve.org/CVERecord?id=CVE-2024-35939 Référence CVE CVE-2024-38540 https://www.cve.org/CVERecord?id=CVE-2024-38540 Référence CVE CVE-2024-38541 https://www.cve.org/CVERecord?id=CVE-2024-38541 Référence CVE CVE-2024-38586 https://www.cve.org/CVERecord?id=CVE-2024-38586 Référence CVE CVE-2024-38608 https://www.cve.org/CVERecord?id=CVE-2024-38608 Référence CVE CVE-2024-39503 https://www.cve.org/CVERecord?id=CVE-2024-39503 Référence CVE CVE-2024-40924 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27268 Référence CVE CVE-2024-28849 https://www.cve.org/CVERecord?id=CVE-2024-28849 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-29180 https://www.cve.org/CVERecord?id=CVE-2024-29180 Référence CVE CVE-2024-29415 https://www.cve.org/CVERecord?id=CVE-2024-29415 Référence CVE CVE-2024-29736 https://www.cve.org/CVERecord?id=CVE-2024-29736 Référence CVE CVE-2024-31141 https://www.cve.org/CVERecord?id=CVE-2024-31141 Référence CVE CVE-2024-32007 https://www.cve.org/CVERecord?id=CVE-2024-32007 Référence CVE CVE-2024-33883 https://www.cve.org/CVERecord?id=CVE-2024-33883 Référence CVE CVE-2024-35839 https://www.cve.org/CVERecord?id=CVE-2024-35839 Référence CVE CVE-2024-35898 https://www.cve.org/CVERecord?id=CVE-2024-35898 Référence CVE CVE-2024-35939 https://www.cve.org/CVERecord?id=CVE-2024-35939 Référence CVE CVE-2024-36361 https://www.cve.org/CVERecord?id=CVE-2024-36361 Référence CVE CVE-2024-37890 https://www.cve.org/CVERecord?id=CVE-2024-37890 Référence CVE CVE-2024-38540 https://www.cve.org/CVERecord?id=CVE-2024-38540 Référence CVE CVE-2024-38541 https://www.cve.org/CVERecord?id=CVE-2024-38541 Référence CVE CVE-2024-38586 https://www.cve.org/CVERecord?id=CVE-2024-38586 Référence CVE CVE-2024-38608 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26924 Référence CVE CVE-2024-26930 https://www.cve.org/CVERecord?id=CVE-2024-26930 Référence CVE CVE-2024-26976 https://www.cve.org/CVERecord?id=CVE-2024-26976 Référence CVE CVE-2024-27029 https://www.cve.org/CVERecord?id=CVE-2024-27029 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-35811 https://www.cve.org/CVERecord?id=CVE-2024-35811 Référence CVE CVE-2024-35815 https://www.cve.org/CVERecord?id=CVE-2024-35815 Référence CVE CVE-2024-35817 https://www.cve.org/CVERecord?id=CVE-2024-35817 Référence CVE CVE-2024-35839 https://www.cve.org/CVERecord?id=CVE-2024-35839 Référence CVE CVE-2024-35847 https://www.cve.org/CVERecord?id=CVE-2024-35847 Référence CVE CVE-2024-35861 https://www.cve.org/CVERecord?id=CVE-2024-35861 Référence CVE CVE-2024-35862 https://www.cve.org/CVERecord?id=CVE-2024-35862 Référence CVE CVE-2024-35863 https://www.cve.org/CVERecord?id=CVE-2024-35863 Référence CVE CVE-2024-35864 https://www.cve.org/CVERecord?id=CVE-2024-35864 Référence CVE CVE-2024-35867 https://www.cve.org/CVERecord?id=CVE-2024-35867 Référence CVE CVE-2024-35895 https://www.cve.org/CVERecord?id=CVE-2024-35895 Référence CVE CVE-2024-35905 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26828 Référence CVE CVE-2024-26852 https://www.cve.org/CVERecord?id=CVE-2024-26852 Référence CVE CVE-2024-26886 https://www.cve.org/CVERecord?id=CVE-2024-26886 Référence CVE CVE-2024-26923 https://www.cve.org/CVERecord?id=CVE-2024-26923 Référence CVE CVE-2024-26924 https://www.cve.org/CVERecord?id=CVE-2024-26924 Référence CVE CVE-2024-26930 https://www.cve.org/CVERecord?id=CVE-2024-26930 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-35817 https://www.cve.org/CVERecord?id=CVE-2024-35817 Référence CVE CVE-2024-35839 https://www.cve.org/CVERecord?id=CVE-2024-35839 Référence CVE CVE-2024-35861 https://www.cve.org/CVERecord?id=CVE-2024-35861 Référence CVE CVE-2024-35862 https://www.cve.org/CVERecord?id=CVE-2024-35862 Référence CVE CVE-2024-35863 https://www.cve.org/CVERecord?id=CVE-2024-35863 Référence CVE CVE-2024-35864 https://www.cve.org/CVERecord?id=CVE-2024-35864 Référence CVE CVE-2024-35867 https://www.cve.org/CVERecord?id=CVE-2024-35867 Référence CVE CVE-2024-35905 https://www.cve.org/CVERecord?id=CVE-2024-35905 Référence CVE CVE-2024-35949 https://www.cve.org/CVERecord?id=CVE-2024-35949 Référence CVE CVE-2024-35950 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26766 Référence CVE CVE-2024-26828 https://www.cve.org/CVERecord?id=CVE-2024-26828 Référence CVE CVE-2024-26852 https://www.cve.org/CVERecord?id=CVE-2024-26852 Référence CVE CVE-2024-26923 https://www.cve.org/CVERecord?id=CVE-2024-26923 Référence CVE CVE-2024-26924 https://www.cve.org/CVERecord?id=CVE-2024-26924 Référence CVE CVE-2024-26930 https://www.cve.org/CVERecord?id=CVE-2024-26930 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-35817 https://www.cve.org/CVERecord?id=CVE-2024-35817 Référence CVE CVE-2024-35839 https://www.cve.org/CVERecord?id=CVE-2024-35839 Référence CVE CVE-2024-35861 https://www.cve.org/CVERecord?id=CVE-2024-35861 Référence CVE CVE-2024-35862 https://www.cve.org/CVERecord?id=CVE-2024-35862 Référence CVE CVE-2024-35863 https://www.cve.org/CVERecord?id=CVE-2024-35863 Référence CVE CVE-2024-35864 https://www.cve.org/CVERecord?id=CVE-2024-35864 Référence CVE CVE-2024-35867 https://www.cve.org/CVERecord?id=CVE-2024-35867 Référence CVE CVE-2024-35905 https://www.cve.org/CVERecord?id=CVE-2024-35905 Référence CVE CVE-2024-35949 https://www.cve.org/CVERecord?id=CVE-2024-35949 Référence CVE CVE-2024-35950 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-48773 Référence CVE CVE-2022-48936 https://www.cve.org/CVERecord?id=CVE-2022-48936 Référence CVE CVE-2023-52492 https://www.cve.org/CVERecord?id=CVE-2023-52492 Référence CVE CVE-2024-24857 https://www.cve.org/CVERecord?id=CVE-2024-24857 Référence CVE CVE-2024-26851 https://www.cve.org/CVERecord?id=CVE-2024-26851 Référence CVE CVE-2024-26924 https://www.cve.org/CVERecord?id=CVE-2024-26924 Référence CVE CVE-2024-26976 https://www.cve.org/CVERecord?id=CVE-2024-26976 Référence CVE CVE-2024-27017 https://www.cve.org/CVERecord?id=CVE-2024-27017 Référence CVE CVE-2024-27062 https://www.cve.org/CVERecord?id=CVE-2024-27062 Référence CVE CVE-2024-35839 https://www.cve.org/CVERecord?id=CVE-2024-35839 Référence CVE CVE-2024-35898 https://www.cve.org/CVERecord?id=CVE-2024-35898 Référence CVE CVE-2024-35939 https://www.cve.org/CVERecord?id=CVE-2024-35939 Référence CVE CVE-2024-38540 https://www.cve.org/CVERecord?id=CVE-2024-38540 Référence CVE CVE-2024-38541 https://www.cve.org/CVERecord?id=CVE-2024-38541 Référence CVE CVE-2024-38586 https://www.cve.org/CVERecord?id=CVE-2024-38586 Référence CVE CVE-2024-38608 https://www.cve.org/CVERecord?id=CVE-2024-38608 Référence CVE CVE-2024-39503 https://www.cve.org/CVERecord?id=CVE-2024-39503 Référence CVE CVE-2024-40924 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Elles permettent à un attaquant de provoquer un déni de service.

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

d?id=CVE-2024-26668 Référence CVE CVE-2024-26810 https://www.cve.org/CVERecord?id=CVE-2024-26810 Référence CVE CVE-2024-26855 https://www.cve.org/CVERecord?id=CVE-2024-26855 Référence CVE CVE-2024-26908 https://www.cve.org/CVERecord?id=CVE-2024-26908 Référence CVE CVE-2024-26925 https://www.cve.org/CVERecord?id=CVE-2024-26925 Référence CVE CVE-2024-27016 https://www.cve.org/CVERecord?id=CVE-2024-27016 Référence CVE CVE-2024-27019 https://www.cve.org/CVERecord?id=CVE-2024-27019 Référence CVE CVE-2024-27020 https://www.cve.org/CVERecord?id=CVE-2024-27020 Référence CVE CVE-2024-27415 https://www.cve.org/CVERecord?id=CVE-2024-27415 Référence CVE CVE-2024-35839 https://www.cve.org/CVERecord?id=CVE-2024-35839 Référence CVE CVE-2024-35896 https://www.cve.org/CVERecord?id=CVE-2024-35896 Référence CVE CVE-2024-35897 https://www.cve.org/CVERecord?id=CVE-2024-35897 Référence CVE CVE-2024-35898 https://www.cve.org/CVERecord?id=CVE-2024-35898 Référence CVE CVE-2024-35962 https://www.cve.org/CVERecord?id=CVE-2024-35962 Référence CVE CVE-2024-36003 https://www.cve.org/CVERecord?id=CVE-2024-36003 Référence CVE CVE-2024-36025 https://www.cve.org/CVERecord?id=CVE-2024-36025 Référence CVE CVE-2024-38538 https://www.cve.org/CVERecord?id=CVE-2024-38538 Référence CVE CVE-2024-38540 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028205Linux の 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.
Patch available
Affected
Fixed
Linux: < 4.2, 6.1.75 ≤ 6.1.*, 6.6.14 ≤ 6.6.*, 6.7.2 ≤ 6.7.*, 6.8 ≤ *
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 17 May 2024 · Last source change 5 Aug 2026, 11:30 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-35656
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 ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-35656↗Vendor CSAF · SUSE Product Security Team↗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-35839 · cve.blacktree.nl