LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48663: gpio: mockup: fix NULL pointer dereference when removing debugfs

In the Linux kernel, the following vulnerability has been resolved: gpio: mockup: fix NULL pointer dereference when removing debugfs We now remove the device's debugfs entries when unbinding the driver. This now causes a NULL-pointer dereference on module exit because the platform devices are unregistered *after* the global debugfs directory has been recursively removed. Fix it by unregistering the devices first.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel cleanup bug in the gpio mockup component. When the driver is removed, debugfs cleanup can trigger a NULL pointer dereference. The likely business impact is a local kernel crash or instability in systems that use this driver path, not broad remote compromise.

Executive priority

Treat as low priority for most production environments unless gpio-mockup is used. Remediate through normal kernel patch cycles and prioritize only where driver unloads or debugfs workflows are operationally relevant.

Technical view

The issue occurs during gpio-mockup driver/module teardown. Debugfs entries are removed while platform devices are unregistered later, creating a NULL pointer dereference on module exit. The upstream fix changes ordering so devices are unregistered before the global debugfs directory is recursively removed.

Likely exposure

Exposure appears limited to Linux systems using the gpio mockup driver and the affected teardown path. The provided data does not establish broad default exposure, reachable remote attack surface, or affected distributions.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. The evidence describes a crash condition during driver unbinding or module exit, with no public exploit status provided.

Researcher notes

Evidence is sparse: no CVSS, CWE, distribution matrix, or exploit confirmation is provided. Analysis should focus on kernel versions, backports, module configuration, and whether local users can trigger the affected teardown path.

Mitigation direction

  • Check vendor kernel guidance for CVE-2022-48663 applicability.
  • Update to a kernel containing the referenced stable fixes.
  • Prioritize systems using gpio-mockup or related debugfs workflows.
  • Disable unnecessary gpio-mockup usage where operationally safe.
  • Track distribution advisories for backported fixes.

Validation and detection

  • Inventory Linux kernels and vendor patch status.
  • Check whether gpio-mockup is built, loaded, or used.
  • Confirm applied kernels include the referenced stable commits.
  • Review crash logs for gpio-mockup or debugfs NULL dereferences.
  • Validate remediation in staging before production rollout.
Prepared
Confidence
medium
Sources
6

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-2022-48663 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
2ADP providers
5Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3815e66c2183f3430490e450ba16779cf5214ec6, 3a10e8edee2b45a654f1f7b05f747129ec84cf9d, bc55c1677edbe86a1c66a35e800df47dff16ad61, 303e6da99429510b1e4edf833afe90ac8542e747unaffected
LinuxLinux5.10.144, 5.15.69, 5.19.10unaffected
Weakness

CWE details

No CWE listed

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