CVE-2026-31504

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net: fix fanout UAF in packet_release() via NETDEV_UP race

packet_release() has a race window where NETDEV_UP can re-register a socket into a fanout group's arr[] array. The re-registration is not cleaned up by fanout_release(), leaving a dangling pointer in the fanout array. packet_release() does NOT zero po->num in its bind_lock section. After releasing bind_lock, po->num is still non-zero and po->ifindex still matches the bound device. A concurrent packet_notifier(NETDEV_UP) that already found the socket in sklist can re-register the hook. For fanout sockets, this re-registration calls __fanout_link(sk, po) which adds the socket back into f->arr[] and increments f->num_members, but does NOT increment f->sk_ref.

The fix sets po->num to zero in packet_release while bind_lock is held to prevent NETDEV_UP from linking, preventing the race window.

This bug was found following an additional audit with Claude Code based on CVE-2025-38617.

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
3%
KEV
Not listed

Published

April 22, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

net: fix fanout UAF in packet_release() via NETDEV_UP race - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: fix fanout UAF in packet_release() via NETDEV_UP race - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: fix fanout UAF in packet_release() via NETDEV_UP race - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: fix fanout UAF in packet_release() via NETDEV_UP race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/75fe6db23705a1d55160081f7b37db9665b1880b
generic

net: fix fanout UAF in packet_release() via NETDEV_UP race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/654386baef228c2992dbf604c819e4c7c35fc71b
generic

net: fix fanout UAF in packet_release() via NETDEV_UP race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42cfd7898eeed290c9fb73f732af1f7d6b0a703e
generic

net: fix fanout UAF in packet_release() via NETDEV_UP race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42156f93d123436f2a27c468f18c966b7e5db796
generic

net: fix fanout UAF in packet_release() via NETDEV_UP race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b4c03f8892d955385c202009af7485364731bb9

Vendor Advisories for CVE-2026-31504(2)

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

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04 (6.17.0-29.29~24.04.1) @ noble2026-06-15ubuntu
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-06-15ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.179.163) @ jammy2026-06-15ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1157.167~18.04.1) @ bionic2026-06-15ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.250.234) @ bionic2026-06-15ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-06-15ubuntu
ubuntulinux-tools-oracle-edge (6.17.0-1014.14~24.04.1) @ noble2026-06-15ubuntu
ubuntulinux-tools-azure-lts-20.04 (5.4.0.1163.155) @ focal2026-06-15ubuntu
ubuntulinux-tools-azure-lts-18.04 (4.15.0.1201.169) @ bionic2026-06-15ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1108.117~20.04.1) @ focal2026-06-15ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1049.51) @ jammy2026-06-15ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-06-15ubuntu
ubuntulinux-tools-iot-5.4 (5.4.0.1063.61) @ focal2026-06-15ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.179.189~20.04.1) @ focal2026-06-15ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1025.25) @ noble2026-06-15ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.179.151) @ jammy2026-06-15ubuntu
ubuntulinux-tools-azure-edge (6.17.0-1015.15~24.04.1) @ noble2026-06-15ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.281.315~14.04.1) @ trusty2026-06-15ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1018.19) @ questing2026-06-15ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1143.174) @ focal2026-06-15ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.231.251~18.04.1) @ bionic2026-06-15ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1114.99) @ jammy2026-06-15ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-06-15ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1100.104) @ jammy2026-06-15ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-06-15ubuntu
ubuntulinux-tools-fips (4.4.0.1125.127) @ xenial2026-06-15ubuntu
linuxKernel @ 5.10.253osv

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 (53 versions)5.10.257-1
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-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 (121 versions)6.19.11-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Data Freshness Timeline

(refreshed 8× in last 7d / 65× 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 243 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31504?
CVE-2026-31504 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: net: fix fanout UAF in packetrelease() via NETDEVUP race packetrelease() has a race window where NETDEVUP can re-register a socket into a fanout group's arr[] array. The re-registration is not cleaned up by fanout_release(),…
When was CVE-2026-31504 disclosed?
CVE-2026-31504 was first published in the National Vulnerability Database on April 22, 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-31504 actively exploited?
CVE-2026-31504 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 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-31504?
CVE-2026-31504 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31504?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31504, 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-31504

Explore →

Is Your Infrastructure Affected by CVE-2026-31504?

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