LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38092: ksmbd: use list_first_entry_or_null for opinfo_get_list()

In the Linux kernel, the following vulnerability has been resolved: ksmbd: use list_first_entry_or_null for opinfo_get_list() The list_first_entry() macro never returns NULL. If the list is empty then it returns an invalid pointer. Use list_first_entry_or_null() to check if the list is empty.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Linux’s ksmbd SMB server can produce an invalid pointer when internal operation information is requested from an empty list. The supplied CVSS score is 8.8, indicating potentially severe confidentiality, integrity, and availability impact. Actual consequences are not demonstrated in the supplied evidence.

Executive priority

Prioritize internet-accessible or broadly reachable ksmbd servers for prompt assessment and patching. Treat internal, tightly restricted servers as high-priority maintenance rather than an emergency unless instability or suspicious activity is observed.

Technical view

opinfo_get_list() used list_first_entry(), which does not return NULL for an empty list and instead yields an invalid pointer. The correction uses list_first_entry_or_null() so the empty-list condition can be handled safely. The evidence does not specify the resulting crash, corruption, or code-execution behavior.

Likely exposure

Exposure requires a Linux system using ksmbd and a path for a low-privileged network user to reach the affected behavior. Systems without ksmbd enabled are unlikely to be exposed. Precise vulnerable version ranges are absent; the bundle lists releases 6.6.88, 6.12.25, and 6.14.4 as unaffected.

Exploitation context

The CVSS vector indicates network reachability, low complexity, low privileges, and no user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public working exploit.

Researcher notes

The root cause is unsafe empty-list handling in opinfo_get_list(). Four stable-kernel correction commits are referenced. The supplied affected-version data is incomplete and labels listed commits and releases as unaffected, so downstream vendor advisories are necessary for exact exposure mapping.

Mitigation direction

  • Apply a vendor-supported kernel containing the referenced ksmbd correction.
  • Check distribution advisories to determine affected and fixed package versions.
  • Disable ksmbd if it is unnecessary and operationally safe to do so.
  • Restrict SMB access to trusted networks and authorized accounts.

Validation and detection

  • Inventory systems with ksmbd installed, loaded, or enabled.
  • Identify running kernel and distribution package versions.
  • Confirm the vendor kernel includes the referenced correction.
  • Review SMB exposure, authentication requirements, and network access controls.
  • Monitor kernel and ksmbd logs for crashes or abnormal behavior.
Prepared
Confidence
medium
Sources
6

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-2025-38092 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
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/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
5Source 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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux296cb5457cc6f4a754c4ae29855f8a253d52bcc6, d54ab1520d43e95f9b2e22d7a05fc9614192e5a5, d73686367ad68534257cd88a36ca3c52cb8b81d8, 18b4fac5ef17f77fed9417d22210ceafd6525fc7unaffected
LinuxLinux6.6.88, 6.12.25, 6.14.4unaffected
Weakness

CWE details

No CWE listed

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