CVE-2026-31673
Received Received - Intake
Use-After-Free Vulnerability in Linux af_unix UNIX_DIAG_VFS Component

Publication date: 2026-04-25

Last updated on: 2026-04-27

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: af_unix: read UNIX_DIAG_VFS data under unix_state_lock Exact UNIX diag lookups hold a reference to the socket, but not to u->path. Meanwhile, unix_release_sock() clears u->path under unix_state_lock() and drops the path reference after unlocking. Read the inode and device numbers for UNIX_DIAG_VFS while holding unix_state_lock(), then emit the netlink attribute after dropping the lock. This keeps the VFS data stable while the reply is being built.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-25
Last Modified
2026-04-27
Generated
2026-05-07
AI Q&A
2026-04-26
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability involves the Linux kernel's handling of UNIX domain sockets diagnostics (UNIX_DIAG_VFS). Specifically, the kernel reads certain filesystem data (inode and device numbers) without properly holding a lock on the path reference, which can be cleared concurrently. The issue arises because the exact UNIX diag lookups hold a reference to the socket but not to the path, while the path can be cleared under a lock. This could lead to unstable or inconsistent data being read. The fix involves reading the inode and device numbers while holding the unix_state_lock to ensure data stability during the operation.


How can this vulnerability impact me? :

This vulnerability could cause the Linux kernel to read unstable or inconsistent filesystem data related to UNIX domain sockets. While the exact impact is not detailed, such inconsistencies might lead to incorrect diagnostic information or potential kernel instability during socket diagnostics operations.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart