CVE-2023-54222: hte: tegra-194: Fix off by one in tegra_hte_map_to_line_id()
In the Linux kernel, the following vulnerability has been resolved:
hte: tegra-194: Fix off by one in tegra_hte_map_to_line_id()
The "map_sz" is the number of elements in the "m" array so the >
comparison needs to be changed to >= to prevent an out of bounds
read.
Security readout for executives and security teams
Plain-English summary
CVE-2023-54222 is a Linux kernel bounds-checking flaw in Tegra-194 HTE code. The published record does not provide CVSS, CWE, exploitation, or business-impact detail. Treat it as a targeted kernel maintenance issue unless you operate Linux systems using this Tegra-194 HTE path.
Executive priority
Low immediate urgency unless your environment includes affected Tegra-194 Linux systems. Because severity and exploitation evidence are incomplete, handle through normal kernel patch governance, with faster action for exposed device fleets.
Technical view
The flaw is an off-by-one check in tegra_hte_map_to_line_id(). The code compared an index with map_sz using >, but map_sz is the number of elements, so equality could permit an out-of-bounds read. Kernel stable commits change the check to >=.
Likely exposure
Exposure appears limited to Linux kernels with the Tegra-194 HTE driver code in affected versions or downstream backports. The bundle does not identify distributions, appliances, or cloud platforms affected.
Exploitation context
CISA KEV is false in the supplied bundle, and no cited source claims active exploitation. The available evidence describes a kernel fix, not a public exploit or attack campaign.
Researcher notes
The source record lacks CVSS, CWE, concrete impact, and exploitability detail. Analysis should stay tied to the off-by-one out-of-bounds read and the referenced Linux stable commits until vendor advisories add context.
Mitigation direction
Identify Linux assets using Tegra-194 HTE-related kernel code.
Apply vendor or kernel updates containing the referenced stable fixes.
Check distribution advisories for backported fixes before relying on version strings.
Prioritize embedded or device fleets that use affected Tegra-194 functionality.
Validation and detection
Confirm the running kernel source includes the >= bounds check fix.
Map installed kernels against vendor advisories or the listed stable commits.
Verify affected device classes actually use the Tegra-194 HTE path.
Record exceptions where vendors mark downstream kernels as fixed or unaffected.
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-2023-54222 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 30, 2025, 12:11 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.