CVE-2024-38568: drivers/perf: hisi: hns3: Fix out-of-bound access when valid event group
In the Linux kernel, the following vulnerability has been resolved:
drivers/perf: hisi: hns3: Fix out-of-bound access when valid event group
The perf tool allows users to create event groups through following
cmd [1], but the driver does not check whether the array index is out
of bounds when writing data to the event_group array. If the number of
events in an event_group is greater than HNS3_PMU_MAX_HW_EVENTS, the
memory write overflow of event_group array occurs.
Add array index check to fix the possible array out of bounds violation,
and return directly when write new events are written to array bounds.
There are 9 different events in an event_group.
[1] perf stat -e '{pmu/event1/, ... ,pmu/event9/}
Security readout for executives and security teams
Plain-English summary
A Linux kernel performance-monitoring driver for HNS3 hardware can write past internal array bounds when handling oversized perf event groups. This is a kernel memory-safety issue, but the source bundle gives no CVSS score, known exploitation, or concrete business impact. Treat affected HNS3 Linux hosts as needing kernel patch tracking.
Executive priority
Schedule remediation after confirming HNS3 exposure. This is not an emergency based on current sources, but kernel memory issues warrant timely patching.
Technical view
The HNS3 PMU perf driver wrote entries into event_group without checking the array index. Event groups larger than HNS3_PMU_MAX_HW_EVENTS could cause an out-of-bounds write. Kernel stable fixes add bounds checking and return when a new event would exceed the array bounds.
Likely exposure
Exposure appears limited to Linux systems using the HiSilicon HNS3 PMU driver or related hardware, with local users able to create perf event groups. The CVE metadata lists Linux kernel versions and stable commits, but distribution-specific affected package ranges are not provided.
Exploitation context
The provided sources do not cite active exploitation, and the CVE is not marked KEV. The trigger is local perf event group creation. The practical impact is not fully characterized in the source bundle.
Researcher notes
Focus validation on driver presence, kernel branch, and whether the stable fix was backported. Do not infer privilege escalation or remote exposure from the provided evidence; the sources only describe an out-of-bounds write condition.
Mitigation direction
Apply Linux kernel updates that include the referenced stable fixes.
Use distribution vendor advisories to map fixed package versions for each kernel branch.
If updates are delayed, request vendor guidance for temporary controls.
Avoid assuming exposure without confirming HNS3 PMU driver or hardware presence.
Validation and detection
Inventory Linux hosts for HNS3 hardware or enabled HNS3 PMU support.
Compare deployed kernel packages against distribution advisories and referenced stable commits.
Check whether untrusted local users can access perf functionality on potentially affected systems.
Confirm patched systems include the bounds-checking fix for the HNS3 PMU driver.
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-38568 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.