LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50218: iio: light: isl29028: Fix the warning in isl29028_remove()

In the Linux kernel, the following vulnerability has been resolved: iio: light: isl29028: Fix the warning in isl29028_remove() The driver use the non-managed form of the register function in isl29028_remove(). To keep the release order as mirroring the ordering in probe, the driver should use non-managed form in probe, too. The following log reveals it: [ 32.374955] isl29028 0-0010: remove [ 32.376861] general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] PREEMPT SMP KASAN PTI [ 32.377676] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037] [ 32.379432] RIP: 0010:kernfs_find_and_get_ns+0x28/0xe0 [ 32.385461] Call Trace: [ 32.385807] sysfs_unmerge_group+0x59/0x110 [ 32.386110] dpm_sysfs_remove+0x58/0xc0 [ 32.386391] device_del+0x296/0xe50 [ 32.386959] cdev_device_del+0x1d/0xd0 [ 32.387231] devm_iio_device_unreg+0x27/0xb0 [ 32.387542] devres_release_group+0x319/0x3d0 [ 32.388162] i2c_device_remove+0x93/0x1f0

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50218 is a Linux kernel driver bug in the ISL29028 light sensor driver. During device removal, mismatched resource cleanup can trigger a kernel general protection fault. Business risk appears concentrated on Linux systems that actually use this sensor driver; public sources do not show broad remote exposure or active exploitation.

Executive priority

Treat this as a targeted kernel maintenance item, not an internet-wide emergency. Prioritize affected device fleets and embedded Linux products where sensor drivers are enabled. Escalate if your environment uses this hardware path or has observed related kernel crashes.

Technical view

The issue is in the Linux IIO light driver isl29028. The CVE text says probe and remove used inconsistent managed versus non-managed registration, causing release-order problems and a crash path through sysfs/device removal. Stable kernel commits are referenced as fixes, but no CVSS, CWE, or exploit details are provided.

Likely exposure

Exposure is likely limited to Linux kernels in the listed affected versions where the isl29028 driver is present and the relevant hardware or driver path is used. General-purpose servers without this light sensor driver are less likely to be exposed, but kernel build and module inventory should confirm that.

Exploitation context

The source bundle does not state active exploitation, and KEV is false. The demonstrated failure is a kernel crash during driver/device removal, suggesting local, hardware, hotplug, or module lifecycle relevance rather than a confirmed remote attack path.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or attack prerequisites are provided. The strongest signal is the kernel commit rationale and crash trace. Analysis should focus on affected kernel branches, driver configuration, and whether removal paths are reachable in deployed systems.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable Linux fixes.
  • Prioritize embedded, laptop, or IoT Linux builds using ISL29028 light sensors.
  • If unused, disable the isl29028 driver through approved kernel configuration or vendor guidance.
  • Monitor vendor advisories for backported fixes matching your deployed kernel branch.

Validation and detection

  • Inventory Linux kernel versions against the affected versions listed in the CVE record.
  • Confirm whether the isl29028 IIO light sensor driver is built, loaded, or deployed.
  • Check vendor kernel changelogs for the referenced stable commit IDs.
  • Review kernel logs for isl29028 removal crashes or related general protection faults.
Prepared
Confidence
medium
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-2022-50218 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
0ADP providers
9Source links

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2db5054ac28d4ab2eaa6c67e2d9f61fa5ba006b8, 2db5054ac28d4ab2eaa6c67e2d9f61fa5ba006b8, 2db5054ac28d4ab2eaa6c67e2d9f61fa5ba006b8, 2db5054ac28d4ab2eaa6c67e2d9f61fa5ba006b8, 2db5054ac28d4ab2eaa6c67e2d9f61fa5ba006b8, 2db5054ac28d4ab2eaa6c67e2d9f61fa5ba006b8, 2db5054ac28d4ab2eaa6c67e2d9f61fa5ba006b8, 2db5054ac28d4ab2eaa6c67e2d9f61fa5ba006b8unaffected
LinuxLinux4.11, 0, 4.14.291, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

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