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

ethtool: fail closed if we can't get max channel used in indirection tables

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 172 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.22% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 172 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 16 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.10.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.11-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-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.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
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-46834 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ethtool: fail closed if we can't get max channel used in indirection tables
156 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 8
  • kernel as a component of Red Hat Enterprise Linux 8
  • kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8
  • kernel-core as a component of Red Hat Enterprise Linux 8
  • kernel-cross-headers as a component of Red Hat Enterprise Linux 8
  • kernel-debug as a component of Red Hat Enterprise Linux 8
  • kernel-debug-core as a component of Red Hat Enterprise Linux 8
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8
Summary
A flaw was found in the Linux kernel's ethtool component. This vulnerability occurs when the indirection table contains channels with out-of-bounds identifiers, which can happen if the driver fails to fetch the indirection table or allocate memory. This can lead to a system crash, resulting in a denial of service.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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-42095

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 172 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: ethtool: fail closed if we can't get max channel used in indirection tables Commit 0d1b7d6c9274 ("bnxt: fix crashes when reducing ring count with active RSS contexts") proves that allowing indirection table to contain channels with out of bounds IDs may lead to crashes. Currently the max channel check in the core gets skipped if driver can't fetch the indirection table or when we can't allocate memory. Both of those conditions should be extremely rare but if they do happen we should try to be safe and fail the channel change.

What

In the Linux kernel, the following vulnerability has been resolved: ethtool: fail closed if we can't get max channel used in indirection tables Commit 0d1b7d6c9274 ("bnxt: fix crashes when reducing ring count with active RSS contexts") proves that allowing indirection table to contain channels with out of bounds IDs may lead to crashes. Currently the max channel check in the core gets skipped if driver can't fetch the indirection table or when we can't allocate memory. Both of those conditions should be extremely rare but if they do happen we should try to be safe and fail the channel change.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: ethtool: fail closed if we can't get max channel used in indirection tables Commit 0d1b7d6c9274 ("bnxt: fix crashes when reducing ring count with active RSS contexts") proves that allowing indirection table to contain channels with out of bounds IDs may lead to crashes. Currently the max channel check in the core gets skipped if driver can't fetch the indirection table or when we can't allocate memory. Both of those conditions should be extremely rare but if they do happen we should try to be safe and fail the channel change.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
local access → vulnerable operation → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial of service
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-3050Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht spezifizierte Auswirkungen zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241002Security Bulletin 02 Oct 2024

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

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

