目標達成 すべての支援者に感謝 — 100%達成しました!

目標: 1000 CNY · 調達済み: 1336 CNY

100%

CVE-2024-35877— Linux kernel 安全漏洞

AI Predicted 5.5 Difficulty: Easy EPSS 0.25% · P17

Possible ATT&CK Techniques 1AI

T1057 · Process Discovery

Affected Version Matrix 18

ベンダープロダクトVersion Rangeステータス
LinuxLinux5899329b19100c0b82dc78e9b21ed8b920c9ffb3< f18681daaec9665a15c5e7e0f591aad5d0ac622baffected
5899329b19100c0b82dc78e9b21ed8b920c9ffb3< 09e6bb53217bf388a0d2fd7fb21e74ab9dffc173affected
5899329b19100c0b82dc78e9b21ed8b920c9ffb3< c2b2430b48f3c9eaccd2c3d2ad75bb540d4952f4affected
5899329b19100c0b82dc78e9b21ed8b920c9ffb3< 7cfee26d1950250b14c5cb0a37b142f3fcc6396aaffected
5899329b19100c0b82dc78e9b21ed8b920c9ffb3< 97e93367e82752e475a33839a80b33bdbef1209faffected
5899329b19100c0b82dc78e9b21ed8b920c9ffb3< 51b7841f3fe84606ec0bd8da859d22e05e5419ecaffected
5899329b19100c0b82dc78e9b21ed8b920c9ffb3< 1341e4b32e1fb1b0acd002ccd56f07bd32f2abc6affected
5899329b19100c0b82dc78e9b21ed8b920c9ffb3< 04c35ab3bdae7fefbd7c7a7355f29fa03a035221affected
… +10 more rows
新しい脆弱性情報の通知を購読するログインして購読

I. CVE-2024-35877の基本情報

脆弱性情報

脆弱性についてご質問がありますか?Shenlongの分析が参考になるかご確認ください!
Shenlongの10の質問を表示 ↗

高度な大規模言語モデル技術を使用していますが、出力には不正確または古い情報が含まれる可能性があります。Shenlongはデータの正確性を確保するよう努めていますが、実際の状況に基づいて検証・判断してください。

脆弱性タイトル
x86/mm/pat: fix VM_PAT handling in COW mappings
ソース: CVE Program / CVE List V5
脆弱性説明
In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: fix VM_PAT handling in COW mappings PAT handling won't do the right thing in COW mappings: the first PTE (or, in fact, all PTEs) can be replaced during write faults to point at anon folios. Reliably recovering the correct PFN and cachemode using follow_phys() from PTEs will not work in COW mappings. Using follow_phys(), we might just get the address+protection of the anon folio (which is very wrong), or fail on swap/nonswap entries, failing follow_phys() and triggering a WARN_ON_ONCE() in untrack_pfn() and track_pfn_copy(), not properly calling free_pfn_range(). In free_pfn_range(), we either wouldn't call memtype_free() or would call it with the wrong range, possibly leaking memory. To fix that, let's update follow_phys() to refuse returning anon folios, and fallback to using the stored PFN inside vma->vm_pgoff for COW mappings if we run into that. We will now properly handle untrack_pfn() with COW mappings, where we don't need the cachemode. We'll have to fail fork()->track_pfn_copy() if the first page was replaced by an anon folio, though: we'd have to store the cachemode in the VMA to make this work, likely growing the VMA size. For now, lets keep it simple and let track_pfn_copy() just fail in that case: it would have failed in the past with swap/nonswap entries already, and it would have done the wrong thing with anon folios. Simple reproducer to trigger the WARN_ON_ONCE() in untrack_pfn(): <--- C reproducer ---> #include <stdio.h> #include <sys/mman.h> #include <unistd.h> #include <liburing.h> int main(void) { struct io_uring_params p = {}; int ring_fd; size_t size; char *map; ring_fd = io_uring_setup(1, &p); if (ring_fd < 0) { perror("io_uring_setup"); return 1; } size = p.sq_off.array + p.sq_entries * sizeof(unsigned); /* Map the submission queue ring MAP_PRIVATE */ map = mmap(0, size, PROT_READ | PROT_WRITE, MAP_PRIVATE, ring_fd, IORING_OFF_SQ_RING); if (map == MAP_FAILED) { perror("mmap"); return 1; } /* We have at least one page. Let's COW it. */ *map = 0; pause(); return 0; } <--- C reproducer ---> On a system with 16 GiB RAM and swap configured: # ./iouring & # memhog 16G # killall iouring [ 301.552930] ------------[ cut here ]------------ [ 301.553285] WARNING: CPU: 7 PID: 1402 at arch/x86/mm/pat/memtype.c:1060 untrack_pfn+0xf4/0x100 [ 301.553989] Modules linked in: binfmt_misc nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_g [ 301.558232] CPU: 7 PID: 1402 Comm: iouring Not tainted 6.7.5-100.fc38.x86_64 #1 [ 301.558772] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebu4 [ 301.559569] RIP: 0010:untrack_pfn+0xf4/0x100 [ 301.559893] Code: 75 c4 eb cf 48 8b 43 10 8b a8 e8 00 00 00 3b 6b 28 74 b8 48 8b 7b 30 e8 ea 1a f7 000 [ 301.561189] RSP: 0018:ffffba2c0377fab8 EFLAGS: 00010282 [ 301.561590] RAX: 00000000ffffffea RBX: ffff9208c8ce9cc0 RCX: 000000010455e047 [ 301.562105] RDX: 07fffffff0eb1e0a RSI: 0000000000000000 RDI: ffff9208c391d200 [ 301.562628] RBP: 0000000000000000 R08: ffffba2c0377fab8 R09: 0000000000000000 [ 301.563145] R10: ffff9208d2292d50 R11: 0000000000000002 R12: 00007fea890e0000 [ 301.563669] R13: 0000000000000000 R14: ffffba2c0377fc08 R15: 0000000000000000 [ 301.564186] FS: 0000000000000000(0000) GS:ffff920c2fbc0000(0000) knlGS:0000000000000000 [ 301.564773] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 301.565197] CR2: 00007fea88ee8a20 CR3: 00000001033a8000 CR4: 0000000000750ef0 [ 301.565725] PKRU: 55555554 [ 301.565944] Call Trace: [ 301.566148] <TASK> [ 301.566325] ? untrack_pfn+0xf4/0x100 [ 301.566618] ? __warn+0x81/0x130 [ 301.566876] ? untrack_pfn+0xf4/0x100 [ 3 ---truncated---
ソース: CVE Program / CVE List V5
CVSS情報
N/A
ソース: CVE Program / CVE List V5
脆弱性タイプ
N/A
ソース: CVE Program / CVE List V5
脆弱性タイトル
Linux kernel 安全漏洞
ソース: CNNVD (China National Vulnerability Database)
脆弱性説明
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel 存在安全漏洞,该漏洞源于 x86/mm/pat 模块存在漏洞。
ソース: CNNVD (China National Vulnerability Database)
CVSS情報
N/A
ソース: CNNVD (China National Vulnerability Database)
脆弱性タイプ
N/A
ソース: CNNVD (China National Vulnerability Database)

