nday
CVE-2024-45003

vfs: Don't evict inode under the inode lru traversing context

Linux / Linux

に公開されました。nday はまだ修正の根拠を取得していません。修正がないという意味ではありません。4 つの PoC ソースのいずれにも未掲載です。CISA KEV には現時点で未掲載です。

tags weakness typerace condition accesslocalno user interaction productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

race condition
CWE-667, stated by NVD's analysts
local
AV:L in CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
no user interaction
UI:N in CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
現在の段階
DIS
公開日時
CVSS 基本値
スコアなし

ライフサイクル

横軸は UTC。点=分単位、幅広の帯=日付のみ、白抜き=不明または推定。
日時不明
DIS公開
2024-09-04T19:54Z
PAT修正
記録なし
ANA解析
記録なし
POCPoC
記録なし
ITW悪用
記録なし
KEVKEV
記録なし

概要

In the Linux kernel, the following vulnerability has been resolved:

vfs: Don't evict inode under the inode lru traversing context

The inode reclaiming process(See function prune_icache_sb) collects all reclaimable inodes and mark them with I_FREEING flag at first, at that time, other processes will be stuck if they try getting these inodes (See function find_inode_fast), then the reclaiming process destroy the inodes by function dispose_list(). Some filesystems(eg. ext4 with ea_inode feature, ubifs with xattr) may do inode lookup in the inode evicting callback function, if the inode lookup is operated under the inode lru traversing context, deadlock problems may happen.

Case 1: In function ext4_evict_inode(), the ea inode lookup could happen if ea_inode feature is enabled, the lookup process will be stuck under the evicting context like this:

1. File A has inode i_reg and an ea inode i_ea 2. getfattr(A, xattr_buf) // i_ea is added into lru // lru->i_ea 3. Then, following three processes running like this:

   PA                              PB
echo 2 > /proc/sys/vm/drop_caches
 shrink_slab
  prune_dcache_sb
  // i_reg is added into lru, lru->i_ea->i_reg
  prune_icache_sb
   list_lru_walk_one
    inode_lru_isolate
     i_ea->i_state |= I_FREEING // set inode state
    inode_lru_isolate
     __iget(i_reg)
     spin_unlock(&i_reg->i_lock)
     spin_unlock(lru_lock)
                                    rm file A
                                     i_reg->nlink = 0
     iput(i_reg) // i_reg->nlink is 0, do evict
      ext4_evict_inode
       ext4_xattr_delete_inode
        ext4_xattr_inode_dec_ref_all
         ext4_xattr_inode_iget
          ext4_iget(i_ea->i_ino)
           iget_locked
            find_inode_fast
             __wait_on_freeing_inode(i_ea) ----→ AA deadlock
   dispose_list // cannot be executed by prune_icache_sb
    wake_up_bit(&i_ea->i_state)

Case 2: In deleted inode writing function ubifs_jnl_write_inode(), file deleting process holds BASEHD's wbuf->io_mutex while getting the xattr inode, which could race with inode reclaiming process(The reclaiming process could try locking BASEHD's wbuf->io_mutex in inode evicting function), then an ABBA deadlock problem would happen as following:

1. File A has inode ia and a xattr(with inode ixa), regular file B has inode ib and a xattr. 2. getfattr(A, xattr_buf) // ixa is added into lru // lru->ixa 3. Then, following three processes running like this:

PA                PB                        PC
        echo 2 > /proc/sys/vm/drop_caches
         shrink_slab
          prune_dcache_sb

// ib and ia are added into lru, lru->ixa->ib->ia

                 prune_icache_sb
                  list_lru_walk_one
                   inode_lru_isolate
                    ixa->i_state |= I_FREEING // set inode state
                   inode_lru_isolate
                    __iget(ib)
                    spin_unlock(&ib->i_lock)
                    spin_unlock(lru_lock)
                                                  rm file B
                                                   ib->nlink = 0
rm file A
 iput(ia)
  ubifs_evict_inode(ia)
   ubifs_jnl_delete_inode(ia)
    ubifs_jnl_write_inode(ia)
     make_reservation(BASEHD) // Lock wbuf->io_mutex
     ubifs_iget(ixa->i_ino)
      iget_locked
       find_inode_fast
        __wait_on_freeing_inode(ixa)
         |          iput(ib) // ib->nlink is 0, do evict
         |           ubifs_evict_inode
         |            ubifs_jnl_delete_inode(ib)
         ↓             ubifs_jnl_write_inode
    ABBA deadlock ←-----make_reservation(BASEHD)
                  dispose_list // cannot be executed by prune_icache_sb
                   wake_up_bit(&ixa->i_state)

Fix the possible deadlock by using new inode state flag I_LRU_ISOLATING to pin the inode in memory while inode_lru_isolate( ---truncated---

Original text of the CVE record (cvelist), shown as published.

イベント履歴

+DIS公開

Linux が CVE レコードを公開。

出典 cvelist · nday が に一括取り込み · 生データ
{
  "id": 340423,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2024-45003",
  "occurred_at": "2024-09-04T19:54:46.276Z",
  "observed_at": "2026-11-13T05:38:38.958665Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "ssvc": {
      "timestamp": "2024-09-04T20:18:27.700271Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2024-09-04T19:54:46.276Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

研究者の投稿

過去 7 日間に 0 人の研究者が言及

リストの研究者が X でこの CVE に触れた投稿です。原文のまま表示し、nday は検証していません。

リストの研究者が X でこの CVE に触れた投稿は、まだ収集していません。

Discussion

0 comments

No comments yet.