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

mlxsw: spectrum_acl_tcam: Fix possible use-after-free during rehash

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 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.58% 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.

17 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 13 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.8.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.90-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-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-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.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 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-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.

2 current
CVE-2024-35854 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: mlxsw: spectrum_acl_tcam: Fix possible use-after-free during rehash
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
In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix possible use-after-free during rehash The Linux kernel CVE team has assigned CVE-2024-35854 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35854-d17b@gregkh/T
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.
SSA-613116 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-613116: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.1
2 known affected

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

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix possible use-after-free during rehash The rehash delayed work migrates filters from one region to another according to the number of available credits. The migrated from region is destroyed at the end of the work if the number of credits is non-negative as the assumption is that this is indicative of migration being complete. This assumption is incorrect as a non-negative number of credits can also be the result of a failed migration. The destruction of a region that still has filters referencing it can result in a use-after-free [1]. Fix by not destroying the region if migration failed. [1] BUG: KASAN: slab-use-after-free in mlxsw_sp_acl_ctcam_region_entry_remove+0x21d/0x230 Read of size 8 at addr ffff8881735319e8 by task kworker/0:31/3858 CPU: 0 PID: 3858 Comm: kworker/0:31 Tainted: G W 6.9.0-rc2-custom-00782-gf2275c2157d8 #5 Hardware name: Mellanox Technologies Ltd. MSN3700/VMOD0005, BIOS 5.11 01/06/2019 Workqueue: mlxsw_core mlxsw_sp_acl_tcam_vregion_rehash_work Call Trace: dump_stack_lvl+0xc6/0x120 print_report+0xce/0x670 kasan_report+0xd7/0x110 mlxsw_sp_acl_ctcam_region_entry_remove+0x21d/0x230 mlxsw_sp_acl_ctcam_entry_del+0x2e/0x70 mlxsw_sp_acl_atcam_entry_del+0x81/0x210 mlxsw_sp_acl_tcam_vchunk_migrate_all+0x3cd/0xb50 mlxsw_sp_acl_tcam_vregion_rehash_work+0x157/0x1300 process_one_work+0x8eb/0x19b0 worker_thread+0x6c9/0xf70 kthread+0x2c9/0x3b0 ret_from_fork+0x4d/0x80 ret_from_fork_asm+0x1a/0x30 Allocated by task 174: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x8f/0xa0 __kmalloc+0x19c/0x360 mlxsw_sp_acl_tcam_region_create+0xdf/0x9c0 mlxsw_sp_acl_tcam_vregion_rehash_work+0x954/0x1300 process_one_work+0x8eb/0x19b0 worker_thread+0x6c9/0xf70 kthread+0x2c9/0x3b0 ret_from_fork+0x4d/0x80 ret_from_fork_asm+0x1a/0x30 Freed by task 7: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 poison_slab_object+0x102/0x170 __kasan_slab_free+0x14/0x30 kfree+0xc1/0x290 mlxsw_sp_acl_tcam_region_destroy+0x272/0x310 mlxsw_sp_acl_tcam_vregion_rehash_work+0x731/0x1300 process_one_work+0x8eb/0x19b0 worker_thread+0x6c9/0xf70 kthread+0x2c9/0x3b0 ret_from_fork+0x4d/0x80 ret_from_fork_asm+0x1a/0x30
Remediation
Update to V3.1 or later version
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-35572

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: mlxsw: spectrum_acl_tcam: Fix possible use-after-free during rehash The rehash delayed work migrates filters from one region to another according to the number of available credits. The migrated from region is destroyed at the end of the work if the number of credits is non-negative as the assumption is that this is indicative of migration being complete. This assumption is incorrect as a non-negative number of credits can also be the result of a failed migration. The destruction of a region that still has filters referencing it can result in a use-after-free [1]. Fix by not destroying the region if migration failed. [1] BUG: KASAN: slab-use-after-free in mlxsw_sp_acl_ctcam_region_entry_remove+0x21d/0x230 Read of size 8 at addr ffff8881735319e8 by task kworker/0:31/3858 CPU: 0 PID: 3858 Comm: kworker/0:31 Tainted: G W 6.9.0-rc2-custom-00782-gf2275c2157d8 #5 Hardware name: Mellanox Technologies Ltd. MSN3700/VMOD0005, BIOS 5.11 01/06/2019 Workqueue: mlxsw_core mlxsw_sp_acl_tcam_vregion_rehash_work Call Trace: <TASK> dump_stack_lvl+0xc6/0x120 print_report+0xce/0x670 kasan_report+0xd7/0x110 mlxsw_sp_acl_ctcam_region_entry_remove+0x21d/0x230 mlxsw_sp_acl_ctcam_entry_del+0x2e/0x70 mlxsw_sp_acl_atcam_entry_del+0x81/0x210 mlxsw_sp_acl_tcam_vchunk_migrate_all+0x3cd/0xb50 mlxsw_sp_acl_tcam_vregion_rehash_work+0x157/0x1300 process_one_work+0x8eb/0x19b0 worker_thread+0x6c9/0xf70 kthread+0x2c9/0x3b0 ret_from_fork+0x4d/0x80 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 174: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x8f/0xa0 __kmalloc+0x19c/0x360 mlxsw_sp_acl_tcam_region_create+0xdf/0x9c0 mlxsw_sp_acl_tcam_vregion_rehash_work+0x954/0x1300 process_one_work+0x8eb/0x19b0 worker_thread+0x6c9/0xf70 kthread+0x2c9/0x3b0 ret_from_fork+0x4d/0x80 ret_from_fork_asm+0x1a/0x30 Freed by task 7: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 poison_slab_object+0x102/0x170 __kasan_slab_free+0x14/0x30 kfree+0xc1/0x290 mlxsw_sp_acl_tcam_region_destroy+0x272/0x310 mlxsw_sp_acl_tcam_vregion_rehash_work+0x731/0x1300 process_one_work+0x8eb/0x19b0 worker_thread+0x6c9/0xf70 kthread+0x2c9/0x3b0 ret_from_fork+0x4d/0x80 ret_from_fork_asm+0x1a/0x30

