LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58087: ksmbd: fix racy issue from session lookup and expire

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix racy issue from session lookup and expire Increment the session reference count within the lock for lookup to avoid racy issue with session expire.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-58087 is a Linux kernel ksmbd flaw involving unsafe session handling during lookup and expiration. A network attacker needs no credentials, but exploitation is rated high complexity. If reachable ksmbd service is affected, impact can include loss of confidentiality, integrity, and availability.

Executive priority

Treat this as high priority for any Linux-hosted SMB service exposed beyond trusted internal networks. Risk is lower where ksmbd is not enabled or SMB is tightly restricted, but patch planning should still follow normal kernel maintenance urgency.

Technical view

The issue is a race condition in ksmbd session lookup and expiration. The kernel fix increments the session reference count while holding the relevant lock, addressing CWE-667 improper locking. CVSS 3.1 is 8.1: network attack vector, high complexity, no privileges, no user interaction, and high CIA impact.

Likely exposure

Exposure is most relevant to Linux systems using ksmbd for SMB service, especially where SMB is reachable over untrusted networks. Exact exposure depends on kernel branch, distro backports, and whether ksmbd is enabled.

Exploitation context

The provided bundle does not show CISA KEV listing or confirmed active exploitation. ZDI published an advisory, but the supplied evidence should not be treated as proof of in-the-wild exploitation.

Researcher notes

The core evidence identifies a locking race in ksmbd session reference handling. The bundle does not provide exploit details, affected distro package names, or a vendor mitigation beyond stable kernel fixes, so validation should focus on enabled ksmbd service and distro-specific patch status.

Mitigation direction

  • Update to vendor kernel packages containing the referenced stable ksmbd fixes.
  • Check Linux distribution advisories for exact fixed package versions and backports.
  • Disable ksmbd where SMB service is not required.
  • Restrict SMB exposure to trusted networks until patched.
  • Prioritize internet-facing or partner-facing SMB hosts for remediation.

Validation and detection

  • Inventory Linux hosts running ksmbd or kernel SMB server functionality.
  • Map kernel versions against vendor advisories and the referenced stable commits.
  • Confirm whether SMB ports are exposed to untrusted networks.
  • Verify patched hosts are running the updated kernel after reboot.
  • Review logs for abnormal ksmbd crashes or SMB session instability.
Prepared
Confidence
medium
Sources
8

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.

cwe · low confidence lookup

CWE-667: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-58087 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.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/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
1ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

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.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2024-58087Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0626e6641f6b467447c81dd7678a69c66f7746cf, 0626e6641f6b467447c81dd7678a69c66f7746cf, 0626e6641f6b467447c81dd7678a69c66f7746cf, 0626e6641f6b467447c81dd7678a69c66f7746cf, 0626e6641f6b467447c81dd7678a69c66f7746cfunaffected
LinuxLinux5.15, 0, 5.15.176, 6.1.121, 6.6.67, 6.12.6, 6.13affected
Weakness

CWE details

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

CWE-667 · source CWE mapping

Improper Locking

Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.