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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-36940 is a Linux kernel memory-management bug in the pin control subsystem. A pointer managed by the kernel device-managed cleanup path could also be freed manually, creating a double-free condition. Business urgency depends on whether exposed systems run affected kernel builds or vendor appliances based on them.

Executive priority

Handle through normal kernel patch governance unless affected systems support critical operations or appliances with slow vendor update cycles. There is no source-backed evidence of active exploitation, but kernel double-free defects warrant timely remediation.

Technical view

The issue is in pinctrl_enable(). The pctldev structure is allocated by devm_pinctrl_register_and_init() and should be released by devm_pinctrl_dev_release(). The vulnerable logic incorrectly frees it in pinctrl_enable(), so normal devm cleanup can free it again. Kernel stable commits remove the incorrect free.

Likely exposure

Exposure is most likely on Linux systems, embedded devices, or appliances using affected kernel versions or unpatched vendor backports. The CVE data lists Linux kernel 4.11 onward and several stable lines, but exact exposure requires vendor kernel package verification.

Exploitation context

The source bundle does not show CISA KEV listing, public exploitation, CVSS scoring, or exploit maturity. Treat it as a kernel reliability and memory-safety issue until vendor advisories or distribution packages clarify practical exploitability.

Researcher notes

The record provides root cause and stable commit references but lacks CVSS, CWE, attack vector, prerequisites, or proof of exploitability. Avoid assuming local privilege escalation or remote reachability without vendor-specific analysis.

Mitigation direction

  • Identify systems and appliances running affected Linux kernel branches.
  • Apply vendor kernel updates containing the referenced stable fixes.
  • Prioritize internet-facing, safety-critical, and appliance workloads using Linux kernels.
  • Track Debian LTS and device-vendor advisories for backported fixes.
  • If no vendor fix exists, request vendor guidance before compensating controls.

Validation and detection

  • Inventory kernel versions and vendor package build numbers.
  • Confirm installed kernels include the referenced pinctrl stable commits or vendor backports.
  • Review Debian LTS advisories if using Debian-based systems.
  • Check vendor appliance advisories for affected firmware images.
  • Monitor kernel logs for related pinctrl instability after updates.
Prepared
Confidence
medium
Sources
12

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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
3ADP providers
13Source links

SSVC decision data

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

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.