What

In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix possible use-after-free during rehash The rehash delayed work migrates filters from one region to another according to the number of available credits. The migrated from region is destroyed at the end of the work if the number of credits is non-negative as the assumption is that this is indicative of migration being complete. This assumption is incorrect as a non-negative number of credits can also be the result of a failed migration. The destruction of a region that still has filters referencing it can result in a use-after-free [1]. Fix by not destroying the region if migration failed. [1] BUG: KASAN: slab-use-after-free in mlxsw_sp_acl_ctcam_region_entry_remove+0x21d/0x230 Read of size 8 at addr ffff8881735319e8 by task kworker/0:31/3858 CPU: 0 PID: 3858 Comm: kworker/0:31 Tainted: G W 6.9.0-rc2-custom-00782-gf2275c2157d8 #5 Hardware name: Mellanox Technologies Ltd. MSN3700/VMOD0005, BIOS 5.11 01/06/2019 Workqueue: mlxsw_core mlxsw_sp_acl_tcam_vregion_rehash_work Call Trace: <TASK> dump_stack_lvl+0xc6/0x120 print_report+0xce/0x670 kasan_report+0xd7/0x110 mlxsw_sp_acl_ctcam_region_entry_remove+0x21d/0x230 mlxsw_sp_acl_ctcam_entry_del+0x2e/0x70 mlxsw_sp_acl_atcam_entry_del+0x81/0x210 mlxsw_sp_acl_tcam_vchunk_migrate_all+0x3cd/0xb50 mlxsw_sp_acl_tcam_vregion_rehash_work+0x157/0x1300 process_one_work+0x8eb/0x19b0 worker_thread+0x6c9/0xf70 kthread+0x2c9/0x3b0 ret_from_fork+0x4d/0x80 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 174: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x8f/0xa0 __kmalloc+0x19c/0x360 mlxsw_sp_acl_tcam_region_create+0xdf/0x9c0 mlxsw_sp_acl_tcam_vregion_rehash_work+0x954/0x1300 process_one_work+0x8eb/0x19b0 worker_thread+0x6c9/0xf70 kthread+0x2c9/0x3b0 ret_from_fork+0x4d/0x80 ret_from_fork_asm+0x1a/0x30 Freed by task 7: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 poison_slab_object+0x102/0x170 __kasan_slab_free+0x14/0x30 kfree+0xc1/0x290 mlxsw_sp_acl_tcam_region_destroy+0x272/0x310 mlxsw_sp_acl_tcam_vregion_rehash_work+0x731/0x1300 process_one_work+0x8eb/0x19b0 worker_thread+0x6c9/0xf70 kthread+0x2c9/0x3b0 ret_from_fork+0x4d/0x80 ret_from_fork_asm+0x1a/0x30

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix possible use-after-free during rehash The rehash delayed work migrates filters from one region to another according to the number of available credits. The migrated from region is destroyed at the end of the work if the number of credits is non-negative as the assumption is that this is indicative of migration being complete. This assumption is incorrect as a non-negative number of credits can also be the result of a failed migration. The destruction of a region that still has filters referencing it can result in a use-after-free [1]. Fix by not destroying the region if migration failed. [1] BUG: KASAN: slab-use-after-free in mlxsw_sp_acl_ctcam_region_entry_remove+0x21d/0x230 Read of size 8 at addr ffff8881735319e8 by task kworker/0:31/3858 CPU: 0 PID: 3858 Comm: kworker/0:31 Tainted: G W 6.9.0-rc2-custom-00782-gf2275c2157d8 #5 Hardware name: Mellanox Technologies Ltd. MSN3700/VMOD0005, BIOS 5.11 01/06/2019 Workqueue: mlxsw_core mlxsw_sp_acl_tcam_vregion_rehash_work Call Trace: <TASK> dump_stack_lvl+0xc6/0x120 print_report+0xce/0x670 kasan_report+0xd7/0x110 mlxsw_sp_acl_ctcam_region_entry_remove+0x21d/0x230 mlxsw_sp_acl_ctcam_entry_del+0x2e/0x70 mlxsw_sp_acl_atcam_entry_del+0x81/0x210 mlxsw_sp_acl_tcam_vchunk_migrate_all+0x3cd/0xb50 mlxsw_sp_acl_tcam_vregion_rehash_work+0x157/0x1300 process_one_work+0x8eb/0x19b0 worker_thread+0x6c9/0xf70 kthread+0x2c9/0x3b0 ret_from_fork+0x4d/0x80 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 174: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x8f/0xa0 __kmalloc+0x19c/0x360 mlxsw_sp_acl_tcam_region_create+0xdf/0x9c0 mlxsw_sp_acl_tcam_vregion_rehash_work+0x954/0x1300 process_one_work+0x8eb/0x19b0 worker_thread+0x6c9/0xf70 kthread+0x2c9/0x3b0 ret_from_fork+0x4d/0x80 ret_from_fork_asm+0x1a/0x30 Freed by task 7: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 poison_slab_object+0x102/0x170 __kasan_slab_free+0x14/0x30 kfree+0xc1/0x290 mlxsw_sp_acl_tcam_region_destroy+0x272/0x310 mlxsw_sp_acl_tcam_vregion_rehash_work+0x731/0x1300 process_one_work+0x8eb/0x19b0 worker_thread+0x6c9/0xf70 kthread+0x2c9/0x3b0 ret_from_fork+0x4d/0x80 ret_from_fork_asm+0x1a/0x30

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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.
CWE-416
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-1905IBM QRadar SIEM: Mehrere Schwachstellen

