LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26836: platform/x86: think-lmi: Fix password opcode ordering for workstations

In the Linux kernel, the following vulnerability has been resolved: platform/x86: think-lmi: Fix password opcode ordering for workstations The Lenovo workstations require the password opcode to be run before the attribute value is changed (if Admin password is enabled). Tested on some Thinkpads to confirm they are OK with this order too.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects Lenovo firmware-management behavior through the think-lmi driver. On some Lenovo workstations, password handling must occur before changing a BIOS attribute when an Admin password is enabled. The source bundle does not describe data theft, privilege escalation, remote access, or service disruption impact.

Executive priority

Handle through normal kernel maintenance unless your fleet centrally manages Lenovo BIOS settings from Linux. There is no source-backed evidence of active exploitation or severe business impact, but affected Lenovo administration workflows should be patched to avoid unreliable firmware configuration behavior.

Technical view

CVE-2024-26836 is a Linux kernel platform/x86 think-lmi fix for password opcode ordering. The cited fix changes the ordering so Lenovo workstations run the password opcode before setting an attribute value. The bundle lists Linux kernel versions including 5.17, 6.6.55, 6.7.7, and 6.8 as affected, with stable kernel commits referenced.

Likely exposure

Exposure is most relevant to Linux systems using the Lenovo think-lmi platform driver for firmware or BIOS attribute management, especially Lenovo workstations with an Admin password enabled. General Linux systems without this driver or Lenovo firmware-management workflow are less likely to be practically exposed.

Exploitation context

The provided sources do not show active exploitation, public exploit availability, KEV listing, CVSS score, CWE, or a concrete attacker path. Treat exploitation context as incomplete rather than assuming exploitability.

Researcher notes

The record is sparse: no CVSS, CWE, exploit narrative, or explicit security consequence is provided. Analysis should stay close to the kernel fix description and avoid inferring remote attack, privilege escalation, or unauthorized BIOS modification without additional vendor evidence.

Mitigation direction

  • Check Linux distribution advisories for kernels containing the referenced stable fixes.
  • Prioritize updates on Lenovo workstations using think-lmi firmware attribute management.
  • Verify patched kernel packages before changing firmware attributes on Admin-password-protected systems.
  • Track CVE metadata for later CVSS, CWE, or vendor impact clarification.

Validation and detection

  • Inventory Linux kernel versions on Lenovo workstation and ThinkPad fleets.
  • Check whether the think-lmi driver is present or used for firmware settings.
  • Confirm installed kernel packages include one of the referenced stable fixes.
  • Review change-management records for BIOS attribute workflows using Admin passwords.
Prepared
Confidence
medium
Sources
5

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.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-26836 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
4Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux640a5fa50a42b99bfa2a0ec51b4ea9591d9bd055, 640a5fa50a42b99bfa2a0ec51b4ea9591d9bd055, 640a5fa50a42b99bfa2a0ec51b4ea9591d9bd055unaffected
LinuxLinux5.17, 0, 6.6.55, 6.7.7, 6.8affected
Weakness

CWE details

No CWE listed

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