LiveActive security incident?Get immediate response
CVE Record

CVE-2024-41049: filelock: fix potential use-after-free in posix_lock_inode

In the Linux kernel, the following vulnerability has been resolved: filelock: fix potential use-after-free in posix_lock_inode Light Hsieh reported a KASAN UAF warning in trace_posix_lock_inode(). The request pointer had been changed earlier to point to a lock entry that was added to the inode's list. However, before the tracepoint could fire, another task raced in and freed that lock. Fix this by moving the tracepoint inside the spinlock, which should ensure that this doesn't happen.

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-41049 is a Linux kernel memory-safety bug in file locking. A race condition can let tracing code touch a lock object after another task has freed it. The public record confirms a kernel fix, but provides no CVSS score, clear impact rating, or evidence of active exploitation.

Executive priority

Handle through normal kernel patch governance unless exposed Linux fleets run untrusted workloads. Escalate if your estate includes shared hosting, build runners, or multi-tenant systems where local kernel bugs carry higher business risk.

Technical view

The issue is a potential use-after-free in posix_lock_inode involving trace_posix_lock_inode(). The request pointer can be changed to a lock added to an inode list, then another task can race and free that lock before the tracepoint fires. The fix moves the tracepoint inside the spinlock.

Likely exposure

Exposure is limited to systems running affected Linux kernel builds. The source bundle lists Linux kernel commit and version references, but does not provide distribution-by-distribution package status except a Debian LTS advisory reference.

Exploitation context

The bundle reports no KEV listing and no cited active exploitation. It describes a KASAN-discovered use-after-free race, not a public exploit path. Treat exploitation feasibility and impact as unproven from these sources.

Researcher notes

Evidence supports a kernel race-triggered use-after-free fixed by locking scope adjustment. Public data does not establish privilege impact, exploitability, or affected distribution packages beyond referenced upstream commits and Debian LTS notice.

Mitigation direction

  • Update affected Linux kernels using vendor-supported packages or kernel stable fixes.
  • Review Debian LTS advisory guidance if running affected Debian LTS systems.
  • Prioritize hosts running untrusted local workloads or shared multi-user Linux environments.
  • Track distribution advisories for backported fixes matching the referenced kernel commits.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, containers hosts, and appliances.
  • Compare installed kernels with vendor advisories and the referenced stable kernel fixes.
  • Confirm patched package changelogs mention CVE-2024-41049 or the filelock fix.
  • Check vulnerability scanner results against actual running kernel versions, not only installed packages.
Prepared
Confidence
medium
Sources
10

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-41049 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
9Source 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
LinuxLinux117fb80cd1e63c419c7a221ce070becb4bfc7b6d, a6f4129378ca15f62cbdde09a7d3ccc35adcf49d, 766e56faddbec2eaf70c9299e1c9ef74d846d32b, 34bff6d850019e00001129d6de3aa4874c2cf471, 74f6f5912693ce454384eaeec48705646a21c74f, 74f6f5912693ce454384eaeec48705646a21c74f, 74f6f5912693ce454384eaeec48705646a21c74f, e75396988bb9b3b90e6e8690604d0f566cea403a, 5.4.257, 5.10.197, 5.15.133, 6.1.55, 6.5.5unaffected
LinuxLinux6.6, 0, 5.4.280, 5.10.222, 5.15.163, 6.1.100, 6.6.41, 6.9.10, 6.10affected
Weakness

CWE details

No CWE listed

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