Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2024-47679— vfs: fix race between evice_inodes() and find_inode()&iput()

CVSS 7.8 · High EPSS 0.20% · P11

Affected Version Matrix 20

VendorProductVersion RangeStatus
LinuxLinux63997e98a3be68d7cec806d22bf9b02b2e1daabb< 6cc13a80a26e6b48f78c725c01b91987d61563efaffected
63997e98a3be68d7cec806d22bf9b02b2e1daabb< 489faddb1ae75b0e1a741fe5ca2542a2b5e794a5affected
63997e98a3be68d7cec806d22bf9b02b2e1daabb< 47a68c75052a660e4c37de41e321582ec9496195affected
63997e98a3be68d7cec806d22bf9b02b2e1daabb< 3721a69403291e2514d13a7c3af50a006ea1153baffected
63997e98a3be68d7cec806d22bf9b02b2e1daabb< 540fb13120c9eab3ef203f90c00c8e69f37449d1affected
63997e98a3be68d7cec806d22bf9b02b2e1daabb< 0eed942bc65de1f93eca7bda51344290f9c573bbaffected
63997e98a3be68d7cec806d22bf9b02b2e1daabb< 0f8a5b6d0dafa4f533ac82e98f8b812073a7c9d1affected
63997e98a3be68d7cec806d22bf9b02b2e1daabb< 6c857fb12b9137fee574443385d53914356bbe11affected
… +12 more rows
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2024-47679

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
vfs: fix race between evice_inodes() and find_inode()&iput()
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: vfs: fix race between evice_inodes() and find_inode()&iput() Hi, all Recently I noticed a bug[1] in btrfs, after digged it into and I believe it'a race in vfs. Let's assume there's a inode (ie ino 261) with i_count 1 is called by iput(), and there's a concurrent thread calling generic_shutdown_super(). cpu0: cpu1: iput() // i_count is 1 ->spin_lock(inode) ->dec i_count to 0 ->iput_final() generic_shutdown_super() ->__inode_add_lru() ->evict_inodes() // cause some reason[2] ->if (atomic_read(inode->i_count)) continue; // return before // inode 261 passed the above check // list_lru_add_obj() // and then schedule out ->spin_unlock() // note here: the inode 261 // was still at sb list and hash list, // and I_FREEING|I_WILL_FREE was not been set btrfs_iget() // after some function calls ->find_inode() // found the above inode 261 ->spin_lock(inode) // check I_FREEING|I_WILL_FREE // and passed ->__iget() ->spin_unlock(inode) // schedule back ->spin_lock(inode) // check (I_NEW|I_FREEING|I_WILL_FREE) flags, // passed and set I_FREEING iput() ->spin_unlock(inode) ->spin_lock(inode) ->evict() // dec i_count to 0 ->iput_final() ->spin_unlock() ->evict() Now, we have two threads simultaneously evicting the same inode, which may trigger the BUG(inode->i_state & I_CLEAR) statement both within clear_inode() and iput(). To fix the bug, recheck the inode->i_count after holding i_lock. Because in the most scenarios, the first check is valid, and the overhead of spin_lock() can be reduced. If there is any misunderstanding, please let me know, thanks. [1]: https://lore.kernel.org/linux-btrfs/000000000000eabe1d0619c48986@google.com/ [2]: The reason might be 1. SB_ACTIVE was removed or 2. mapping_shrinkable() return false when I reproduced the bug.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于vfs子系统evice_inodes、find_inode和iput函数间有竞争条件问题。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 63997e98a3be68d7cec806d22bf9b02b2e1daabb ~ 6cc13a80a26e6b48f78c725c01b91987d61563ef -
LinuxLinux 2.6.37 -

II. Public POCs for CVE-2024-47679

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-47679

登录查看更多情报信息。

Patches & Fixes for CVE-2024-47679 (4)

Same Patch Batch · Linux · 2024-10-21 · 372 CVEs total

CVE-2022-489859.8 CRITICALnet: mana: Fix race on per-CQ variable napi work_done
CVE-2024-498559.8 CRITICALnbd: fix race between timeout and normal completion
CVE-2024-500339.8 CRITICALslip: make slhc_remember() more robust against malicious packets
CVE-2022-490039.8 CRITICALnvme: fix SRCU protection of nvme_ns_head list
CVE-2024-476959.8 CRITICALRDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds
CVE-2024-500469.8 CRITICALNFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies()
CVE-2024-500479.8 CRITICALsmb: client: fix UAF in async decryption
CVE-2024-500439.8 CRITICALnfsd: fix possible badness in FREE_STATEID
CVE-2024-499969.4 CRITICALcifs: Fix buffer overflow when parsing NFS reparse points
CVE-2024-476789.4 CRITICALicmp: change the order of rate limits
CVE-2024-499508.8 HIGHBluetooth: L2CAP: Fix uaf in l2cap_connect
CVE-2024-499368.8 HIGHnet/xen-netback: prevent UAF in xenvif_flush_hash()
CVE-2022-490178.8 HIGHtipc: re-fetch skb cb after tipc_msg_validate
CVE-2022-490158.8 HIGHnet: hsr: Fix potential use-after-free
CVE-2024-499398.8 HIGHwifi: rtw89: avoid to add interface to list twice when SER
CVE-2024-500418.8 HIGHi40e: Fix macvlan leak by synchronizing access to mac_filter_hash
CVE-2024-499308.8 HIGHwifi: ath11k: fix array out-of-bound access in SoC stats
CVE-2022-489678.8 HIGHNFC: nci: Bounds check struct nfc_target arrays
CVE-2022-489648.8 HIGHravb: Fix potential use-after-free in ravb_rx_gbeth()
CVE-2022-489628.8 HIGHnet: hisilicon: Fix potential use-after-free in hisi_femac_rx()

Showing top 20 of 372 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2024-47679

No comments yet


Leave a comment