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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2025-40214— af_unix: Initialise scc_index in unix_add_edge().

EPSS 0.03% · P9
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2025-40214

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
af_unix: Initialise scc_index in unix_add_edge().
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: af_unix: Initialise scc_index in unix_add_edge(). Quang Le reported that the AF_UNIX GC could garbage-collect a receive queue of an alive in-flight socket, with a nice repro. The repro consists of three stages. 1) 1-a. Create a single cyclic reference with many sockets 1-b. close() all sockets 1-c. Trigger GC 2) 2-a. Pass sk-A to an embryo sk-B 2-b. Pass sk-X to sk-X 2-c. Trigger GC 3) 3-a. accept() the embryo sk-B 3-b. Pass sk-B to sk-C 3-c. close() the in-flight sk-A 3-d. Trigger GC As of 2-c, sk-A and sk-X are linked to unix_unvisited_vertices, and unix_walk_scc() groups them into two different SCCs: unix_sk(sk-A)->vertex->scc_index = 2 (UNIX_VERTEX_INDEX_START) unix_sk(sk-X)->vertex->scc_index = 3 Once GC completes, unix_graph_grouped is set to true. Also, unix_graph_maybe_cyclic is set to true due to sk-X's cyclic self-reference, which makes close() trigger GC. At 3-b, unix_add_edge() allocates unix_sk(sk-B)->vertex and links it to unix_unvisited_vertices. unix_update_graph() is called at 3-a. and 3-b., but neither unix_graph_grouped nor unix_graph_maybe_cyclic is changed because both sk-B's listener and sk-C are not in-flight. 3-c decrements sk-A's file refcnt to 1. Since unix_graph_grouped is true at 3-d, unix_walk_scc_fast() is finally called and iterates 3 sockets sk-A, sk-B, and sk-X: sk-A -> sk-B (-> sk-C) sk-X -> sk-X This is totally fine. All of them are not yet close()d and should be grouped into different SCCs. However, unix_vertex_dead() misjudges that sk-A and sk-B are in the same SCC and sk-A is dead. unix_sk(sk-A)->scc_index == unix_sk(sk-B)->scc_index <-- Wrong! && sk-A's file refcnt == unix_sk(sk-A)->vertex->out_degree ^-- 1 in-flight count for sk-B -> sk-A is dead !? The problem is that unix_add_edge() does not initialise scc_index. Stage 1) is used for heap spraying, making a newly allocated vertex have vertex->scc_index == 2 (UNIX_VERTEX_INDEX_START) set by unix_walk_scc() at 1-c. Let's track the max SCC index from the previous unix_walk_scc() call and assign the max + 1 to a new vertex's scc_index. This way, we can continue to avoid Tarjan's algorithm while preventing misjudgments.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于未初始化scc_index,可能导致垃圾回收错误。
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 adfb68b39b39767d6bfb53e48c4f19c183765686 ~ 20003fbb9174121b27bd1da6ebe61542ac4c327d -
LinuxLinux 6.10 -

II. Public POCs for CVE-2025-40214

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-40214

登录查看更多情报信息。

Same Patch Batch · Linux · 2025-12-04 · 53 CVEs total

CVE-2025-40230mm: prevent poison consumption when splitting THP
CVE-2025-40215xfrm: delete x->tunnel as we delete x
CVE-2025-40216io_uring/rsrc: don't rely on user vaddr alignment
CVE-2025-40221media: pci: mg4b: fix uninitialized iio scan data
CVE-2025-40218mm/damon/vaddr: do not repeat pte_offset_map_lock() until success
CVE-2025-40219PCI/IOV: Fix race between SR-IOV enable/disable and hotplug
CVE-2025-40220fuse: fix livelock in synchronous file put from fuseblk workers
CVE-2025-40217pidfs: validate extensible ioctls
CVE-2025-40228mm/damon/sysfs: catch commit test ctx alloc failure
CVE-2025-40229mm/damon/core: fix potential memory leak by cleaning ops_filter in damon_destroy_scheme
CVE-2025-40227mm/damon/sysfs: dealloc commit test ctx always
CVE-2025-40231vsock: fix lock inversion in vsock_assign_transport()
CVE-2025-40232rv: Fully convert enabled_monitors to use list_head as iterator
CVE-2025-40233ocfs2: clear extent cache after moving/defragmenting extents
CVE-2025-40234platform/x86: alienware-wmi-wmax: Fix NULL pointer dereference in sleep handlers
CVE-2025-40236virtio-net: zero unused hash fields
CVE-2025-40235btrfs: directly free partially initialized fs_info in btrfs_check_leaked_roots()
CVE-2025-40237fs/notify: call exportfs_encode_fid with s_umount
CVE-2025-40238net/mlx5: Fix IPsec cleanup over MPV device
CVE-2025-40239net: phy: micrel: always set shared->phydev for LAN8814

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

IV. Related Vulnerabilities

V. Comments for CVE-2025-40214

No comments yet


Leave a comment