LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can let an unsafe network channel configuration proceed when ethtool cannot confirm RSS indirection table limits. The stated impact is possible kernel crashes in rare failure conditions. The public record does not provide CVSS, confirmed exploitation, or a detailed product matrix.

Executive priority

Treat this as an availability risk rather than a confirmed breach pathway. Patch through normal kernel maintenance, with higher priority for critical network infrastructure where kernel crashes would cause service disruption.

Technical view

The ethtool core skipped the maximum-channel validation when a driver could not fetch an indirection table or memory allocation failed. The fix changes behavior to fail closed, blocking channel changes when validation cannot prove RSS table entries are within bounds.

Likely exposure

Exposure is limited to Linux systems using affected kernel versions and ethtool channel/RSS configuration paths. Systems without such driver paths or administrative network reconfiguration exposure are less likely to encounter the bug.

Exploitation context

The source bundle does not identify active exploitation, public exploit code, or CISA KEV listing. The described trigger depends on rare driver table retrieval or memory allocation failures during channel changes.

Researcher notes

Evidence is narrow but credible: the fix hardens ethtool validation by failing closed when max-channel checks cannot complete. The public CVE data lacks CVSS, CWE, exploit status, and detailed affected distribution guidance.

Mitigation direction

  • Review vendor kernel advisories for CVE-2024-46834 applicability.
  • Update to a vendor kernel containing the referenced stable fixes.
  • Avoid unnecessary ethtool channel changes on potentially affected systems.
  • Prioritize systems with high-availability network workloads or custom NIC tuning.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Check whether vendor kernel changelogs include CVE-2024-46834 or the referenced commits.
  • Identify systems using ethtool RSS or channel tuning workflows.
  • Review kernel logs for crashes around NIC channel or RSS changes.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-46834 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd4ab4286276fcd6c155bafdf4422b712068d2516, d4ab4286276fcd6c155bafdf4422b712068d2516unaffected
LinuxLinux4.6, 0, 6.10.10, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.