CVE-2024-46833: net: hns3: void array out of bound when loop tnl_num
In the Linux kernel, the following vulnerability has been resolved:
net: hns3: void array out of bound when loop tnl_num
When query reg inf of SSU, it loops tnl_num times. However, tnl_num comes
from hardware and the length of array is a fixed value. To void array out
of bound, make sure the loop time is not greater than the length of array
Security readout for executives and security teams
Plain-English summary
CVE-2024-46833 is a Linux kernel issue in the hns3 network driver. A hardware-reported tunnel count could make the driver loop past a fixed array while querying SSU register information. The sources confirm a kernel fix, but do not state business impact, CVSS severity, or active exploitation.
Executive priority
Treat this as targeted kernel hygiene rather than an internet-wide emergency. Prioritize patch validation for servers using hns3 network hardware, especially production systems where kernel driver faults could affect availability. No active exploitation is supported by the supplied sources.
Technical view
The vulnerable hns3 code trusted tnl_num from hardware when iterating over a fixed-size array during SSU register information queries. The fix limits loop iterations to the array length. Source metadata lists Linux kernel 6.10, 6.10.10, and 6.11-related affected entries, but distro backport status is not provided.
Likely exposure
Exposure appears limited to Linux systems using affected kernel builds with the hns3 network driver and compatible hardware. General Linux systems without that driver or hardware are less likely exposed. Confirm exact exposure through kernel package, driver presence, and vendor or distribution advisories.
Exploitation context
The source bundle does not identify public exploitation, weaponization, or KEV listing. The described condition depends on hardware-provided tnl_num exceeding a fixed array length during a driver register query path. Practical exploitability and impact are not established by the supplied sources.
Researcher notes
Evidence is narrow: the CVE text describes an out-of-bounds array loop, and two stable kernel commits are referenced. There is no CVSS, CWE, crash detail, exploitability analysis, or vendor-specific package mapping in the supplied bundle.
Mitigation direction
Update to a kernel containing the referenced stable hns3 fixes.
Check your Linux distribution advisory for backported fixed packages.
Prioritize systems with Huawei HNS3-compatible network hardware or loaded hns3 drivers.
If patching is delayed, consult vendor guidance for supported risk reduction.
Validation and detection
Inventory kernels matching the affected Linux version entries from the CVE source.
Check whether the hns3 driver is present or loaded on those systems.
Verify installed kernel packages include the referenced upstream stable fix commits.
Review distribution changelogs for CVE-2024-46833 or hns3 fix backports.
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-46833 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.