影響を受ける製品

ベンダープロダクト影響を受けるバージョンCPE購読
LinuxLinux 5899329b19100c0b82dc78e9b21ed8b920c9ffb3 ~ f18681daaec9665a15c5e7e0f591aad5d0ac622b -
LinuxLinux 2.6.29 -

II. CVE-2024-35877の公開POC

#POC説明ソースリンクShenlongリンク
AI生成POCプレミアム

公開POCは見つかりませんでした。

ログインしてAI POCを生成

III. CVE-2024-35877のインテリジェンス情報

登录查看更多情报信息。

CVE-2024-35877 邮件列表归档 (2)

CVE-2024-35877 其他参考 (6)

Same Patch Batch · Linux · 2024-05-19 · 82 CVEs total

CVE-2024-358619.8 CRITICALsmb: client: fix potential UAF in cifs_signal_cifsd_for_reconnect()
CVE-2024-358629.8 CRITICALsmb: client: fix potential UAF in smb2_is_network_name_deleted()
CVE-2024-358639.8 CRITICALsmb: client: fix potential UAF in is_valid_oplock_break()
CVE-2024-358649.8 CRITICALsmb: client: fix potential UAF in smb2_is_valid_lease_break()
CVE-2024-358659.8 CRITICALsmb: client: fix potential UAF in smb2_is_valid_oplock_break()
CVE-2024-358849.8 CRITICALudp: do not accept non-tunnel GSO skbs landing in a tunnel
CVE-2024-358709.8 CRITICALsmb: client: fix UAF in smb2_reconnect_server()
CVE-2024-358699.8 CRITICALsmb: client: guarantee refcounted children from parent session
CVE-2024-359399.3 CRITICALdma-direct: Leak pages on dma_set_decrypted() failure
CVE-2024-358878.8 HIGHax25: fix use-after-free bugs caused by ax25_ds_del_timer
CVE-2024-359158.8 HIGHnfc: nci: Fix uninit-value in nci_dev_up and nci_ntf_packet
CVE-2024-358898.6 HIGHidpf: fix kernel panic on unknown packet types
CVE-2024-358758.4 HIGHx86/coco: Require seeding RNG with RDRAND on CoCo systems
CVE-2024-359378.1 HIGHwifi: cfg80211: check A-MSDU format more carefully
CVE-2024-359197.8 HIGHmedia: mediatek: vcodec: adding lock to protect encoder context list
CVE-2024-359317.8 HIGHdrm/amdgpu: Skip do PCI error slot reset during RAS recovery
CVE-2024-358907.8 HIGHgro: fix ownership transfer
CVE-2024-359207.8 HIGHmedia: mediatek: vcodec: adding lock to protect decoder context list
CVE-2024-359217.8 HIGHmedia: mediatek: vcodec: Fix oops when HEVC init fails
CVE-2024-358977.8 HIGHnetfilter: nf_tables: discard table flag update with pending basechain deletion

Showing 20 of 82 CVEs. View all on vendor page →

IV. 関連脆弱性

V. CVE-2024-35877へのコメント

まだコメントはありません


コメントを残す