Answer in brief
CVE-2024-46834 records a Unknown severity vulnerability in ethtool: fail closed if we can't get max channel used in indirection tables. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d4ab4286276fcd6c155bafdf4422b712068d2516 <101737d8b88dbd4be6010bac398fe810f1950036 || >=d4ab4286276fcd6c155bafdf4422b712068d2516 <2899d58462ba868287d6ff3acad3675e7adf934f | 101737d8b88dbd4be6010bac398fe810f1950036, 2899d58462ba868287d6ff3acad3675e7adf934f |
| Linux/Linuxgeneric | 4.6 | Not reported |
Published upstream
Sep 27, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-46834 records a Unknown severity vulnerability in ethtool: fail closed if we can't get max channel used in indirection tables. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d4ab4286276fcd6c155bafdf4422b712068d2516 <101737d8b88dbd4be6010bac398fe810f1950036 || >=d4ab4286276fcd6c155bafdf4422b712068d2516 <2899d58462ba868287d6ff3acad3675e7adf934f | 101737d8b88dbd4be6010bac398fe810f1950036, 2899d58462ba868287d6ff3acad3675e7adf934f |
| Linux/Linuxgeneric | 4.6 | Not reported |
Published upstream
Sep 27, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.