Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-36965: remoteproc: mediatek: Make sure IPI buffer fits in L2TCM

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 00548ac6b14428719c970ef90adae2b3b48c0cdf, 1d9e2de24533daca36cbf09e8d8596bf72b526b2, 26c6d7dc8c6a9fde9d362ab2eef6390efeff145e.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 00548ac6b14428719c970ef90adae2b3b48c0cdf, 1d9e2de24533daca36cbf09e8d8596bf72b526b2, 26c6d7dc8c6a9fde9d362ab2eef6390efeff145e or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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).

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jun 8, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-36965

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.11 and later · up to 5.15.160 inclusive
  • linux linux kernel5.16 and later · up to 6.1.92 inclusive
  • linux linux kernel6.2 and later · up to 6.6.32 inclusive
  • linux linux kernel6.7 and later · up to 6.8.11 inclusive
  • linux linux kernel6.9 and later · up to 6.9.2 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.11affected
    • 3efa0ea743b77d1611501f7d8b4f320d032d73ae and later · before 00548ac6b14428719c970ef90adae2b3b48c0cdfaffected · git
    • 3efa0ea743b77d1611501f7d8b4f320d032d73ae and later · before 1d9e2de24533daca36cbf09e8d8596bf72b526b2affected · git
    • 3efa0ea743b77d1611501f7d8b4f320d032d73ae and later · before 26c6d7dc8c6a9fde9d362ab2eef6390efeff145eaffected · git
    • 3efa0ea743b77d1611501f7d8b4f320d032d73ae and later · before 838b49e211d59fa827ff9df062d4020917cffbdfaffected · git
    • 3efa0ea743b77d1611501f7d8b4f320d032d73ae and later · before 36c79eb4845551e9f6d28c663b38ce0ab03b84a9affected · git
    • 3efa0ea743b77d1611501f7d8b4f320d032d73ae and later · before 331f91d86f71d0bb89a44217cc0b2a22810bbd42affected · git
    • before 5.11not affected · semver
    • 5.15.160 and later · up to and including 5.15.*not affected · semver
    • 6.1.92 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.94-16.1.94-1
Debian:13linuxbefore 6.8.11-16.8.11-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-36963Jun 3, 2024 · tracefs: Reset permissions on remount if permissions are options
    31Monitor
  • ← EarlierCVE-2024-36964Jun 3, 2024 · fs/9p: only translate RWX permissions for plain 9P2000
    22Monitor
  • Later →CVE-2024-36966Jun 8, 2024 · erofs: reliably distinguish block based and fscache mode
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux00548ac6b14428719c970ef90adae2b3b48c0cdfVendor (CNA)
Linux Linux1d9e2de24533daca36cbf09e8d8596bf72b526b2Vendor (CNA)
Linux Linux26c6d7dc8c6a9fde9d362ab2eef6390efeff145eVendor (CNA)
Linux Linux331f91d86f71d0bb89a44217cc0b2a22810bbd42Vendor (CNA)
Linux Linux36c79eb4845551e9f6d28c663b38ce0ab03b84a9Vendor (CNA)
Linux Linux838b49e211d59fa827ff9df062d4020917cffbdfVendor (CNA)
debian:linux6.1.94-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records