Ein entfernter, anonymer oder lokaler Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, eine Man-in-the-Middle-Situation zu schaffen, Sicherheitsmaßnahmen zu umgehen oder eine Denial-of-Service-Situation zu schaffen.

Official advisory ↗
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-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=CVE-2024-35884 Référence CVE CVE-2024-35888 https://www.cve.org/CVERecord?id=CVE-2024-35888 Référence CVE CVE-2024-35890 https://www.cve.org/CVERecord?id=CVE-2024-35890 Référence CVE CVE-2024-35893 https://www.cve.org/CVERecord?id=CVE-2024-35893 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=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0253Multiples 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 à distance, une atteinte à l'intégrité des données et un contournement de la politique de sécurité.

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

d?id=CVE-2024-31880 Référence CVE CVE-2024-31881 https://www.cve.org/CVERecord?id=CVE-2024-31881 Référence CVE CVE-2024-32487 https://www.cve.org/CVERecord?id=CVE-2024-32487 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 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-35845 https://www.cve.org/CVERecord?id=CVE-2024-35845 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-35888 https://www.cve.org/CVERecord?id=CVE-2024-35888 Référence CVE CVE-2024-35890 https://www.cve.org/CVERecord?id=CVE-2024-35890 Référence CVE CVE-2024-35958 https://www.cve.org/CVERecord?id=CVE-2024-35958 Référence CVE CVE-2024-35959 https://www.cve.org/CVERecord?id=CVE-2024-35959 Référence CVE CVE-2024-35960 https://www.cve.org/CVERecord?id=CVE-2024-35960 Référence CVE CVE-2024-36004 https://www.cve.org/CVERecord?id=CVE-2024-36004 Référence CVE CVE-2024-36007 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27049 Référence CVE CVE-2024-27050 https://www.cve.org/CVERecord?id=CVE-2024-27050 Référence CVE CVE-2024-27079 https://www.cve.org/CVERecord?id=CVE-2024-27079 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-27403 https://www.cve.org/CVERecord?id=CVE-2024-27403 Référence CVE CVE-2024-27433 https://www.cve.org/CVERecord?id=CVE-2024-27433 Référence CVE CVE-2024-27437 https://www.cve.org/CVERecord?id=CVE-2024-27437 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-35817 https://www.cve.org/CVERecord?id=CVE-2024-35817 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-35897 https://www.cve.org/CVERecord?id=CVE-2024-35897 Référence CVE CVE-2024-35902 https://www.cve.org/CVERecord?id=CVE-2024-35902 Référence CVE CVE-2024-35913 https://www.cve.org/CVERecord?id=CVE-2024-35913 Référence CVE CVE-2024-35939 https://www.cve.org/CVERecord?id=CVE-2024-35939 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=CVE-2024-35950 Référence CVE CVE-2024-36270 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35822 Référence CVE CVE-2024-35823 https://www.cve.org/CVERecord?id=CVE-2024-35823 Référence CVE CVE-2024-35825 https://www.cve.org/CVERecord?id=CVE-2024-35825 Référence CVE CVE-2024-35847 https://www.cve.org/CVERecord?id=CVE-2024-35847 Référence CVE CVE-2024-35848 https://www.cve.org/CVERecord?id=CVE-2024-35848 Référence CVE CVE-2024-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 Référence CVE CVE-2024-35851 https://www.cve.org/CVERecord?id=CVE-2024-35851 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-35857 https://www.cve.org/CVERecord?id=CVE-2024-35857 Référence CVE CVE-2024-35871 https://www.cve.org/CVERecord?id=CVE-2024-35871 Référence CVE CVE-2024-35872 https://www.cve.org/CVERecord?id=CVE-2024-35872 Référence CVE CVE-2024-35877 https://www.cve.org/CVERecord?id=CVE-2024-35877 Référence CVE CVE-2024-35879 https://www.cve.org/CVERecord?id=CVE-2024-35879 Référence CVE CVE-2024-35884 https://www.cve.org/CVERecord?id=CVE-2024-35884 Référence CVE CVE-2024-35885 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-27016 Référence CVE CVE-2024-27024 https://www.cve.org/CVERecord?id=CVE-2024-27024 Référence CVE CVE-2024-27049 https://www.cve.org/CVERecord?id=CVE-2024-27049 Référence CVE CVE-2024-27050 https://www.cve.org/CVERecord?id=CVE-2024-27050 Référence CVE CVE-2024-27079 https://www.cve.org/CVERecord?id=CVE-2024-27079 Référence CVE CVE-2024-27403 https://www.cve.org/CVERecord?id=CVE-2024-27403 Référence CVE CVE-2024-27433 https://www.cve.org/CVERecord?id=CVE-2024-27433 Référence CVE CVE-2024-27437 https://www.cve.org/CVERecord?id=CVE-2024-27437 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 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-35897 https://www.cve.org/CVERecord?id=CVE-2024-35897 Référence CVE CVE-2024-35902 https://www.cve.org/CVERecord?id=CVE-2024-35902 Référence CVE CVE-2024-35913 https://www.cve.org/CVERecord?id=CVE-2024-35913 Référence CVE CVE-2024-35915 https://www.cve.org/CVERecord?id=CVE-2024-35915 Référence CVE CVE-2024-35933 https://www.cve.org/CVERecord?id=CVE-2024-35933 Référence CVE CVE-2024-35939 https://www.cve.org/CVERecord?id=CVE-2024-35939 Référence CVE CVE-2024-35945 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0741Multiples vulnérabilités dans Juniper Secure Analytics

