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.
- BDU:2026-11258
- SUSE-SU-2026:22276-1
- SUSE-SU-2026:22277-1
- SUSE-SU-2026:22278-1
- SUSE-SU-2026:22279-1
- SUSE-SU-2026:22280-1
- SUSE-SU-2026:22281-1
- SUSE-SU-2026:22282-1
- SUSE-SU-2026:22283-1
- SUSE-SU-2026:22288-1
- SUSE-SU-2026:22383-1
- SUSE-SU-2026:22384-1
- SUSE-SU-2026:22385-1
- SUSE-SU-2026:22386-1
- SUSE-SU-2026:22387-1
- SUSE-SU-2026:22388-1
- SUSE-SU-2026:22389-1
- SUSE-SU-2026:22390-1
- SUSE-SU-2026:22391-1
- SUSE-SU-2026:22396-1
- Published
- Apr 22, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-416
Report tools
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.11-1 | 6.19.11-1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_69 | before 17-2.1 | 17-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_70 | before 17-2.1 | 17-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_71 | before 14-2.1 | 14-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_79 | before 5-2.1 | 5-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_80 | before 4-2.1 | 4-2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_40 | before 21-150400.2.1 | 21-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_44 | before 15-150400.2.1 | 15-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_45 | before 13-150400.2.1 | 13-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_46 | before 9-150400.2.1 | 9-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_47 | before 9-150400.2.1 | 9-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_50 | before 5-150400.2.1 | 5-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_26 | before 21-150500.2.1 | 21-150500.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_30 | before 14-150500.2.1 | 14-150500.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_38 | before 4-150500.2.1 | 4-150500.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_11 | before 19-150600.2.1 | 19-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_12 | before 19-150600.2.1 | 19-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_18 | before 8-150600.2.1 | 8-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_22 | before 5-150600.2.1 | 5-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_23 | before 4-150600.2.1 | 4-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_24 | before 3-150600.2.1 | 3-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_11 | before 5-150700.2.1 | 5-150700.2.1 |
+46
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-31502Apr 22, 2026 · team: fix header_ops type confusion with non-Ethernet ports31Monitor
- ← EarlierCVE-2026-31503Apr 22, 2026 · udp: Fix wildcard bind conflict check when using hash222Monitor
- 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 / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1b4c03f8892d955385c202009af7485364731bb9 | Vendor (CNA) |
| Linux Linux | 42156f93d123436f2a27c468f18c966b7e5db796 | Vendor (CNA) |
| Linux Linux | 42cfd7898eeed290c9fb73f732af1f7d6b0a703e | Vendor (CNA) |
| Linux Linux | 654386baef228c2992dbf604c819e4c7c35fc71b | Vendor (CNA) |
| Linux Linux | 75fe6db23705a1d55160081f7b37db9665b1880b | Vendor (CNA) |
| Linux Linux | ceccbfc6de720ad633519a226715989cfb065af1 | Vendor (CNA) |
| Linux Linux | d0c7cdc15fdf8c4f91aca1928e52295d175b6ec6 | Vendor (CNA) |
| Linux Linux | ee642b1962caa9aa231c01abbd58bc453ae6b66e | Vendor (CNA) |
| azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 | 6.6.134.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_7 | 20-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_8 | 19-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_9 | 17-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16_Update_0 | 14-160000.4.3 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16_Update_1 | 12-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16_Update_10 | 3-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16_Update_2 | 10-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16_Update_3 | 9-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16_Update_4 | 8-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16_Update_6 | 6-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16_Update_7 | 5-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16_Update_8 | 4-160000.1.1 · SUSE:Linux Micro 6.2 | Package 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.
Credits
All researchersFinders, 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 FreeCVSS 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.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- git.kernel.org/stable/c/42156f93d123436f2a27c468f18c966b7e5db796
- git.kernel.org/stable/c/42cfd7898eeed290c9fb73f732af1f7d6b0a703e
- git.kernel.org/stable/c/654386baef228c2992dbf604c819e4c7c35fc71b
- git.kernel.org/stable/c/75fe6db23705a1d55160081f7b37db9665b1880b
- git.kernel.org/stable/c/ceccbfc6de720ad633519a226715989cfb065af1
- git.kernel.org/stable/c/d0c7cdc15fdf8c4f91aca1928e52295d175b6ec6
- git.kernel.org/stable/c/ee642b1962caa9aa231c01abbd58bc453ae6b66e
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-082556.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.