Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-31504: net: fix fanout UAF in packet_release() via NETDEV_UP race

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.10% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1b4c03f8892d955385c202009af7485364731bb9, 42156f93d123436f2a27c468f18c966b7e5db796, 42cfd7898eeed290c9fb73f732af1f7d6b0a703e; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 1b4c03f8892d955385c202009af7485364731bb9, 42156f93d123436f2a27c468f18c966b7e5db796, 42cfd7898eeed290c9fb73f732af1f7d6b0a703e; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Apr 22, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 1th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-31504

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.1.1 and later · before 5.10.253
  • linux linux kernel5.11 and later · before 5.15.203
  • linux linux kernel5.16 and later · before 6.1.168
  • linux linux kernel6.2 and later · before 6.6.131
  • linux linux kernel6.7 and later · before 6.12.80
  • linux linux kernel6.13 and later · before 6.18.21
  • linux linux kernel6.19 and later · before 6.19.11
  • linux linux kernel3.1
  • linux linux kernel7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.1affected
    • ce06b03e60fc19c680d1bf873e779bf11c2fc518 and later · before ee642b1962caa9aa231c01abbd58bc453ae6b66eaffected · git
    • ce06b03e60fc19c680d1bf873e779bf11c2fc518 and later · before 42cfd7898eeed290c9fb73f732af1f7d6b0a703eaffected · git
    • ce06b03e60fc19c680d1bf873e779bf11c2fc518 and later · before 1b4c03f8892d955385c202009af7485364731bb9affected · git
    • ce06b03e60fc19c680d1bf873e779bf11c2fc518 and later · before 654386baef228c2992dbf604c819e4c7c35fc71baffected · git
    • ce06b03e60fc19c680d1bf873e779bf11c2fc518 and later · before 75fe6db23705a1d55160081f7b37db9665b1880baffected · git
    • ce06b03e60fc19c680d1bf873e779bf11c2fc518 and later · before d0c7cdc15fdf8c4f91aca1928e52295d175b6ec6affected · git
    • ce06b03e60fc19c680d1bf873e779bf11c2fc518 and later · before ceccbfc6de720ad633519a226715989cfb065af1affected · git
    • ce06b03e60fc19c680d1bf873e779bf11c2fc518 and later · before 42156f93d123436f2a27c468f18c966b7e5db796affected · git
    • before 3.1not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.170-16.1.170-1
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.11-16.19.11-1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_69before 17-2.117-2.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_70before 17-2.117-2.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_71before 14-2.114-2.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_79before 5-2.15-2.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_80before 4-2.14-2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_40before 21-150400.2.121-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_44before 15-150400.2.115-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_45before 13-150400.2.113-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_46before 9-150400.2.19-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_47before 9-150400.2.19-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_50before 5-150400.2.15-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_26before 21-150500.2.121-150500.2.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_30before 14-150500.2.114-150500.2.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_38before 4-150500.2.14-150500.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_11before 19-150600.2.119-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_12before 19-150600.2.119-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_18before 8-150600.2.18-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_22before 5-150600.2.15-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_23before 4-150600.2.14-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_24before 3-150600.2.13-150600.2.1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_11before 5-150700.2.15-150700.2.1

+46

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-31502Apr 22, 2026 · team: fix header_ops type confusion with non-Ethernet ports
    31Monitor
  • ← EarlierCVE-2026-31503Apr 22, 2026 · udp: Fix wildcard bind conflict check when using hash2
    22Monitor
  • Later →CVE-2026-31505Apr 22, 2026 · iavf: fix out-of-bounds writes in iavf_get_ethtool_stats()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1b4c03f8892d955385c202009af7485364731bb9Vendor (CNA)
Linux Linux42156f93d123436f2a27c468f18c966b7e5db796Vendor (CNA)
Linux Linux42cfd7898eeed290c9fb73f732af1f7d6b0a703eVendor (CNA)
Linux Linux654386baef228c2992dbf604c819e4c7c35fc71bVendor (CNA)
Linux Linux75fe6db23705a1d55160081f7b37db9665b1880bVendor (CNA)
Linux Linuxceccbfc6de720ad633519a226715989cfb065af1Vendor (CNA)
Linux Linuxd0c7cdc15fdf8c4f91aca1928e52295d175b6ec6Vendor (CNA)
Linux Linuxee642b1962caa9aa231c01abbd58bc453ae6b66eVendor (CNA)
azl3 kernel 6.6.130.1-3 on Azure Linux 3.06.6.134.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
debian:linux6.1.170-1 · Debian:12Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0_Update_720-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_819-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_917-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-SLE16_Update_014-160000.4.3 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16_Update_112-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16_Update_103-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16_Update_210-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16_Update_39-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16_Update_48-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16_Update_66-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16_Update_75-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16_Update_84-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records