LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27058: tmpfs: fix race on handling dquot rbtree

In the Linux kernel, the following vulnerability has been resolved: tmpfs: fix race on handling dquot rbtree A syzkaller reproducer found a race while attempting to remove dquot information from the rb tree. Fetching the rb_tree root node must also be protected by the dqopt->dqio_sem, otherwise, giving the right timing, shmem_release_dquot() will trigger a warning because it couldn't find a node in the tree, when the real reason was the root node changing before the search starts: Thread 1 Thread 2 - shmem_release_dquot() - shmem_{acquire,release}_dquot() - fetch ROOT - Fetch ROOT - acquire dqio_sem - wait dqio_sem - do something, triger a tree rebalance - release dqio_sem - acquire dqio_sem - start searching for the node, but from the wrong location, missing the node, and triggering a warning.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-27058 is a Linux kernel race in tmpfs quota bookkeeping. Concurrent quota operations can search a changing red-black tree from an outdated root, causing a kernel warning. The supplied CVSS rates potential confidentiality, integrity, and availability impact as high, but the description does not demonstrate those outcomes.

Executive priority

Treat as a high-priority kernel maintenance issue on multi-user or less-trusted workload hosts. It is not described as remotely exploitable, and active exploitation is unconfirmed. Accelerate normal patching where affected kernels and tmpfs quota usage coincide; validate distributor backports before declaring exposure resolved.

Technical view

The tmpfs dquot release path fetched the quota tree root before acquiring dqopt->dqio_sem. Another thread could rebalance the tree first, leaving the search at the wrong location and falsely missing an existing node. The referenced stable commits protect root retrieval with the same semaphore.

Likely exposure

Exposure applies to Linux systems running affected kernel revisions, particularly where tmpfs quota operations are used and a locally authenticated user can trigger concurrent activity. The bundle lists affected releases including 6.6, 6.6.24, 6.7.12, 6.8.3, and 6.9, but provides incomplete range semantics.

Exploitation context

The CVSS vector indicates local access, low complexity, low privileges, and no user interaction. A syzkaller reproducer discovered the race. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public weaponized exploit.

Researcher notes

The documented defect is a synchronization error around dquot red-black-tree root retrieval. The immediate observed result is a warning after a failed lookup. Although CVSS assigns high C/I/A impacts, the bundle does not explain a proven path from the race to disclosure, modification, privilege escalation, or system compromise.

Mitigation direction

  • Apply the applicable Linux stable fix or distribution kernel update containing the referenced correction.
  • Confirm exact affected and fixed versions through your Linux distributor's current security guidance.
  • Restrict untrusted local access where immediate kernel remediation is unavailable.
  • Prioritize systems using tmpfs quotas or allowing less-trusted local workloads.

Validation and detection

  • Inventory running kernel versions and compare them with vendor-specific affected-version guidance.
  • Verify the installed kernel includes the applicable referenced stable commit or downstream backport.
  • Identify systems using tmpfs quota functionality and rank them for earlier remediation.
  • After updating, reboot into the corrected kernel and confirm the running version.
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-2024-27058 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.

2CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

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

CVSS vector scores

2 official scores

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
4.7CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L1.23.4CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-27058Attack 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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxeafc474e202978ac735c551d5ee1eb8c02e2be54, eafc474e202978ac735c551d5ee1eb8c02e2be54, eafc474e202978ac735c551d5ee1eb8c02e2be54, eafc474e202978ac735c551d5ee1eb8c02e2be54unaffected
LinuxLinux6.6, 0, 6.6.24, 6.7.12, 6.8.3, 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.