LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23237: platform/x86: classmate-laptop: Add missing NULL pointer checks

In the Linux kernel, the following vulnerability has been resolved: platform/x86: classmate-laptop: Add missing NULL pointer checks In a few places in the Classmate laptop driver, code using the accel object may run before that object's address is stored in the driver data of the input device using it. For example, cmpc_accel_sensitivity_store_v4() is the "show" method of cmpc_accel_sensitivity_attr_v4 which is added in cmpc_accel_add_v4(), before calling dev_set_drvdata() for inputdev->dev. If the sysfs attribute is accessed prematurely, the dev_get_drvdata(&inputdev->dev) call in in cmpc_accel_sensitivity_store_v4() returns NULL which leads to a NULL pointer dereference going forward. Moreover, sysfs attributes using the input device are added before initializing that device by cmpc_add_acpi_notify_device() and if one of them is accessed before running that function, a NULL pointer dereference will occur. For example, cmpc_accel_sensitivity_attr_v4 is added before calling cmpc_add_acpi_notify_device() and if it is read prematurely, the dev_get_drvdata(&acpi->dev) call in cmpc_accel_sensitivity_show_v4() returns NULL which leads to a NULL pointer dereference going forward. Fix this by adding NULL pointer checks in all of the relevant places.

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

Security readout for executives and security teams

Plain-English summary

CVE-2026-23237 is a Linux kernel bug in the Classmate laptop driver. If certain sysfs attributes are accessed before driver data is fully initialized, the kernel may hit a NULL pointer dereference. The public record describes a stability issue, not data theft or remote compromise.

Executive priority

Treat as a targeted stability risk, not an emergency. Patch through normal Linux kernel maintenance, with higher priority for fleets that actually use the Classmate laptop driver.

Technical view

The platform/x86 classmate-laptop driver added sysfs attributes before related accel/input device driver data was set. Premature reads or writes can make dev_get_drvdata() return NULL and trigger a NULL pointer dereference. Upstream stable commits add NULL checks in relevant paths.

Likely exposure

Exposure appears limited to Linux systems using the platform/x86 Classmate laptop driver. Organizations should prioritize specialized or legacy laptop fleets where this driver may load. The provided version data is ambiguous, so confirm against your distribution kernel advisories and the referenced stable commits.

Exploitation context

No active exploitation is indicated by KEV or the provided sources. The described trigger is premature access to driver sysfs attributes during initialization. The sources do not establish remote exploitability, privilege requirements, or practical exploit reliability.

Researcher notes

The record lacks CVSS, CWE, and detailed exploitability assessment. The core issue is initialization ordering around sysfs attribute exposure and missing NULL checks. Version mapping in the supplied data should be verified against upstream commits and downstream backports.

Mitigation direction

  • Update to a kernel or vendor package containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes and affected kernel builds.
  • Disable or avoid loading the classmate-laptop driver if not required, per vendor guidance.
  • Prioritize systems where this driver is present and sysfs attributes are user-accessible.

Validation and detection

  • Inventory Linux systems for kernels and hardware using the Classmate laptop driver.
  • Confirm whether vendor kernels include one of the referenced stable fixes.
  • Review distribution security advisories for CVE-2026-23237 applicability.
  • Monitor kernel logs for NULL pointer dereference reports involving classmate-laptop.
Prepared
Confidence
medium
Sources
9

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-2026-23237 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
8Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux529aa8cb0a59367d08883f818e8c47028e819d0d, 529aa8cb0a59367d08883f818e8c47028e819d0d, 529aa8cb0a59367d08883f818e8c47028e819d0d, 529aa8cb0a59367d08883f818e8c47028e819d0d, 529aa8cb0a59367d08883f818e8c47028e819d0d, 529aa8cb0a59367d08883f818e8c47028e819d0d, 529aa8cb0a59367d08883f818e8c47028e819d0dunaffected
LinuxLinux2.6.33, 0, 5.10.251, 5.15.201, 6.1.164, 6.6.127, 6.12.74, 6.18.13, 6.19affected
Weakness

CWE details

No CWE listed

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