d?id=CVE-2024-46803 Référence CVE CVE-2024-46806 https://www.cve.org/CVERecord?id=CVE-2024-46806 Référence CVE CVE-2024-46808 https://www.cve.org/CVERecord?id=CVE-2024-46808 Référence CVE CVE-2024-46811 https://www.cve.org/CVERecord?id=CVE-2024-46811 Référence CVE CVE-2024-46813 https://www.cve.org/CVERecord?id=CVE-2024-46813 Référence CVE CVE-2024-46820 https://www.cve.org/CVERecord?id=CVE-2024-46820 Référence CVE CVE-2024-46823 https://www.cve.org/CVERecord?id=CVE-2024-46823 Référence CVE CVE-2024-46830 https://www.cve.org/CVERecord?id=CVE-2024-46830 Référence CVE CVE-2024-46833 https://www.cve.org/CVERecord?id=CVE-2024-46833 Référence CVE CVE-2024-46834 https://www.cve.org/CVERecord?id=CVE-2024-46834 Référence CVE CVE-2024-46835 https://www.cve.org/CVERecord?id=CVE-2024-46835 Référence CVE CVE-2024-46836 https://www.cve.org/CVERecord?id=CVE-2024-46836 Référence CVE CVE-2024-46842 https://www.cve.org/CVERecord?id=CVE-2024-46842 Référence CVE CVE-2024-46843 https://www.cve.org/CVERecord?id=CVE-2024-46843 Référence CVE CVE-2024-46848 https://www.cve.org/CVERecord?id=CVE-2024-46848 Référence CVE CVE-2024-46857 https://www.cve.org/CVERecord?id=CVE-2024-46857 Référence CVE CVE-2024-46860 https://www.cve.org/CVERecord?id=CVE-2024-46860 Référence CVE CVE-2024-46861 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46803 Référence CVE CVE-2024-46806 https://www.cve.org/CVERecord?id=CVE-2024-46806 Référence CVE CVE-2024-46808 https://www.cve.org/CVERecord?id=CVE-2024-46808 Référence CVE CVE-2024-46811 https://www.cve.org/CVERecord?id=CVE-2024-46811 Référence CVE CVE-2024-46813 https://www.cve.org/CVERecord?id=CVE-2024-46813 Référence CVE CVE-2024-46820 https://www.cve.org/CVERecord?id=CVE-2024-46820 Référence CVE CVE-2024-46823 https://www.cve.org/CVERecord?id=CVE-2024-46823 Référence CVE CVE-2024-46830 https://www.cve.org/CVERecord?id=CVE-2024-46830 Référence CVE CVE-2024-46833 https://www.cve.org/CVERecord?id=CVE-2024-46833 Référence CVE CVE-2024-46834 https://www.cve.org/CVERecord?id=CVE-2024-46834 Référence CVE CVE-2024-46835 https://www.cve.org/CVERecord?id=CVE-2024-46835 Référence CVE CVE-2024-46836 https://www.cve.org/CVERecord?id=CVE-2024-46836 Référence CVE CVE-2024-46842 https://www.cve.org/CVERecord?id=CVE-2024-46842 Référence CVE CVE-2024-46843 https://www.cve.org/CVERecord?id=CVE-2024-46843 Référence CVE CVE-2024-46848 https://www.cve.org/CVERecord?id=CVE-2024-46848 Référence CVE CVE-2024-46857 https://www.cve.org/CVERecord?id=CVE-2024-46857 Référence CVE CVE-2024-46860 https://www.cve.org/CVERecord?id=CVE-2024-46860 Référence CVE CVE-2024-46861 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46771 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-46802 https://www.cve.org/CVERecord?id=CVE-2024-46802 Référence CVE CVE-2024-46809 https://www.cve.org/CVERecord?id=CVE-2024-46809 Référence CVE CVE-2024-46813 https://www.cve.org/CVERecord?id=CVE-2024-46813 Référence CVE CVE-2024-46816 https://www.cve.org/CVERecord?id=CVE-2024-46816 Référence CVE CVE-2024-46818 https://www.cve.org/CVERecord?id=CVE-2024-46818 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=CVE-2024-46826 Référence CVE CVE-2024-46834 https://www.cve.org/CVERecord?id=CVE-2024-46834 Référence CVE CVE-2024-46840 https://www.cve.org/CVERecord?id=CVE-2024-46840 Référence CVE CVE-2024-46841 https://www.cve.org/CVERecord?id=CVE-2024-46841 Référence CVE CVE-2024-46848 https://www.cve.org/CVERecord?id=CVE-2024-46848 Référence CVE CVE-2024-47660 https://www.cve.org/CVERecord?id=CVE-2024-47660 Référence CVE CVE-2024-47670 https://www.cve.org/CVERecord?id=CVE-2024-47670 Référence CVE CVE-2024-47672 https://www.cve.org/CVERecord?id=CVE-2024-47672 Référence CVE CVE-2024-47673 https://www.cve.org/CVERecord?id=CVE-2024-47673 Référence CVE CVE-2024-47674 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-46824 Référence CVE CVE-2024-46825 https://www.cve.org/CVERecord?id=CVE-2024-46825 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=CVE-2024-46826 Référence CVE CVE-2024-46827 https://www.cve.org/CVERecord?id=CVE-2024-46827 Référence CVE CVE-2024-46828 https://www.cve.org/CVERecord?id=CVE-2024-46828 Référence CVE CVE-2024-46829 https://www.cve.org/CVERecord?id=CVE-2024-46829 Référence CVE CVE-2024-46830 https://www.cve.org/CVERecord?id=CVE-2024-46830 Référence CVE CVE-2024-46831 https://www.cve.org/CVERecord?id=CVE-2024-46831 Référence CVE CVE-2024-46832 https://www.cve.org/CVERecord?id=CVE-2024-46832 Référence CVE CVE-2024-46834 https://www.cve.org/CVERecord?id=CVE-2024-46834 Référence CVE CVE-2024-46835 https://www.cve.org/CVERecord?id=CVE-2024-46835 Référence CVE CVE-2024-46836 https://www.cve.org/CVERecord?id=CVE-2024-46836 Référence CVE CVE-2024-46838 https://www.cve.org/CVERecord?id=CVE-2024-46838 Référence CVE CVE-2024-46840 https://www.cve.org/CVERecord?id=CVE-2024-46840 Référence CVE CVE-2024-46841 https://www.cve.org/CVERecord?id=CVE-2024-46841 Référence CVE CVE-2024-46842 https://www.cve.org/CVERecord?id=CVE-2024-46842 Référence CVE CVE-2024-46843 https://www.cve.org/CVERecord?id=CVE-2024-46843 Référence CVE CVE-2024-46844 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46818 Référence CVE CVE-2024-46819 https://www.cve.org/CVERecord?id=CVE-2024-46819 Référence CVE CVE-2024-46821 https://www.cve.org/CVERecord?id=CVE-2024-46821 Référence CVE CVE-2024-46825 https://www.cve.org/CVERecord?id=CVE-2024-46825 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=CVE-2024-46826 Référence CVE CVE-2024-46827 https://www.cve.org/CVERecord?id=CVE-2024-46827 Référence CVE CVE-2024-46828 https://www.cve.org/CVERecord?id=CVE-2024-46828 Référence CVE CVE-2024-46830 https://www.cve.org/CVERecord?id=CVE-2024-46830 Référence CVE CVE-2024-46831 https://www.cve.org/CVERecord?id=CVE-2024-46831 Référence CVE CVE-2024-46834 https://www.cve.org/CVERecord?id=CVE-2024-46834 Référence CVE CVE-2024-46835 https://www.cve.org/CVERecord?id=CVE-2024-46835 Référence CVE CVE-2024-46836 https://www.cve.org/CVERecord?id=CVE-2024-46836 Référence CVE CVE-2024-46840 https://www.cve.org/CVERecord?id=CVE-2024-46840 Référence CVE CVE-2024-46841 https://www.cve.org/CVERecord?id=CVE-2024-46841 Référence CVE CVE-2024-46842 https://www.cve.org/CVERecord?id=CVE-2024-46842 Référence CVE CVE-2024-46843 https://www.cve.org/CVERecord?id=CVE-2024-46843 Référence CVE CVE-2024-46845 https://www.cve.org/CVERecord?id=CVE-2024-46845 Référence CVE CVE-2024-46846 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-46824 Référence CVE CVE-2024-46825 https://www.cve.org/CVERecord?id=CVE-2024-46825 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=CVE-2024-46826 Référence CVE CVE-2024-46827 https://www.cve.org/CVERecord?id=CVE-2024-46827 Référence CVE CVE-2024-46828 https://www.cve.org/CVERecord?id=CVE-2024-46828 Référence CVE CVE-2024-46829 https://www.cve.org/CVERecord?id=CVE-2024-46829 Référence CVE CVE-2024-46830 https://www.cve.org/CVERecord?id=CVE-2024-46830 Référence CVE CVE-2024-46831 https://www.cve.org/CVERecord?id=CVE-2024-46831 Référence CVE CVE-2024-46832 https://www.cve.org/CVERecord?id=CVE-2024-46832 Référence CVE CVE-2024-46834 https://www.cve.org/CVERecord?id=CVE-2024-46834 Référence CVE CVE-2024-46835 https://www.cve.org/CVERecord?id=CVE-2024-46835 Référence CVE CVE-2024-46836 https://www.cve.org/CVERecord?id=CVE-2024-46836 Référence CVE CVE-2024-46838 https://www.cve.org/CVERecord?id=CVE-2024-46838 Référence CVE CVE-2024-46840 https://www.cve.org/CVERecord?id=CVE-2024-46840 Référence CVE CVE-2024-46841 https://www.cve.org/CVERecord?id=CVE-2024-46841 Référence CVE CVE-2024-46842 https://www.cve.org/CVERecord?id=CVE-2024-46842 Référence CVE CVE-2024-46843 https://www.cve.org/CVERecord?id=CVE-2024-46843 Référence CVE CVE-2024-46844 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46802 Référence CVE CVE-2024-46809 https://www.cve.org/CVERecord?id=CVE-2024-46809 Référence CVE CVE-2024-46813 https://www.cve.org/CVERecord?id=CVE-2024-46813 Référence CVE CVE-2024-46814 https://www.cve.org/CVERecord?id=CVE-2024-46814 Référence CVE CVE-2024-46815 https://www.cve.org/CVERecord?id=CVE-2024-46815 Référence CVE CVE-2024-46816 https://www.cve.org/CVERecord?id=CVE-2024-46816 Référence CVE CVE-2024-46817 https://www.cve.org/CVERecord?id=CVE-2024-46817 Référence CVE CVE-2024-46818 https://www.cve.org/CVERecord?id=CVE-2024-46818 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=CVE-2024-46826 Référence CVE CVE-2024-46834 https://www.cve.org/CVERecord?id=CVE-2024-46834 Référence CVE CVE-2024-46840 https://www.cve.org/CVERecord?id=CVE-2024-46840 Référence CVE CVE-2024-46841 https://www.cve.org/CVERecord?id=CVE-2024-46841 Référence CVE CVE-2024-46848 https://www.cve.org/CVERecord?id=CVE-2024-46848 Référence CVE CVE-2024-46849 https://www.cve.org/CVERecord?id=CVE-2024-46849 Référence CVE CVE-2024-47668 https://www.cve.org/CVERecord?id=CVE-2024-47668 Référence CVE CVE-2024-47670 https://www.cve.org/CVERecord?id=CVE-2024-47670 Référence CVE CVE-2024-47672 https://www.cve.org/CVERecord?id=CVE-2024-47672 Référence CVE CVE-2024-47673 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46818 Référence CVE CVE-2024-46819 https://www.cve.org/CVERecord?id=CVE-2024-46819 Référence CVE CVE-2024-46821 https://www.cve.org/CVERecord?id=CVE-2024-46821 Référence CVE CVE-2024-46825 https://www.cve.org/CVERecord?id=CVE-2024-46825 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=CVE-2024-46826 Référence CVE CVE-2024-46827 https://www.cve.org/CVERecord?id=CVE-2024-46827 Référence CVE CVE-2024-46828 https://www.cve.org/CVERecord?id=CVE-2024-46828 Référence CVE CVE-2024-46830 https://www.cve.org/CVERecord?id=CVE-2024-46830 Référence CVE CVE-2024-46831 https://www.cve.org/CVERecord?id=CVE-2024-46831 Référence CVE CVE-2024-46834 https://www.cve.org/CVERecord?id=CVE-2024-46834 Référence CVE CVE-2024-46835 https://www.cve.org/CVERecord?id=CVE-2024-46835 Référence CVE CVE-2024-46836 https://www.cve.org/CVERecord?id=CVE-2024-46836 Référence CVE CVE-2024-46840 https://www.cve.org/CVERecord?id=CVE-2024-46840 Référence CVE CVE-2024-46841 https://www.cve.org/CVERecord?id=CVE-2024-46841 Référence CVE CVE-2024-46842 https://www.cve.org/CVERecord?id=CVE-2024-46842 Référence CVE CVE-2024-46843 https://www.cve.org/CVERecord?id=CVE-2024-46843 Référence CVE CVE-2024-46846 https://www.cve.org/CVERecord?id=CVE-2024-46846 Référence CVE CVE-2024-46848 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-010114Linux の 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: < 4.6, 6.10.10 ≤ 6.10.*, 6.11 ≤ *
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
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
04

Evidence and provenance

Published 27 Sept 2024 · Last source change 5 Aug 2026, 11:38 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-42095
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

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-42095↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor 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-46834 · cve.blacktree.nl