---
id: CVE-2026-31504
title: |-
  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[]…
summary: |-
  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[]…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
cwe:
  - CWE-416
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 3.1.1, < 5.10.253'
  - 'linux_kernel >= 5.11, < 5.15.203'
  - 'linux_kernel >= 5.16, < 6.1.168'
  - 'linux_kernel >= 6.2, < 6.6.131'
  - 'linux_kernel >= 6.7, < 6.12.80'
  - 'linux_kernel >= 6.13, < 6.18.21'
  - 'linux_kernel >= 6.19, < 6.19.11'
  - linux_kernel = 3.1
  - linux_kernel = 7.0
patched:
  - linux_kernel 6.19.11
published: '2026-04-22'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T02:19:09.080'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-31504'
references:
  - url: 'https://git.kernel.org/stable/c/1b4c03f8892d955385c202009af7485364731bb9'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/42156f93d123436f2a27c468f18c966b7e5db796'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/42cfd7898eeed290c9fb73f732af1f7d6b0a703e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/654386baef228c2992dbf604c819e4c7c35fc71b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/75fe6db23705a1d55160081f7b37db9665b1880b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ceccbfc6de720ad633519a226715989cfb065af1'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d0c7cdc15fdf8c4f91aca1928e52295d175b6ec6'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ee642b1962caa9aa231c01abbd58bc453ae6b66e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-019113.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-082556.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-457936.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
tags:
  - nvd
  - cve.org
epss: 0.00105
epssPercentile: 0.01044
ingestedAt: '2026-09-08T15:33:26.990Z'
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-10-16T15:10:18.282904Z'
---

## Overview

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.

## Affected

- `linux_kernel >= 3.1.1, < 5.10.253`
- `linux_kernel >= 5.11, < 5.15.203`
- `linux_kernel >= 5.16, < 6.1.168`
- `linux_kernel >= 6.2, < 6.6.131`
- `linux_kernel >= 6.7, < 6.12.80`
- `linux_kernel >= 6.13, < 6.18.21`
- `linux_kernel >= 6.19, < 6.19.11`
- `linux_kernel = 3.1`
- `linux_kernel = 7.0`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.19.11`