LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36940: pinctrl: core: delete incorrect free in pinctrl_enable()

In the Linux kernel, the following vulnerability has been resolved: pinctrl: core: delete incorrect free in pinctrl_enable() The "pctldev" struct is allocated in devm_pinctrl_register_and_init(). It's a devm_ managed pointer that is freed by devm_pinctrl_dev_release(), so freeing it in pinctrl_enable() will lead to a double free. The devm_pinctrl_dev_release() function frees the pindescs and destroys the mutex as well.

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

Security readout for executives and security teams

Plain-English summary

A flaw in Linux pin-control code can free the same kernel object twice. If a local, low-privileged user can reach the vulnerable path, resulting memory corruption could crash the system or potentially compromise kernel confidentiality and integrity. The supplied evidence does not establish remote reachability or active exploitation.

Executive priority

Use an accelerated patch cycle, especially for shared Linux hosts or systems executing untrusted local workloads. The potential impact is severe, but the local attack requirement and absence of cited active exploitation make this less urgent than a remotely exploitable or KEV-listed flaw. Require owners to verify vendor backports rather than relying solely on kernel version labels.

Technical view

The pctldev object is allocated as device-managed memory in devm_pinctrl_register_and_init() and released by devm_pinctrl_dev_release(). An incorrect free in pinctrl_enable() can therefore cause a double free. The managed release also frees pin descriptors and destroys the mutex. Referenced Linux stable commits remove the incorrect free across kernel branches.

Likely exposure

Exposure is limited to Linux systems containing the affected pinctrl implementation where a local user or workload can exercise the vulnerable path. The bundle lists affected kernel versions but does not clearly define every vulnerable-to-fixed range. Distribution and appliance backports make exact package-level verification necessary.

Exploitation context

CVSS 3.1 scores this 7.8: local access, low complexity, low privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact. The bundle marks KEV false, and no cited source reports active exploitation or a public proof of concept. Internet-scale remote exploitation is not supported by the evidence.

Researcher notes

The supplied affected-version data is ambiguous: it includes an unusual "0" entry and repeated commit identifiers under an unaffected record. Establish exposure through branch ancestry and vendor backport evidence. The bundle supplies no CWE classification, trigger prerequisites, exploit evidence, or product-specific applicability beyond Linux; Siemens references exist but their contents were not provided.

Mitigation direction

  • Install a vendor-supported kernel update containing the applicable Linux stable fix.
  • Check distribution and appliance advisories for package-specific backport status.
  • Restrict local shell access and untrusted workload execution until affected systems are updated.
  • Prioritize systems permitting multiple users, containers, plugins, or other locally executed untrusted code.

Validation and detection

  • Inventory each system's exact running kernel and vendor package revision.
  • Compare package revisions with applicable distribution or appliance security guidance.
  • Verify source, package changelogs, or vendor records include the relevant stable fix.
  • After maintenance, confirm systems are running the updated kernel rather than only having it installed.
  • Review kernel crash records for pinctrl-related memory corruption, while treating absence as inconclusive.
Prepared
Confidence
medium
Sources
10

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-36940 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
3ADP providers
13Source 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-36940Attack 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
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6118714275f0a313ecc296a87ed1af32d9691bed, 6118714275f0a313ecc296a87ed1af32d9691bed, 6118714275f0a313ecc296a87ed1af32d9691bed, 6118714275f0a313ecc296a87ed1af32d9691bed, 6118714275f0a313ecc296a87ed1af32d9691bed, 6118714275f0a313ecc296a87ed1af32d9691bed, 6118714275f0a313ecc296a87ed1af32d9691bed, 6118714275f0a313ecc296a87ed1af32d9691bedunaffected
LinuxLinux4.11, 0, 4.19.314, 5.4.276, 5.10.217, 5.15.159, 6.1.91, 6.6.31, 6.8.10, 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.