dbcve.org
Linux KernelOperating system · Linux

CVE-2024-36965

MEDIUM · 5.5 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to after 6.9.2 or later.
See remediation →
57/100
Remediation priority · Elevated
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: remoteproc: mediatek: Make sure IPI buffer fits in L2TCM The IPI buffer location is read from the firmware that we load to the System Companion Processor, and it's not granted that both the SRAM (L2TCM) size that is defined in the devicetree node is large enough for that, and while this is especially true for multi-core SCP, it's still useful to check on single-core variants as well. Failing to perform this check may make this driver perform R/W operations out of the L2TCM boundary, resulting (at best) in a kernel panic. To fix that, check that the IPI buffer fits, otherwise return a failure and refuse to boot the relevant SCP core (or the SCP at all, if this is single core).

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.11, <= 5.15.160>= 5.16, <= 6.1.92>= 6.2, <= 6.6.32>= 6.7, <= 6.8.11>= 6.9, <= 6.9.2

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 a release after 6.9.2
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to Linux kernel 5.15.161+, 6.1.93+, 6.6.33+, or 6.8.12+ depending on the branch in use

  1. 1. Identify the currently running Linux kernel version using `uname -r`
  2. 2. Check if the running version is within the affected range: 5.11 to 5.15.160, 5.16 to 6.1.92, 6.2 to 6.6.32, or 6.7 to 6.8.11
  3. 3. If affected, upgrade the Linux kernel to a patched version: 5.15.161 or later for the 5.15 branch, 6.1.93 or later for the 6.1 branch, 6.6.33 or later for the 6.6 branch, or 6.8.12 or later for the 6.8 branch
  4. 4. For distribution-based systems, apply vendor-supplied kernel updates via package manager (e.g., `apt update && apt upgrade` for Debian/Ubuntu, `yum update` for RHEL/CentOS, or `dnf update` for Fedora)
  5. 5. Reboot the system to load the patched kernel
  6. 6. Verify the new kernel version is running with `uname -r`
Caveat Kernel upgrades may require system reboot and could introduce compatibility changes with third-party modules; ensure critical drivers and modules are compatible with the new kernel version

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36965 — 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-36965 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