CVE-2026-31673: af_unix: read UNIX_DIAG_VFS data under unix_state_lock
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.
Security readout for executives and security teams
Plain-English summary
A local, low-privileged Linux user may trigger a race while the kernel reports UNIX socket filesystem information. The kernel can read path data while another operation releases it, potentially compromising confidentiality, integrity, or availability. Network-only attackers are not indicated by the supplied CVSS vector.
Executive priority
Prioritize timely remediation on shared, multi-user, and untrusted-workload Linux hosts. Treat this as high severity but not an internet-routable emergency based on current evidence. Routine single-user systems can follow risk-based kernel maintenance after exposure is verified.
Technical view
Exact UNIX socket diagnostic lookups retain the socket but not its path. Concurrent socket release clears and later drops that path reference. The fix reads inode and device values while holding unix_state_lock, then emits the netlink attribute after unlocking, keeping UNIX_DIAG_VFS data stable.
Likely exposure
Exposure requires an affected Linux kernel and local low-privileged access. Multi-user systems and hosts running untrusted workloads deserve particular attention. The supplied affected-version data is ambiguous, including unusual and duplicated entries, so determine exposure through distribution advisories and fix-commit inclusion rather than version strings alone.
Exploitation context
The CVSS 3.1 score is 7.8 with local access, low complexity, low privileges, and no user interaction. The record is not marked as CISA KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. Exploitability beyond the stated vector remains unconfirmed.
Researcher notes
The flaw is a synchronization and lifetime issue around u->path during UNIX_DIAG_VFS reply construction. The correction snapshots inode and device numbers under unix_state_lock. The source bundle does not identify a CWE, crash signature, proof of concept, exploitation telemetry, or vendor-specific package boundaries.
Mitigation direction
Install a vendor-supported kernel containing the applicable stable fix commit.
Reboot into the updated kernel after installation.
If patching is delayed, reduce untrusted local access where operationally feasible.
Check distribution guidance for branch-specific packages and compensating controls.
Validation and detection
Inventory running kernel versions across Linux systems.
Map each kernel package to its distribution security advisory.
Confirm the running kernel contains the applicable stable fix.
Verify systems rebooted into the corrected kernel, not merely installed it.
Monitor vendor advisories for clarified affected ranges or exploitation evidence.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-31673 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.