CVE-2026-64054: net: shaper: reject duplicate leaves in GROUP request
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.12% (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 31767bf852b59f05125b58a17007e4cd1ea9eb2e, 5098b223f0f0c5c18a3884a8b0ea5bd4a0c7bd75, a9a2fa1da619f276580b0d4c5d12efac89e8642b.
Low priority for now. Upgrade to Linux Linux 31767bf852b59f05125b58a17007e4cd1ea9eb2e, 5098b223f0f0c5c18a3884a8b0ea5bd4a0c7bd75, a9a2fa1da619f276580b0d4c5d12efac89e8642b 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: shaper: reject duplicate leaves in GROUP request net_shaper_nl_group_doit() does not deduplicate NET_SHAPER_A_LEAVES entries. When userspace supplies the same leaf handle twice, the same old-parent pointer lands twice in old_nodes[]. The cleanup loop double frees the parent. Of course the same parent may still be in old_nodes[] twice if we are moving multiple of its leaves. Note that this patch also implicitly fixes the fact that the i >= leaves_count path forgets to set ret.
- SUSE-SU-2026:24387-1
- SUSE-SU-2026:24388-1
- SUSE-SU-2026:24389-1
- SUSE-SU-2026:24390-1
- SUSE-SU-2026:24391-1
- SUSE-SU-2026:24392-1
- SUSE-SU-2026:24393-1
- SUSE-SU-2026:24394-1
- SUSE-SU-2026:24395-1
- SUSE-SU-2026:24396-1
- SUSE-SU-2026:24397-1
- SUSE-SU-2026:24398-1
- SUSE-SU-2026:24399-1
- SUSE-SU-2026:24400-1
- SUSE-SU-2026:24401-1
- SUSE-SU-2026:24402-1
- SUSE-SU-2026:24403-1
- SUSE-SU-2026:24415-1
- SUSE-SU-2026:24416-1
- SUSE-SU-2026:24417-1
- Published
- Jul 19, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-415
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
- partial
Vulnrichment: CISA's decision-tree inputs.
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 kernel6.13 and later · before 6.18.34
- linux linux kernel6.19 and later · before 7.0.11
- linux linux kernel7.1
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
- 6.13affected
- 5d5d4700e75d861e83bf18eb6bf66ff90f85fe4e and later · before 5098b223f0f0c5c18a3884a8b0ea5bd4a0c7bd75affected · git
- 5d5d4700e75d861e83bf18eb6bf66ff90f85fe4e and later · before 31767bf852b59f05125b58a17007e4cd1ea9eb2eaffected · git
- 5d5d4700e75d861e83bf18eb6bf66ff90f85fe4e and later · before a9a2fa1da619f276580b0d4c5d12efac89e8642baffected · git
- before 6.13not affected · semver
- 6.18.34 and later · up to and including 6.18.*not affected · semver
- 7.0.11 and later · up to and including 7.0.*not affected · semver
- 7.1 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 7.0.12-1 | 7.0.12-1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_0 | before 20-160000.4.3 | 20-160000.4.3 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_1 | before 18-160000.1.1 | 18-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_10 | before 9-160000.1.1 | 9-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_11 | before 9-160000.1.1 | 9-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_12 | before 7-160000.1.1 | 7-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_13 | before 7-160000.1.2 | 7-160000.1.2 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_14 | before 7-160000.1.1 | 7-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_15 | before 5-160000.1.1 | 5-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_16 | before 4-160000.1.1 | 4-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_2 | before 16-160000.1.1 | 16-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_3 | before 15-160000.1.1 | 15-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_4 | before 14-160000.1.1 | 14-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_5 | before 13-160000.1.1 | 13-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_6 | before 12-160000.1.1 | 12-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_7 | before 11-160000.1.1 | 11-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_8 | before 10-160000.1.1 | 10-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_9 | before 9-160000.1.1 | 9-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_0 | before 18-160000.3.4 | 18-160000.3.4 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_1 | before 17-160000.1.1 | 17-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_10 | before 9-160000.1.1 | 9-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_11 | before 9-160000.1.1 | 9-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_12 | before 7-160000.1.1 | 7-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_13 | before 7-160000.1.1 | 7-160000.1.1 |
+11
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-64052Jul 19, 2026 · block: bio-integrity: Fix null-ptr-deref in bio_integrity_map_user()22Monitor
- ← EarlierCVE-2026-64053Jul 19, 2026 · block: don't overwrite bip_vcnt in bio_integrity_copy_user()31Monitor
- Later →CVE-2026-64057Jul 19, 2026 · afs: Fix the locking used by afs_get_link()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 | 31767bf852b59f05125b58a17007e4cd1ea9eb2e | Vendor (CNA) |
| Linux Linux | 5098b223f0f0c5c18a3884a8b0ea5bd4a0c7bd75 | Vendor (CNA) |
| Linux Linux | a9a2fa1da619f276580b0d4c5d12efac89e8642b | Vendor (CNA) |
| debian:linux | 7.0.12-1 · Debian:14 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_10 | 9-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_11 | 9-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_12 | 7-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_13 | 7-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_14 | 7-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_15 | 5-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_16 | 4-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_4 | 14-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_5 | 13-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_6 | 12-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_7 | 11-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_9 | 9-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- CVE-2026-638880 days apartscsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()39Monitor
- CVE-2026-643836 days apartsmb: client: fix double-free in SMB2_flush() replay39Monitor
- CVE-2026-643846 days apartsmb: client: fix change notify replay double-free39Monitor
- CVE-2026-643856 days apartsmb: client: fix double-free in SMB2_ioctl() replay39Monitor
- CVE-2026-643866 days apartsmb: client: fix query_info() replay double-free39Monitor
- CVE-2026-643876 days apartsmb: client: fix query directory replay double-free39Monitor
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-415 · Double FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
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 (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.