LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47499: iio: accel: kxcjk-1013: Fix possible memory leak in probe and remove

In the Linux kernel, the following vulnerability has been resolved: iio: accel: kxcjk-1013: Fix possible memory leak in probe and remove When ACPI type is ACPI_SMO8500, the data->dready_trig will not be set, the memory allocated by iio_triggered_buffer_setup() will not be freed, and cause memory leak as follows: unreferenced object 0xffff888009551400 (size 512): comm "i2c-SMO8500-125", pid 911, jiffies 4294911787 (age 83.852s) hex dump (first 32 bytes): 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 20 e2 e5 c0 ff ff ff ff ........ ....... backtrace: [<0000000041ce75ee>] kmem_cache_alloc_trace+0x16d/0x360 [<000000000aeb17b0>] iio_kfifo_allocate+0x41/0x130 [kfifo_buf] [<000000004b40c1f5>] iio_triggered_buffer_setup_ext+0x2c/0x210 [industrialio_triggered_buffer] [<000000004375b15f>] kxcjk1013_probe+0x10c3/0x1d81 [kxcjk_1013] Fix it by remove data->dready_trig condition in probe and remove.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory leak in an accelerometer driver path. It appears relevant mainly to systems using the KXCJK-1013/SMO8500 hardware path, not broad remote server exposure. Sources do not provide CVSS, confirmed exploitation, or a standalone workaround.

Executive priority

Treat as routine kernel maintenance unless your fleet includes affected accelerometer-equipped Linux devices. No source indicates active exploitation or broad remote risk, but unresolved kernel memory leaks can affect device reliability over time.

Technical view

The kxcjk-1013 IIO accelerometer driver can leak memory when ACPI type ACPI_SMO8500 leaves data->dready_trig unset after iio_triggered_buffer_setup(). Linux stable commits fix probe and remove handling by removing that conditional cleanup dependency.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel versions with the kxcjk-1013 driver and ACPI_SMO8500-related accelerometer hardware. Headless cloud servers are less likely to be exposed, but kernel backports require vendor verification.

Exploitation context

The provided sources do not report active exploitation, KEV listing, exploit availability, privilege requirements, or remote attack path. Evidence supports a kernel memory leak condition in a hardware driver, not a confirmed weaponized vulnerability.

Researcher notes

The key condition is ACPI_SMO8500 with data->dready_trig unset, leaving memory allocated by iio_triggered_buffer_setup() unfreed. The source bundle lacks CVSS, CWE, exploitability analysis, and distribution-specific package status.

Mitigation direction

  • Apply Linux kernel or distribution updates containing the stable kxcjk-1013 fix.
  • Confirm vendor kernels include the relevant upstream stable backport.
  • Prioritize endpoints or embedded systems with SMO8500/KXCJK-1013 accelerometer hardware.
  • If no update is available, request vendor-specific mitigation guidance.

Validation and detection

  • Inventory Linux kernel versions against the affected version ranges in the CVE record.
  • Check hardware inventory for SMO8500 or KXCJK-1013 accelerometer usage.
  • Confirm the patched kernel contains a referenced stable commit or vendor backport.
  • Review kernel logs for related kxcjk_1013 or IIO buffer leak indicators.
Prepared
Confidence
high
Sources
10

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-2021-47499 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
9Source 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa25691c1f9674090fb66586cf4c5d60d3efdf339, a25691c1f9674090fb66586cf4c5d60d3efdf339, a25691c1f9674090fb66586cf4c5d60d3efdf339, a25691c1f9674090fb66586cf4c5d60d3efdf339, a25691c1f9674090fb66586cf4c5d60d3efdf339, a25691c1f9674090fb66586cf4c5d60d3efdf339, a25691c1f9674090fb66586cf4c5d60d3efdf339, a25691c1f9674090fb66586cf4c5d60d3efdf339unaffected
LinuxLinux4.2, 0, 4.4.295, 4.9.293, 4.14.258, 4.19.221, 5.4.165, 5.10.85, 5.15.8, 5.16affected
Weakness

CWE details

No CWE listed

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