LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38580: epoll: be better about file lifetimes

In the Linux kernel, the following vulnerability has been resolved: epoll: be better about file lifetimes epoll can call out to vfs_poll() with a file pointer that may race with the last 'fput()'. That would make f_count go down to zero, and while the ep->mtx locking means that the resulting file pointer tear-down will be blocked until the poll returns, it means that f_count is already dead, and any use of it won't actually get a reference to the file any more: it's dead regardless. Make sure we have a valid ref on the file pointer before we call down to vfs_poll() from the epoll routines.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-38580 is a Linux kernel epoll file-lifetime race. The record says epoll could poll a file pointer while its final reference is being released, creating unsafe kernel object lifetime handling. The public sources do not provide CVSS, impact details, or evidence of exploitation.

Executive priority

Track and patch through normal kernel update governance, with higher urgency for shared hosts or systems running untrusted workloads. Current public evidence does not support emergency treatment, but missing severity data means exposure should not be ignored.

Technical view

The issue is in Linux kernel epoll calling vfs_poll() without ensuring a live file reference. A concurrent final fput() can drop f_count to zero before polling completes. Stable kernel commits change epoll to hold a valid reference before calling into vfs_poll().

Likely exposure

Exposure is limited to systems running affected Linux kernel versions identified in the CVE record. The bundle does not identify affected distributions, appliances, cloud images, or application products. Kernel packages may include backported fixes, so version-only checks need vendor confirmation.

Exploitation context

The source bundle provides no exploit status, no KEV listing, no CVSS vector, and no proof-of-concept reference. Because epoll is a kernel interface used by local processes, assess systems with untrusted local workloads carefully, but treat this as an inference from component context.

Researcher notes

Evidence is sparse. The CVE text describes a race around epoll, vfs_poll(), fput(), and f_count lifetime handling. No CWE, CVSS, exploitability assessment, affected distro matrix, or runtime symptom is included in the provided bundle.

Mitigation direction

  • Apply vendor Linux kernel updates that include the referenced stable fixes.
  • Check distribution advisories for backported CVE-2024-38580 fixes.
  • Prioritize shared, multi-tenant, container, and untrusted workload hosts.
  • If updates are delayed, request vendor-supported mitigation guidance.
  • Avoid assuming fixed status from upstream version numbers alone.

Validation and detection

  • Inventory running Linux kernel packages across exposed and production systems.
  • Confirm whether vendor packages include CVE-2024-38580 backports.
  • Review kernel changelogs for the referenced epoll lifetime fix commits.
  • Run normal regression testing after kernel updates.
  • Document any unsupported kernels requiring upgrade or replacement.
Prepared
Confidence
medium
Sources
7

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-2024-38580 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
6Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 5.15.161, 6.1.93, 6.6.33, 6.8.12, 6.9affected
Weakness

CWE details

No CWE listed

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