CVE-2026-31673

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-25. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

April 25, 2026

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated May 7, 2026
No patch confirmed yet.
generic

af_unix: read UNIX_DIAG_VFS data under unix_state_lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bdf206e740bf2919d818f132c8c9cc7ed91d11c0
generic

af_unix: read UNIX_DIAG_VFS data under unix_state_lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b9232421a77a649c9376c99fdfc8cb7f79cad34c
generic

af_unix: read UNIX_DIAG_VFS data under unix_state_lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/900a4e0910e98b8caef117d5df00471fa438dcf9
generic

af_unix: read UNIX_DIAG_VFS data under unix_state_lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39897df386376912d561d4946499379effa1e7ef
generic

af_unix: read UNIX_DIAG_VFS data under unix_state_lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0c739f3785f84af695952c2bac8be2f45082c9b8

Vendor Advisories for CVE-2026-31673(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.258—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (126 versions)6.19.14-1—

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 68× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 248 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-04 02:59 UTCOSV refresh
  3. 2026-09-02 14:11 UTCEPSS rescore
  4. 2026-09-01 13:53 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-09-01 04:39 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-24 14:17 UTCEPSS rescore
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 17:03 UTCEPSS rescore
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 14:45 UTCEG score recompute
  20. 2026-08-17 14:45 UTCVendor advisory
  21. 2026-08-17 14:45 UTCGHSA enrichment
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 05:44 UTCEG score recompute
  25. 2026-08-16 05:44 UTCVendor advisory
Show 75 more
  1. 2026-08-16 05:44 UTCGHSA enrichment
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 16:06 UTCVendor advisory
  5. 2026-08-14 16:06 UTCGHSA enrichment
  6. 2026-08-14 04:05 UTCEG score recompute
  7. 2026-08-14 04:05 UTCVendor advisory
  8. 2026-08-14 04:05 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 08:29 UTCVendor advisory
  11. 2026-08-13 08:29 UTCGHSA enrichment
  12. 2026-08-12 17:46 UTCEG score recompute
  13. 2026-08-12 17:46 UTCVendor advisory
  14. 2026-08-12 17:46 UTCGHSA enrichment
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 16:40 UTCEG score recompute
  17. 2026-08-11 16:40 UTCVendor advisory
  18. 2026-08-11 16:40 UTCGHSA enrichment
  19. 2026-08-11 02:07 UTCEG score recompute
  20. 2026-08-11 02:07 UTCVendor advisory
  21. 2026-08-11 02:07 UTCGHSA enrichment
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 03:19 UTCVendor advisory
  24. 2026-08-10 03:19 UTCGHSA enrichment
  25. 2026-08-09 15:18 UTCEG score recompute
  26. 2026-08-09 15:18 UTCVendor advisory
  27. 2026-08-09 15:18 UTCGHSA enrichment
  28. 2026-08-09 13:46 UTCEPSS rescore
  29. 2026-08-09 03:16 UTCEG score recompute
  30. 2026-08-09 03:16 UTCVendor advisory
  31. 2026-08-09 03:16 UTCGHSA enrichment
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-08 12:33 UTCVendor advisory
  34. 2026-08-08 12:33 UTCGHSA enrichment
  35. 2026-08-08 00:31 UTCEG score recompute
  36. 2026-08-08 00:31 UTCVendor advisory
  37. 2026-08-08 00:31 UTCGHSA enrichment
  38. 2026-08-07 12:30 UTCEG score recompute
  39. 2026-08-07 12:30 UTCVendor advisory
  40. 2026-08-07 12:30 UTCGHSA enrichment
  41. 2026-08-06 13:46 UTCEPSS rescore
  42. 2026-08-06 12:38 UTCVendor advisory
  43. 2026-08-06 12:38 UTCGHSA enrichment
  44. 2026-08-06 00:37 UTCEG score recompute
  45. 2026-08-06 00:37 UTCVendor advisory
  46. 2026-08-06 00:37 UTCGHSA enrichment
  47. 2026-08-05 19:17 UTCEPSS rescore
  48. 2026-08-05 12:36 UTCEG score recompute
  49. 2026-08-05 12:36 UTCVendor advisory
  50. 2026-08-05 12:36 UTCGHSA enrichment
  51. 2026-08-04 15:10 UTCEPSS rescore
  52. 2026-08-04 10:38 UTCEPSS rescore
  53. 2026-08-03 20:59 UTCEG score recompute
  54. 2026-08-03 20:59 UTCVendor advisory
  55. 2026-08-03 20:59 UTCGHSA enrichment
  56. 2026-08-03 10:36 UTCEPSS rescore
  57. 2026-08-02 22:43 UTCVendor advisory
  58. 2026-08-02 22:43 UTCGHSA enrichment
  59. 2026-08-02 10:42 UTCEG score recompute
  60. 2026-08-02 10:42 UTCVendor advisory
  61. 2026-08-02 10:42 UTCGHSA enrichment
  62. 2026-08-02 02:27 UTCEPSS rescore
  63. 2026-08-01 04:16 UTCEPSS rescore
  64. 2026-07-30 16:28 UTCEPSS rescore
  65. 2026-07-30 01:30 UTCEPSS rescore
  66. 2026-07-28 15:36 UTCEPSS rescore
  67. 2026-07-26 14:54 UTCEPSS rescore
  68. 2026-07-26 14:54 UTCEPSS rescore
  69. 2026-07-25 14:18 UTCEPSS rescore
  70. 2026-07-25 14:17 UTCEPSS rescore
  71. 2026-07-24 14:17 UTCEPSS rescore
  72. 2026-07-23 14:18 UTCEPSS rescore
  73. 2026-07-23 14:18 UTCEPSS rescore
  74. 2026-07-23 03:08 UTCEG score recompute
  75. 2026-07-22 14:08 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-31673?
CVE-2026-31673 is a high vulnerability published on April 25, 2026. In the Linux kernel, the following vulnerability has been resolved: afunix: read UNIXDIAGVFS data under unixstate_lock Exact UNIX diag lookups hold a reference to the socket, but not to u->path. Meanwhile, unixreleasesock() clears u->path under unixstatelock() and drops the path reference after…
When was CVE-2026-31673 disclosed?
CVE-2026-31673 was first published in the National Vulnerability Database on April 25, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31673 actively exploited?
CVE-2026-31673 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-31673?
CVE-2026-31673 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31673?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31673, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31673

Explore →

Is Your Infrastructure Affected by CVE-2026-31673?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs