dbcve.org
Linux KernelOperating system · Linux

CVE-2024-38569

HIGH · 7.8 CVSS v3.1 Published 2024-06-19
Fix available
A fix is available. Upgrade to 6.1.93 / 6.6.33 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: drivers/perf: hisi_pcie: 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 HISI_PCIE_MAX_COUNTERS, 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/}'

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.17, < 6.1.93>= 6.2, < 6.6.33>= 6.7, < 6.8.12>= 6.9, < 6.9.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.1.93 / 6.6.33 / 6.8.12 or later
Fixed in 6.1.936.6.336.8.12
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux Kernel 6.1.93+ (6.1.y), 6.6.33+ (6.6.y), 6.8.12+ (6.8.y), or 6.9.3+ (6.9.y) - or upgrade to latest stable (6.10+)

  1. Identify the current kernel version using 'uname -r' or 'cat /proc/version'
  2. Determine which branch of the affected kernel version is in use (e.g., 6.1.y, 6.6.y, 6.7.y, 6.8.y, 6.9.y)
  3. Upgrade the Linux kernel to the latest stable version in the respective branch that includes the fix: for 6.1.x upgrade to >= 6.1.93, for 6.6.x upgrade to >= 6.6.33, for 6.7.x upgrade to >= 6.8.12, for 6.8.x upgrade to >= 6.8.12, for 6.9.x upgrade to >= 6.9.3
  4. Alternatively, upgrade to the latest stable kernel release (e.g., 6.10 or later) which contains this fix
  5. After kernel upgrade, reboot the system to load the patched kernel
  6. Verify the fix is applied by checking the kernel version and confirming the patch commit 3d1face00ebb7996842aee4214d7d0fb0c77b1e9 is included
Caveat Kernel upgrades may require rebooting production systems; ensure compatibility with existing hardware drivers and software stack before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38569 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-38569 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data