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

netfilter: nf_tables: prefer nft_chain_validate

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 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.32% 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.9.10-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.106-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.10-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.10-1Debian Security Tracker ↗Source updated 7 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 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 6 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 6 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 6 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 6 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-41042 · CSAF 2.0 · revision 118 · interimSUSE Product Security TeamCVE-2024-41042
278 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 High Availability Extension 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: prefer nft_chain_validate nft_chain_validate already performs loop detection because a cycle will result in a call stack overflow (ctx->level >= NFT_JUMP_STACK_SIZE). It also follows maps via ->validate callback in nft_lookup, so there appears no reason to iterate the maps again. nf_tables_check_loops() and all its helper functions can be removed. This improves ruleset load time significantly, from 23s down to 12s. This also fixes a crash bug. Old loop detection code can result in unbounded recursion: BUG: TASK stack guard page was hit at .... Oops: stack guard page: 0000 [#1] PREEMPT SMP KASAN CPU: 4 PID: 1539 Comm: nft Not tainted 6.10.0-rc5+ #1 [..] with a suitable ruleset during validation of register stores. I can't see any actual reason to attempt to check for this from nft_validate_register_store(), at this point the transaction is still in progress, so we don't have a full picture of the rule graph. For nf-next it might make sense to either remove it or make this depend on table->validate_state in case we could catch an error earlier (for improved error reporting to userspace).
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-39308

No EUVD known-exploited evidence

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

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 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: netfilter: nf_tables: prefer nft_chain_validate nft_chain_validate already performs loop detection because a cycle will result in a call stack overflow (ctx->level >= NFT_JUMP_STACK_SIZE). It also follows maps via ->validate callback in nft_lookup, so there appears no reason to iterate the maps again. nf_tables_check_loops() and all its helper functions can be removed. This improves ruleset load time significantly, from 23s down to 12s. This also fixes a crash bug. Old loop detection code can result in unbounded recursion: BUG: TASK stack guard page was hit at .... Oops: stack guard page: 0000 [#1] PREEMPT SMP KASAN CPU: 4 PID: 1539 Comm: nft Not tainted 6.10.0-rc5+ #1 [..] with a suitable ruleset during validation of register stores. I can't see any actual reason to attempt to check for this from nft_validate_register_store(), at this point the transaction is still in progress, so we don't have a full picture of the rule graph. For nf-next it might make sense to either remove it or make this depend on table->validate_state in case we could catch an error earlier (for improved error reporting to userspace).

What

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: prefer nft_chain_validate nft_chain_validate already performs loop detection because a cycle will result in a call stack overflow (ctx->level >= NFT_JUMP_STACK_SIZE). It also follows maps via ->validate callback in nft_lookup, so there appears no reason to iterate the maps again. nf_tables_check_loops() and all its helper functions can be removed. This improves ruleset load time significantly, from 23s down to 12s. This also fixes a crash bug. Old loop detection code can result in unbounded recursion: BUG: TASK stack guard page was hit at .... Oops: stack guard page: 0000 [#1] PREEMPT SMP KASAN CPU: 4 PID: 1539 Comm: nft Not tainted 6.10.0-rc5+ #1 [..] with a suitable ruleset during validation of register stores. I can't see any actual reason to attempt to check for this from nft_validate_register_store(), at this point the transaction is still in progress, so we don't have a full picture of the rule graph. For nf-next it might make sense to either remove it or make this depend on table->validate_state in case we could catch an error earlier (for improved error reporting to userspace).

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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: nf_tables: prefer nft_chain_validate nft_chain_validate already performs loop detection because a cycle will result in a call stack overflow (ctx->level >= NFT_JUMP_STACK_SIZE). It also follows maps via ->validate callback in nft_lookup, so there appears no reason to iterate the maps again. nf_tables_check_loops() and all its helper functions can be removed. This improves ruleset load time significantly, from 23s down to 12s. This also fixes a crash bug. Old loop detection code can result in unbounded recursion: BUG: TASK stack guard page was hit at .... Oops: stack guard page: 0000 [#1] PREEMPT SMP KASAN CPU: 4 PID: 1539 Comm: nft Not tainted 6.10.0-rc5+ #1 [..] with a suitable ruleset during validation of register stores. I can't see any actual reason to attempt to check for this from nft_validate_register_store(), at this point the transaction is still in progress, so we don't have a full picture of the rule graph. For nf-next it might make sense to either remove it or make this depend on table->validate_state in case we could catch an error earlier (for improved error reporting to userspace).

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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 → Out-of-bounds Write → 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: a standard category for the underlying weakness.
CWE-787 ↗

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

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 serviceCWE-787
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-0612IBM Security Guardium: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Guardium ausnutzen, um Sicherheitsbeschränkungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, beliebigen Code auszuführen und vertrauliche Informationen preiszugeben.

Official advisory ↗
BSI · German · WID-SEC-2024-1722Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240731Security Bulletin 31 Jul 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 31 Jul 2024, published on 31 July 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-41012 Référence CVE CVE-2024-41013 https://www.cve.org/CVERecord?id=CVE-2024-41013 Référence CVE CVE-2024-41014 https://www.cve.org/CVERecord?id=CVE-2024-41014 Référence CVE CVE-2024-41023 https://www.cve.org/CVERecord?id=CVE-2024-41023 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41040 https://www.cve.org/CVERecord?id=CVE-2024-41040 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=CVE-2024-41041 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41044 https://www.cve.org/CVERecord?id=CVE-2024-41044 Référence CVE CVE-2024-41055 https://www.cve.org/CVERecord?id=CVE-2024-41055 Référence CVE CVE-2024-41056 https://www.cve.org/CVERecord?id=CVE-2024-41056 Référence CVE CVE-2024-41060 https://www.cve.org/CVERecord?id=CVE-2024-41060 Référence CVE CVE-2024-41064 https://www.cve.org/CVERecord?id=CVE-2024-41064 Référence CVE CVE-2024-41065 https://www.cve.org/CVERecord?id=CVE-2024-41065 Référence CVE CVE-2024-41066 https://www.cve.org/CVERecord?id=CVE-2024-41066 Référence CVE CVE-2024-41076 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52623 Référence CVE CVE-2023-52662 https://www.cve.org/CVERecord?id=CVE-2023-52662 Référence CVE CVE-2023-52933 https://www.cve.org/CVERecord?id=CVE-2023-52933 Référence CVE CVE-2024-26638 https://www.cve.org/CVERecord?id=CVE-2024-26638 Référence CVE CVE-2024-26669 https://www.cve.org/CVERecord?id=CVE-2024-26669 Référence CVE CVE-2024-26939 https://www.cve.org/CVERecord?id=CVE-2024-26939 Référence CVE CVE-2024-35838 https://www.cve.org/CVERecord?id=CVE-2024-35838 Référence CVE CVE-2024-35847 https://www.cve.org/CVERecord?id=CVE-2024-35847 Référence CVE CVE-2024-36917 https://www.cve.org/CVERecord?id=CVE-2024-36917 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-50301 https://www.cve.org/CVERecord?id=CVE-2024-50301 Référence CVE CVE-2024-53064 https://www.cve.org/CVERecord?id=CVE-2024-53064 Référence CVE CVE-2024-56615 https://www.cve.org/CVERecord?id=CVE-2024-56615 Référence CVE CVE-2024-58099 https://www.cve.org/CVERecord?id=CVE-2024-58099 Référence CVE CVE-2025-21764 https://www.cve.org/CVERecord?id=CVE-2025-21764 Référence CVE CVE-2025-21883 https://www.cve.org/CVERecord?id=CVE-2025-21883 Référence CVE CVE-2025-21961 https://www.cve.org/CVERecord?id=CVE-2025-21961 Référence CVE CVE-2025-22104 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-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=CVE-2024-40924 Référence CVE CVE-2024-40961 https://www.cve.org/CVERecord?id=CVE-2024-40961 Référence CVE CVE-2024-40983 https://www.cve.org/CVERecord?id=CVE-2024-40983 Référence CVE CVE-2024-40984 https://www.cve.org/CVERecord?id=CVE-2024-40984 Référence CVE CVE-2024-41009 https://www.cve.org/CVERecord?id=CVE-2024-41009 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41066 https://www.cve.org/CVERecord?id=CVE-2024-41066 Référence CVE CVE-2024-41092 https://www.cve.org/CVERecord?id=CVE-2024-41092 Référence CVE CVE-2024-41093 https://www.cve.org/CVERecord?id=CVE-2024-41093 Référence CVE CVE-2024-42070 https://www.cve.org/CVERecord?id=CVE-2024-42070 Référence CVE CVE-2024-42079 https://www.cve.org/CVERecord?id=CVE-2024-42079 Référence CVE CVE-2024-42244 https://www.cve.org/CVERecord?id=CVE-2024-42244 Référence CVE CVE-2024-42284 https://www.cve.org/CVERecord?id=CVE-2024-42284 Référence CVE CVE-2024-42292 https://www.cve.org/CVERecord?id=

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

rd?id=CVE-2024-3372 Référence CVE CVE-2024-34064 https://www.cve.org/CVERecord?id=CVE-2024-34064 Référence CVE CVE-2024-34069 https://www.cve.org/CVERecord?id=CVE-2024-34069 Référence CVE CVE-2024-35195 https://www.cve.org/CVERecord?id=CVE-2024-35195 Référence CVE CVE-2024-35995 https://www.cve.org/CVERecord?id=CVE-2024-35995 Référence CVE CVE-2024-36015 https://www.cve.org/CVERecord?id=CVE-2024-36015 Référence CVE CVE-2024-36881 https://www.cve.org/CVERecord?id=CVE-2024-36881 Référence CVE CVE-2024-36882 https://www.cve.org/CVERecord?id=CVE-2024-36882 Référence CVE CVE-2024-36974 https://www.cve.org/CVERecord?id=CVE-2024-36974 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2024-49766 https://www.cve.org/CVERecord?id=CVE-2024-49766 Référence CVE CVE-2024-49767 https://www.cve.org/CVERecord?id=CVE-2024-49767 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-56201 https://www.cve.org/CVERecord?id=CVE-2024-56201 Référence CVE CVE-2024-56326 https://www.cve.org/CVERecord?id=CVE-2024-56326 Référence CVE CVE-2024-7553 https://www.cve.org/CVERecord?id=CVE-2024-7553 Référence CVE CVE-2024-8207 https://www.cve.org/CVERecord?id=CVE-202

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

ecord?id=CVE-2024-39338 Référence CVE CVE-2024-39503 https://www.cve.org/CVERecord?id=CVE-2024-39503 Référence CVE CVE-2024-4067 https://www.cve.org/CVERecord?id=CVE-2024-4067 Référence CVE CVE-2024-4068 https://www.cve.org/CVERecord?id=CVE-2024-4068 Référence CVE CVE-2024-40924 https://www.cve.org/CVERecord?id=CVE-2024-40924 Référence CVE CVE-2024-40961 https://www.cve.org/CVERecord?id=CVE-2024-40961 Référence CVE CVE-2024-40983 https://www.cve.org/CVERecord?id=CVE-2024-40983 Référence CVE CVE-2024-40984 https://www.cve.org/CVERecord?id=CVE-2024-40984 Référence CVE CVE-2024-41009 https://www.cve.org/CVERecord?id=CVE-2024-41009 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41066 https://www.cve.org/CVERecord?id=CVE-2024-41066 Référence CVE CVE-2024-41092 https://www.cve.org/CVERecord?id=CVE-2024-41092 Référence CVE CVE-2024-41093 https://www.cve.org/CVERecord?id=CVE-2024-41093 Référence CVE CVE-2024-41942 https://www.cve.org/CVERecord?id=CVE-2024-41942 Référence CVE CVE-2024-42070 https://www.cve.org/CVERecord?id=CVE-2024-42070 Référence CVE CVE-2024-42079 https://www.cve.org/CVERecord?id=CVE-2024-42079 Référence CVE CVE-2024-42244 https://www.cve.org/CVERecord?id=CVE-2024-42244 Référence CVE CVE-2024-42284 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-36979 Référence CVE CVE-2024-38589 https://www.cve.org/CVERecord?id=CVE-2024-38589 Référence CVE CVE-2024-39282 https://www.cve.org/CVERecord?id=CVE-2024-39282 Référence CVE CVE-2024-39480 https://www.cve.org/CVERecord?id=CVE-2024-39480 Référence CVE CVE-2024-40909 https://www.cve.org/CVERecord?id=CVE-2024-40909 Référence CVE CVE-2024-40920 https://www.cve.org/CVERecord?id=CVE-2024-40920 Référence CVE CVE-2024-40921 https://www.cve.org/CVERecord?id=CVE-2024-40921 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-41013 https://www.cve.org/CVERecord?id=CVE-2024-41013 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41057 https://www.cve.org/CVERecord?id=CVE-2024-41057 Référence CVE CVE-2024-41059 https://www.cve.org/CVERecord?id=CVE-2024-41059 Référence CVE CVE-2024-42133 https://www.cve.org/CVERecord?id=CVE-2024-42133 Référence CVE CVE-2024-42232 https://www.cve.org/CVERecord?id=CVE-2024-42232 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-43913 https://www.cve.org/CVERecord?id=CVE-2024-43913 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44996 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-35950 Référence CVE CVE-2024-36899 https://www.cve.org/CVERecord?id=CVE-2024-36899 Référence CVE CVE-2024-36904 https://www.cve.org/CVERecord?id=CVE-2024-36904 Référence CVE CVE-2024-36908 https://www.cve.org/CVERecord?id=CVE-2024-36908 Référence CVE CVE-2024-36915 https://www.cve.org/CVERecord?id=CVE-2024-36915 Référence CVE CVE-2024-36964 https://www.cve.org/CVERecord?id=CVE-2024-36964 Référence CVE CVE-2024-39480 https://www.cve.org/CVERecord?id=CVE-2024-39480 Référence CVE CVE-2024-40909 https://www.cve.org/CVERecord?id=CVE-2024-40909 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41059 https://www.cve.org/CVERecord?id=CVE-2024-41059 Référence CVE CVE-2024-41087 https://www.cve.org/CVERecord?id=CVE-2024-41087 Référence CVE CVE-2024-42133 https://www.cve.org/CVERecord?id=CVE-2024-42133 Référence CVE CVE-2024-42232 https://www.cve.org/CVERecord?id=CVE-2024-42232 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-47666 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-35950 Référence CVE CVE-2024-36899 https://www.cve.org/CVERecord?id=CVE-2024-36899 Référence CVE CVE-2024-36904 https://www.cve.org/CVERecord?id=CVE-2024-36904 Référence CVE CVE-2024-36908 https://www.cve.org/CVERecord?id=CVE-2024-36908 Référence CVE CVE-2024-36915 https://www.cve.org/CVERecord?id=CVE-2024-36915 Référence CVE CVE-2024-36964 https://www.cve.org/CVERecord?id=CVE-2024-36964 Référence CVE CVE-2024-39480 https://www.cve.org/CVERecord?id=CVE-2024-39480 Référence CVE CVE-2024-40909 https://www.cve.org/CVERecord?id=CVE-2024-40909 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41059 https://www.cve.org/CVERecord?id=CVE-2024-41059 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-49854 https://www.cve.org/CVERecord?id=CVE-2024-49854 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49915 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40973 Référence CVE CVE-2024-41011 https://www.cve.org/CVERecord?id=CVE-2024-41011 Référence CVE CVE-2024-41012 https://www.cve.org/CVERecord?id=CVE-2024-41012 Référence CVE CVE-2024-41015 https://www.cve.org/CVERecord?id=CVE-2024-41015 Référence CVE CVE-2024-41016 https://www.cve.org/CVERecord?id=CVE-2024-41016 Référence CVE CVE-2024-41017 https://www.cve.org/CVERecord?id=CVE-2024-41017 Référence CVE CVE-2024-41019 https://www.cve.org/CVERecord?id=CVE-2024-41019 Référence CVE CVE-2024-41020 https://www.cve.org/CVERecord?id=CVE-2024-41020 Référence CVE CVE-2024-41022 https://www.cve.org/CVERecord?id=CVE-2024-41022 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41059 https://www.cve.org/CVERecord?id=CVE-2024-41059 Référence CVE CVE-2024-41060 https://www.cve.org/CVERecord?id=CVE-2024-41060 Référence CVE CVE-2024-41063 https://www.cve.org/CVERecord?id=CVE-2024-41063 Référence CVE CVE-2024-41064 https://www.cve.org/CVERecord?id=CVE-2024-41064 Référence CVE CVE-2024-41065 https://www.cve.org/CVERecord?id=CVE-2024-41065 Référence CVE CVE-2024-41068 https://www.cve.org/CVERecord?id=CVE-2024-41068 Référence CVE CVE-2024-41070 https://www.cve.org/CVERecord?id=CVE-2024-41070 Référence CVE CVE-2024-41071 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41028 Référence CVE CVE-2024-41030 https://www.cve.org/CVERecord?id=CVE-2024-41030 Référence CVE CVE-2024-41034 https://www.cve.org/CVERecord?id=CVE-2024-41034 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41040 https://www.cve.org/CVERecord?id=CVE-2024-41040 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=CVE-2024-41041 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41044 https://www.cve.org/CVERecord?id=CVE-2024-41044 Référence CVE CVE-2024-41046 https://www.cve.org/CVERecord?id=CVE-2024-41046 Référence CVE CVE-2024-41047 https://www.cve.org/CVERecord?id=CVE-2024-41047 Référence CVE CVE-2024-41048 https://www.cve.org/CVERecord?id=CVE-2024-41048 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41051 https://www.cve.org/CVERecord?id=CVE-2024-41051 Référence CVE CVE-2024-41055 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41032 Référence CVE CVE-2024-41033 https://www.cve.org/CVERecord?id=CVE-2024-41033 Référence CVE CVE-2024-41034 https://www.cve.org/CVERecord?id=CVE-2024-41034 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41037 https://www.cve.org/CVERecord?id=CVE-2024-41037 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=CVE-2024-41041 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41044 https://www.cve.org/CVERecord?id=CVE-2024-41044 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41046 https://www.cve.org/CVERecord?id=CVE-2024-41046 Référence CVE CVE-2024-41047 https://www.cve.org/CVERecord?id=CVE-2024-41047 Référence CVE CVE-2024-41048 https://www.cve.org/CVERecord?id=CVE-2024-41048 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41051 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41032 Référence CVE CVE-2024-41033 https://www.cve.org/CVERecord?id=CVE-2024-41033 Référence CVE CVE-2024-41034 https://www.cve.org/CVERecord?id=CVE-2024-41034 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41037 https://www.cve.org/CVERecord?id=CVE-2024-41037 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=CVE-2024-41041 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41044 https://www.cve.org/CVERecord?id=CVE-2024-41044 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41046 https://www.cve.org/CVERecord?id=CVE-2024-41046 Référence CVE CVE-2024-41047 https://www.cve.org/CVERecord?id=CVE-2024-41047 Référence CVE CVE-2024-41048 https://www.cve.org/CVERecord?id=CVE-2024-41048 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41051 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41032 Référence CVE CVE-2024-41033 https://www.cve.org/CVERecord?id=CVE-2024-41033 Référence CVE CVE-2024-41034 https://www.cve.org/CVERecord?id=CVE-2024-41034 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41037 https://www.cve.org/CVERecord?id=CVE-2024-41037 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=CVE-2024-41041 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41044 https://www.cve.org/CVERecord?id=CVE-2024-41044 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41046 https://www.cve.org/CVERecord?id=CVE-2024-41046 Référence CVE CVE-2024-41047 https://www.cve.org/CVERecord?id=CVE-2024-41047 Référence CVE CVE-2024-41048 https://www.cve.org/CVERecord?id=CVE-2024-41048 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41051 https://www.cve.org/CVERecord?id=

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

ecord?id=CVE-2024-39487 Référence CVE CVE-2024-39495 https://www.cve.org/CVERecord?id=CVE-2024-39495 Référence CVE CVE-2024-39502 https://www.cve.org/CVERecord?id=CVE-2024-39502 Référence CVE CVE-2024-39689 https://www.cve.org/CVERecord?id=CVE-2024-39689 Référence CVE CVE-2024-4032 https://www.cve.org/CVERecord?id=CVE-2024-4032 Référence CVE CVE-2024-4067 https://www.cve.org/CVERecord?id=CVE-2024-4067 Référence CVE CVE-2024-40902 https://www.cve.org/CVERecord?id=CVE-2024-40902 Référence CVE CVE-2024-40927 https://www.cve.org/CVERecord?id=CVE-2024-40927 Référence CVE CVE-2024-40974 https://www.cve.org/CVERecord?id=CVE-2024-40974 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-42232 https://www.cve.org/CVERecord?id=CVE-2024-42232 Référence CVE CVE-2024-42236 https://www.cve.org/CVERecord?id=CVE-2024-42236 Référence CVE CVE-2024-42238 https://www.cve.org/CVERecord?id=CVE-2024-42238 Référence CVE CVE-2024-42244 https://www.cve.org/CVERecord?id=CVE-2024-42244 Référence CVE CVE-2024-42247 https://www.cve.org/CVERecord?id=CVE-2024-42247 Référence CVE CVE-2024-42251 https://www.cve.org/CVERecord?id=CVE-2024-42251 Référence CVE CVE-2024-42252 https://www.cve.org/CVERecord?id=CVE-2024-42252 Référence CVE CVE-2024-42254 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41032 Référence CVE CVE-2024-41033 https://www.cve.org/CVERecord?id=CVE-2024-41033 Référence CVE CVE-2024-41034 https://www.cve.org/CVERecord?id=CVE-2024-41034 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41037 https://www.cve.org/CVERecord?id=CVE-2024-41037 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=CVE-2024-41041 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41044 https://www.cve.org/CVERecord?id=CVE-2024-41044 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41046 https://www.cve.org/CVERecord?id=CVE-2024-41046 Référence CVE CVE-2024-41047 https://www.cve.org/CVERecord?id=CVE-2024-41047 Référence CVE CVE-2024-41048 https://www.cve.org/CVERecord?id=CVE-2024-41048 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41051 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-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=CVE-2024-40924 Référence CVE CVE-2024-40961 https://www.cve.org/CVERecord?id=CVE-2024-40961 Référence CVE CVE-2024-40983 https://www.cve.org/CVERecord?id=CVE-2024-40983 Référence CVE CVE-2024-40984 https://www.cve.org/CVERecord?id=CVE-2024-40984 Référence CVE CVE-2024-41009 https://www.cve.org/CVERecord?id=CVE-2024-41009 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41066 https://www.cve.org/CVERecord?id=CVE-2024-41066 Référence CVE CVE-2024-41092 https://www.cve.org/CVERecord?id=CVE-2024-41092 Référence CVE CVE-2024-41093 https://www.cve.org/CVERecord?id=CVE-2024-41093 Référence CVE CVE-2024-42070 https://www.cve.org/CVERecord?id=CVE-2024-42070 Référence CVE CVE-2024-42079 https://www.cve.org/CVERecord?id=CVE-2024-42079 Référence CVE CVE-2024-42244 https://www.cve.org/CVERecord?id=CVE-2024-42244 Référence CVE CVE-2024-42284 https://www.cve.org/CVERecord?id=CVE-2024-42284 Référence CVE CVE-2024-42292 https://www.cve.org/CVERecord?id=

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

S DLA-3912-1 du 07 octobre 2024 https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html Référence CVE CVE-2021-3669 https://www.cve.org/CVERecord?id=CVE-2021-3669 Référence CVE CVE-2022-48733 https://www.cve.org/CVERecord?id=CVE-2022-48733 Référence CVE CVE-2023-31083 https://www.cve.org/CVERecord?id=CVE-2023-31083 Référence CVE CVE-2023-52889 https://www.cve.org/CVERecord?id=CVE-2023-52889 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-38577 https://www.cve.org/CVERecord?id=CVE-2024-38577 Référence CVE CVE-2024-41011 https://www.cve.org/CVERecord?id=CVE-2024-41011 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41098 https://www.cve.org/CVERecord?id=CVE-2024-41098 Référence CVE CVE-2024-42114 https://www.cve.org/CVERecord?id=CVE-2024-42114 Référence CVE CVE-2024-42228 https://www.cve.org/CVERecord?id=CVE-2024-42228 Référence CVE CVE-2024-42246 https://www.cve.org/CVERecord?id=CVE-2024-42246 Référence CVE CVE-2024-42259 https://www.cve.org/CVERecord?id=CVE-2024-42259 Référence CVE CVE-2024-42265 https://www.cve.org/CVERecord?id=CVE-2024-42265 Référence CVE CVE-2024-42272 https://www.cve.org/CVERecord?id=CVE-2024-42272 Référence CVE CVE-2024-42276 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41009 Référence CVE CVE-2024-41011 https://www.cve.org/CVERecord?id=CVE-2024-41011 Référence CVE CVE-2024-41016 https://www.cve.org/CVERecord?id=CVE-2024-41016 Référence CVE CVE-2024-41020 https://www.cve.org/CVERecord?id=CVE-2024-41020 Référence CVE CVE-2024-41022 https://www.cve.org/CVERecord?id=CVE-2024-41022 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41056 https://www.cve.org/CVERecord?id=CVE-2024-41056 Référence CVE CVE-2024-41060 https://www.cve.org/CVERecord?id=CVE-2024-41060 Référence CVE CVE-2024-41062 https://www.cve.org/CVERecord?id=CVE-2024-41062 Référence CVE CVE-2024-41065 https://www.cve.org/CVERecord?id=CVE-2024-41065 Référence CVE CVE-2024-41068 https://www.cve.org/CVERecord?id=CVE-2024-41068 Référence CVE CVE-2024-41073 https://www.cve.org/CVERecord?id=CVE-2024-41073 Référence CVE CVE-2024-41079 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41028 Référence CVE CVE-2024-41032 https://www.cve.org/CVERecord?id=CVE-2024-41032 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41037 https://www.cve.org/CVERecord?id=CVE-2024-41037 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41040 https://www.cve.org/CVERecord?id=CVE-2024-41040 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=CVE-2024-41041 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41044 https://www.cve.org/CVERecord?id=CVE-2024-41044 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41048 https://www.cve.org/CVERecord?id=CVE-2024-41048 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41051 https://www.cve.org/CVERecord?id=CVE-2024-41051 Référence CVE CVE-2024-41056 https://www.cve.org/CVERecord?id=CVE-2024-41056 Référence CVE CVE-2024-41057 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028865Linux の 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: < 3.13, 4.19.320 ≤ 4.19.*, 5.4.282 ≤ 5.4.*, 5.10.224 ≤ 5.10.*, 5.15.165 ≤ 5.15.*, 6.1.105 ≤ 6.1.*, 6.6.46 ≤ 6.6.*, 6.9.10 ≤ 6.9.*, 6.10 ≤ *
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 29 Jul 2024 · Last source change 11 May 2026, 20:25 UTC · CWE-787 · Out-of-bounds Write

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-39308
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗

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

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