LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36019: regmap: maple: Fix cache corruption in regcache_maple_drop()

In the Linux kernel, the following vulnerability has been resolved: regmap: maple: Fix cache corruption in regcache_maple_drop() When keeping the upper end of a cache block entry, the entry[] array must be indexed by the offset from the base register of the block, i.e. max - mas.index. The code was indexing entry[] by only the register address, leading to an out-of-bounds access that copied some part of the kernel memory over the cache contents. This bug was not detected by the regmap KUnit test because it only tests with a block of registers starting at 0, so mas.index == 0.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel register-cache bug can copy unrelated kernel memory into cache entries, corrupting state and potentially affecting confidentiality, integrity, or availability. Exploitation requires local access with low privileges according to the supplied CVSS assessment. Exposure depends on whether an affected kernel actually uses the maple-backed regmap cache path.

Executive priority

Treat as a high-priority kernel maintenance issue, especially on systems permitting untrusted local access. Schedule validated vendor updates promptly, but avoid declaring an emergency solely from the CVSS score because active exploitation is not supported by the supplied evidence.

Technical view

regcache_maple_drop() indexed entry[] using a register address instead of the offset from the cache block base. For blocks not starting at zero, this causes an out-of-bounds access and copies kernel memory over cache contents. Existing KUnit coverage missed the defect because its tested block began at register zero.

Likely exposure

The bundle identifies Linux and lists versions 6.4, 6.6.26, 6.8.5, and 6.9 as affected data, but does not clearly express every range boundary. Practical exposure requires the vulnerable maple regcache code path. Distribution kernels may contain backports, so version numbers alone are insufficient.

Exploitation context

The CVSS 3.1 score is 7.8 with local access, low complexity, low privileges, and no user interaction. CISA KEV status is false in the supplied bundle, and no cited source establishes active exploitation or a public exploit. Real-world exploitability is therefore unconfirmed.

Researcher notes

The defect is an offset-calculation error: retaining a cache block's upper portion requires indexing by max minus mas.index. Testing only blocks starting at zero masked the problem. The bundle provides three stable-tree fix references, but no exploit evidence, affected-driver enumeration, or definitive distribution package mapping.

Mitigation direction

  • Apply a vendor-supported kernel update containing the relevant upstream fix or distribution backport.
  • Prioritize multi-user, shared-compute, and other systems where untrusted users have local access.
  • If immediate updating is impossible, check vendor guidance for supported exposure-reduction measures.
  • Reboot into the updated kernel and remove vulnerable kernels from normal boot selection.

Validation and detection

  • Inventory running kernel versions and distribution package build identifiers.
  • Confirm the running kernel contains an upstream fix commit or documented vendor backport.
  • Determine whether deployed hardware and drivers use the maple-backed regmap cache path.
  • Review kernel and device logs for unexplained faults, while treating their absence as inconclusive.
  • Verify the remediated kernel remains active after reboot.
Prepared
Confidence
high
Sources
5

Public sources used

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-36019 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-36019Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf033c26de5a5734625d2dd1dc196745fae186f1b, f033c26de5a5734625d2dd1dc196745fae186f1b, f033c26de5a5734625d2dd1dc196745fae186f1bunaffected
LinuxLinux6.4, 0, 6.6.26, 6.8.5, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.