LiveActive security incident?Get immediate response
CVE Record

CVE-2025-40202: ipmi: Rework user message limit handling

In the Linux kernel, the following vulnerability has been resolved: ipmi: Rework user message limit handling The limit on the number of user messages had a number of issues, improper counting in some cases and a use after free. Restructure how this is all done to handle more in the receive message allocation routine, so all refcouting and user message limit counts are done in that routine. It's a lot cleaner and safer.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Linux IPMI message handling can cause a use-after-free when enforcing per-user message limits. A locally authenticated, low-privileged attacker may be able to crash the system or potentially compromise sensitive data and system integrity. The supplied CVSS score is 7.8, making this a high-severity issue.

Executive priority

Treat as a high-priority kernel update for systems exposing IPMI functionality to local users. Internet-facing emergency patching is not indicated by the supplied evidence because exploitation requires local access and active exploitation is unconfirmed. Accelerate remediation where untrusted users, shared hosting, or compromised service accounts could obtain local execution.

Technical view

The Linux kernel IPMI subsystem incorrectly counted user messages and mishandled object lifetimes, creating a use-after-free. The fix centralizes allocation, reference counting, and limit accounting in the receive-message allocation routine. The CVSS vector requires local access and low privileges, with no user interaction; confidentiality, integrity, and availability impacts are rated high.

Likely exposure

Exposure is most likely on systems running an affected Linux kernel and using the IPMI user-message interface. Exploitation requires local, low-privileged access according to the supplied CVSS vector. The bundle identifies affected versions but does not preserve sufficiently clear range semantics, so confirm applicability against the appropriate kernel or distribution advisory.

Exploitation context

The supplied record is not listed in CISA KEV, and no cited source establishes active exploitation or a public proof of concept. The vulnerability is not remotely reachable under the supplied CVSS vector; an attacker must already have local low-privileged access. Practical exploitability and reliability are not established by the bundle.

Researcher notes

The record describes improper message counting and a use-after-free but assigns no CWE and provides no triggering details. Five stable-kernel commits are cited, apparently covering multiple maintained branches. Exact affected ranges are unclear in the supplied normalized version list; validate branch ancestry or rely on distribution advisories rather than interpreting the listed versions as complete boundaries.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable referenced stable fix.
  • Consult the Linux distribution advisory to confirm corrected package versions and reboot requirements.
  • Prioritize multi-user, administrative, virtualization, and server-management systems where local accounts and IPMI coexist.
  • Restrict unnecessary local access and IPMI device permissions until patched.

Validation and detection

  • Record the running kernel release and distribution package version on potentially exposed systems.
  • Confirm whether IPMI modules and the user-message interface are present or used.
  • Compare kernel packages against distribution guidance and the referenced stable commits.
  • After updating, verify the corrected kernel is running following any required reboot.
Prepared
Confidence
medium
Sources
7

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-2025-40202 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-40202Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
LinuxLinux8e76741c3d8b20dfa2d6c30fa10ff927cfd93d82, 8e76741c3d8b20dfa2d6c30fa10ff927cfd93d82, 8e76741c3d8b20dfa2d6c30fa10ff927cfd93d82, 8e76741c3d8b20dfa2d6c30fa10ff927cfd93d82, 8e76741c3d8b20dfa2d6c30fa10ff927cfd93d82unaffected
LinuxLinux5.19, 0, 6.1.157, 6.6.113, 6.12.54, 6.17.4, 6.18affected
Weakness

CWE details

No CWE listed

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