d?id=CVE-2024-33602 Référence CVE CVE-2024-34064 https://www.cve.org/CVERecord?id=CVE-2024-34064 Référence CVE CVE-2024-34750 https://www.cve.org/CVERecord?id=CVE-2024-34750 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 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-35845 https://www.cve.org/CVERecord?id=CVE-2024-35845 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-35888 https://www.cve.org/CVERecord?id=CVE-2024-35888 Référence CVE CVE-2024-35890 https://www.cve.org/CVERecord?id=CVE-2024-35890 Référence CVE CVE-2024-35958 https://www.cve.org/CVERecord?id=CVE-2024-35958 Référence CVE CVE-2024-35959 https://www.cve.org/CVERecord?id=CVE-2024-35959 Référence CVE CVE-2024-35960 https://www.cve.org/CVERecord?id=CVE-2024-35960 Référence CVE CVE-2024-36004 https://www.cve.org/CVERecord?id=CVE-2024-36004 Référence CVE CVE-2024-36007 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0720Multiples vulnérabilités dans IBM QRadar SIEM

d?id=CVE-2024-27397 Référence CVE CVE-2024-27410 https://www.cve.org/CVERecord?id=CVE-2024-27410 Référence CVE CVE-2024-34750 https://www.cve.org/CVERecord?id=CVE-2024-34750 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 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-35845 https://www.cve.org/CVERecord?id=CVE-2024-35845 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-35888 https://www.cve.org/CVERecord?id=CVE-2024-35888 Référence CVE CVE-2024-35890 https://www.cve.org/CVERecord?id=CVE-2024-35890 Référence CVE CVE-2024-35958 https://www.cve.org/CVERecord?id=CVE-2024-35958 Référence CVE CVE-2024-35959 https://www.cve.org/CVERecord?id=CVE-2024-35959 Référence CVE CVE-2024-35960 https://www.cve.org/CVERecord?id=CVE-2024-35960 Référence CVE CVE-2024-36004 https://www.cve.org/CVERecord?id=CVE-2024-36004 Référence CVE CVE-2024-36007 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35843 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-35848 https://www.cve.org/CVERecord?id=CVE-2024-35848 Référence CVE CVE-2024-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 Référence CVE CVE-2024-35850 https://www.cve.org/CVERecord?id=CVE-2024-35850 Référence CVE CVE-2024-35851 https://www.cve.org/CVERecord?id=CVE-2024-35851 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-35857 https://www.cve.org/CVERecord?id=CVE-2024-35857 Référence CVE CVE-2024-35860 https://www.cve.org/CVERecord?id=CVE-2024-35860 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-35865 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-33621 Référence CVE CVE-2024-35846 https://www.cve.org/CVERecord?id=CVE-2024-35846 Référence CVE CVE-2024-35847 https://www.cve.org/CVERecord?id=CVE-2024-35847 Référence CVE CVE-2024-35848 https://www.cve.org/CVERecord?id=CVE-2024-35848 Référence CVE CVE-2024-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 Référence CVE CVE-2024-35850 https://www.cve.org/CVERecord?id=CVE-2024-35850 Référence CVE CVE-2024-35851 https://www.cve.org/CVERecord?id=CVE-2024-35851 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-35856 https://www.cve.org/CVERecord?id=CVE-2024-35856 Référence CVE CVE-2024-35857 https://www.cve.org/CVERecord?id=CVE-2024-35857 Référence CVE CVE-2024-35858 https://www.cve.org/CVERecord?id=CVE-2024-35858 Référence CVE CVE-2024-35859 https://www.cve.org/CVERecord?id=CVE-2024-35859 Référence CVE CVE-2024-35947 https://www.cve.org/CVERecord?id=CVE-2024-35947 Référence CVE CVE-2024-35949 https://www.cve.org/CVERecord?id=CVE-2024-35949 Référence CVE CVE-2024-35976 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35819 Référence CVE CVE-2024-35827 https://www.cve.org/CVERecord?id=CVE-2024-35827 Référence CVE CVE-2024-35828 https://www.cve.org/CVERecord?id=CVE-2024-35828 Référence CVE CVE-2024-35831 https://www.cve.org/CVERecord?id=CVE-2024-35831 Référence CVE CVE-2024-35835 https://www.cve.org/CVERecord?id=CVE-2024-35835 Référence CVE CVE-2024-35837 https://www.cve.org/CVERecord?id=CVE-2024-35837 Référence CVE CVE-2024-35843 https://www.cve.org/CVERecord?id=CVE-2024-35843 Référence CVE CVE-2024-35848 https://www.cve.org/CVERecord?id=CVE-2024-35848 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-35857 https://www.cve.org/CVERecord?id=CVE-2024-35857 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-35864 https://www.cve.org/CVERecord?id=CVE-2024-35864 Référence CVE CVE-2024-35869 https://www.cve.org/CVERecord?id=CVE-2024-35869 Référence CVE CVE-2024-35878 https://www.cve.org/CVERecord?id=CVE-2024-35878 Référence CVE CVE-2024-35880 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27020 Référence CVE CVE-2024-27025 https://www.cve.org/CVERecord?id=CVE-2024-27025 Référence CVE CVE-2024-27064 https://www.cve.org/CVERecord?id=CVE-2024-27064 Référence CVE CVE-2024-27065 https://www.cve.org/CVERecord?id=CVE-2024-27065 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-27402 https://www.cve.org/CVERecord?id=CVE-2024-27402 Référence CVE CVE-2024-27404 https://www.cve.org/CVERecord?id=CVE-2024-27404 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 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-35890 https://www.cve.org/CVERecord?id=CVE-2024-35890 Référence CVE CVE-2024-35893 https://www.cve.org/CVERecord?id=CVE-2024-35893 Référence CVE CVE-2024-35899 https://www.cve.org/CVERecord?id=CVE-2024-35899 Référence CVE CVE-2024-35908 https://www.cve.org/CVERecord?id=CVE-2024-35908 Référence CVE CVE-2024-35934 https://www.cve.org/CVERecord?id=CVE-2024-35934 Référence CVE CVE-2024-35942 https://www.cve.org/CVERecord?id=CVE-2024-35942 Référence CVE CVE-2024-35950 https://www.cve.org/CVERecord?id=CVE-2024-35950 Référence CVE CVE-2024-36003 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35833 Référence CVE CVE-2024-35846 https://www.cve.org/CVERecord?id=CVE-2024-35846 Référence CVE CVE-2024-35847 https://www.cve.org/CVERecord?id=CVE-2024-35847 Référence CVE CVE-2024-35848 https://www.cve.org/CVERecord?id=CVE-2024-35848 Référence CVE CVE-2024-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 Référence CVE CVE-2024-35850 https://www.cve.org/CVERecord?id=CVE-2024-35850 Référence CVE CVE-2024-35851 https://www.cve.org/CVERecord?id=CVE-2024-35851 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-35856 https://www.cve.org/CVERecord?id=CVE-2024-35856 Référence CVE CVE-2024-35857 https://www.cve.org/CVERecord?id=CVE-2024-35857 Référence CVE CVE-2024-35858 https://www.cve.org/CVERecord?id=CVE-2024-35858 Référence CVE CVE-2024-35859 https://www.cve.org/CVERecord?id=CVE-2024-35859 Référence CVE CVE-2024-35947 https://www.cve.org/CVERecord?id=CVE-2024-35947 Référence CVE CVE-2024-35949 https://www.cve.org/CVERecord?id=CVE-2024-35949 Référence CVE CVE-2024-35976 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35829 Référence CVE CVE-2024-35830 https://www.cve.org/CVERecord?id=CVE-2024-35830 Référence CVE CVE-2024-35844 https://www.cve.org/CVERecord?id=CVE-2024-35844 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-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 Référence CVE CVE-2024-35851 https://www.cve.org/CVERecord?id=CVE-2024-35851 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-35857 https://www.cve.org/CVERecord?id=CVE-2024-35857 Référence CVE CVE-2024-35860 https://www.cve.org/CVERecord?id=CVE-2024-35860 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-35865 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35825 Référence CVE CVE-2024-35828 https://www.cve.org/CVERecord?id=CVE-2024-35828 Référence CVE CVE-2024-35830 https://www.cve.org/CVERecord?id=CVE-2024-35830 Référence CVE CVE-2024-35833 https://www.cve.org/CVERecord?id=CVE-2024-35833 Référence CVE CVE-2024-35847 https://www.cve.org/CVERecord?id=CVE-2024-35847 Référence CVE CVE-2024-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 Référence CVE CVE-2024-35851 https://www.cve.org/CVERecord?id=CVE-2024-35851 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-35857 https://www.cve.org/CVERecord?id=CVE-2024-35857 Référence CVE CVE-2024-35860 https://www.cve.org/CVERecord?id=CVE-2024-35860 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-35865 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35825 Référence CVE CVE-2024-35828 https://www.cve.org/CVERecord?id=CVE-2024-35828 Référence CVE CVE-2024-35830 https://www.cve.org/CVERecord?id=CVE-2024-35830 Référence CVE CVE-2024-35833 https://www.cve.org/CVERecord?id=CVE-2024-35833 Référence CVE CVE-2024-35847 https://www.cve.org/CVERecord?id=CVE-2024-35847 Référence CVE CVE-2024-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 Référence CVE CVE-2024-35851 https://www.cve.org/CVERecord?id=CVE-2024-35851 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-35857 https://www.cve.org/CVERecord?id=CVE-2024-35857 Référence CVE CVE-2024-35860 https://www.cve.org/CVERecord?id=CVE-2024-35860 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-35865 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27393 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-27410 https://www.cve.org/CVERecord?id=CVE-2024-27410 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 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-35845 https://www.cve.org/CVERecord?id=CVE-2024-35845 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-35870 https://www.cve.org/CVERecord?id=CVE-2024-35870 Référence CVE CVE-2024-35888 https://www.cve.org/CVERecord?id=CVE-2024-35888 Référence CVE CVE-2024-35890 https://www.cve.org/CVERecord?id=CVE-2024-35890 Référence CVE CVE-2024-35958 https://www.cve.org/CVERecord?id=CVE-2024-35958 Référence CVE CVE-2024-35959 https://www.cve.org/CVERecord?id=CVE-2024-35959 Référence CVE CVE-2024-35960 https://www.cve.org/CVERecord?id=CVE-2024-35960 Référence CVE CVE-2024-35969 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35833 Référence CVE CVE-2024-35835 https://www.cve.org/CVERecord?id=CVE-2024-35835 Référence CVE CVE-2024-35837 https://www.cve.org/CVERecord?id=CVE-2024-35837 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-35848 https://www.cve.org/CVERecord?id=CVE-2024-35848 Référence CVE CVE-2024-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 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-35871 https://www.cve.org/CVERecord?id=CVE-2024-35871 Référence CVE CVE-2024-35877 https://www.cve.org/CVERecord?id=CVE-2024-35877 Référence CVE CVE-2024-35879 https://www.cve.org/CVERecord?id=CVE-2024-35879 Référence CVE CVE-2024-35884 https://www.cve.org/CVERecord?id=CVE-2024-35884 Référence CVE CVE-2024-35886 https://www.cve.org/CVERecord?id=CVE-2024-35886 Référence CVE CVE-2024-35888 https://www.cve.org/CVERecord?id=CVE-2024-35888 Référence CVE CVE-2024-35893 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35838 Référence CVE CVE-2024-35841 https://www.cve.org/CVERecord?id=CVE-2024-35841 Référence CVE CVE-2024-35842 https://www.cve.org/CVERecord?id=CVE-2024-35842 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-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 Référence CVE CVE-2024-35850 https://www.cve.org/CVERecord?id=CVE-2024-35850 Référence CVE CVE-2024-35851 https://www.cve.org/CVERecord?id=CVE-2024-35851 Référence CVE CVE-2024-35852 https://www.cve.org/CVERecord?id=CVE-2024-35852 Référence CVE CVE-2024-35854 https://www.cve.org/CVERecord?id=CVE-2024-35854 Référence CVE CVE-2024-35860 https://www.cve.org/CVERecord?id=CVE-2024-35860 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-35865 https://www.cve.org/CVERecord?id=CVE-2024-35865 Référence CVE CVE-2024-35866 https://www.cve.org/CVERecord?id=CVE-2024-35866 Référence CVE CVE-2024-35867 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35828 Référence CVE CVE-2024-35829 https://www.cve.org/CVERecord?id=CVE-2024-35829 Référence CVE CVE-2024-35830 https://www.cve.org/CVERecord?id=CVE-2024-35830 Référence CVE CVE-2024-35833 https://www.cve.org/CVERecord?id=CVE-2024-35833 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-35849 https://www.cve.org/CVERecord?id=CVE-2024-35849 Référence CVE CVE-2024-35851 https://www.cve.org/CVERecord?id=CVE-2024-35851 Référence CVE CVE-2024-35852 https://www.cve.org/CVERecord?id=CVE-2024-35852 Référence CVE CVE-2024-35854 https://www.cve.org/CVERecord?id=CVE-2024-35854 Référence CVE CVE-2024-35860 https://www.cve.org/CVERecord?id=CVE-2024-35860 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-35865 https://www.cve.org/CVERecord?id=CVE-2024-35865 Référence CVE CVE-2024-35866 https://www.cve.org/CVERecord?id=CVE-2024-35866 Référence CVE CVE-2024-35867 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-021994Linux の 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
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 17 May 2024 · Last source change 5 Aug 2026, 11:30 UTC · CWE-416 · Use After Free

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-35572
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCISA ADP
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-35572↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-35854 · cve.blacktree.nl