CVE-2026-53233: netdev: fix double-free in netdev_nl_bind_rx_doit()
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.17% (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 9b019376cbee10c4f9184d1745fa37d156e36f30, c299321bc6232770ce378d6fa6bc46004d2d7fdb, c849de7d8757a7af801fc4a4058f71d481d367f2.
Low priority for now. Upgrade to Linux Linux 9b019376cbee10c4f9184d1745fa37d156e36f30, c299321bc6232770ce378d6fa6bc46004d2d7fdb, c849de7d8757a7af801fc4a4058f71d481d367f2 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: netdev: fix double-free in netdev_nl_bind_rx_doit() Sashiko flags that genlmsg_reply() always consumes the skb. The error path calls nlmsg_free(rsp) so we can't jump directly to it. Let's not unbind, just propagate the error to the user. This is the typical way of handling genlmsg_reply() failures. They shouldn't happen unless user does something silly like calling the kernel with an already-full rcvbuf.
- BDU:2026-14054
- SUSE-SU-2026:23257-1
- SUSE-SU-2026:23258-1
- SUSE-SU-2026:23259-1
- SUSE-SU-2026:23260-1
- SUSE-SU-2026:23261-1
- SUSE-SU-2026:23262-1
- SUSE-SU-2026:23263-1
- SUSE-SU-2026:23264-1
- SUSE-SU-2026:23265-1
- SUSE-SU-2026:23266-1
- SUSE-SU-2026:23267-1
- SUSE-SU-2026:23268-1
- SUSE-SU-2026:23269-1
- SUSE-SU-2026:23270-1
- SUSE-SU-2026:23279-1
- SUSE-SU-2026:23280-1
- SUSE-SU-2026:23281-1
- SUSE-SU-2026:23282-1
- SUSE-SU-2026:23283-1
- Published
- Jun 25, 2026
- Updated
- Jul 7, 2026
- EPSS
- 0.1% · 6th 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%
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.12 and later · before 6.12.94
- linux linux kernel6.13 and later · before 6.18.36
- linux linux kernel6.19 and later · before 7.0.13
- 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.12affected
- 170aafe35cb98e0f3fbacb446ea86389fbce22ea and later · before e055ca9205d3eb6aec3e5fe4ecc18abbbf18c599affected · git
- 170aafe35cb98e0f3fbacb446ea86389fbce22ea and later · before c299321bc6232770ce378d6fa6bc46004d2d7fdbaffected · git
- 170aafe35cb98e0f3fbacb446ea86389fbce22ea and later · before 9b019376cbee10c4f9184d1745fa37d156e36f30affected · git
- 170aafe35cb98e0f3fbacb446ea86389fbce22ea and later · before c849de7d8757a7af801fc4a4058f71d481d367f2affected · git
- before 6.12not affected · semver
- 6.12.94 and later · up to and including 6.12.*not affected · semver
- 6.18.36 and later · up to and including 6.18.*not affected · semver
- 7.0.13 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:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.13-1 | 7.0.13-1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_10 | before 6-160000.1.1 | 6-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_11 | before 6-160000.1.1 | 6-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_12 | before 4-160000.1.1 | 4-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_13 | before 4-160000.1.2 | 4-160000.1.2 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_14 | before 4-160000.1.1 | 4-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_15 | before 2-160000.1.1 | 2-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_2 | before 13-160000.1.1 | 13-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_3 | before 12-160000.1.1 | 12-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_4 | before 11-160000.1.1 | 11-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_5 | before 10-160000.1.1 | 10-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_6 | before 9-160000.1.1 | 9-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_7 | before 8-160000.1.1 | 8-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_8 | before 7-160000.1.1 | 7-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16_Update_9 | before 6-160000.1.1 | 6-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_10 | before 6-160000.1.1 | 6-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_11 | before 6-160000.1.1 | 6-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_12 | before 4-160000.1.1 | 4-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_13 | before 4-160000.1.1 | 4-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_14 | before 4-160000.1.1 | 4-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_15 | before 2-160000.1.1 | 2-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_2 | before 12-160000.1.1 | 12-160000.1.1 |
| SUSE:Linux Micro 6.2 | kernel-livepatch-SLE16-RT_Update_3 | before 11-160000.1.1 | 11-160000.1.1 |
+6
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-53216Jun 25, 2026 · net: mvpp2: limit XDP frame size to the RX buffer39Monitor
- ← EarlierCVE-2026-53231Jun 25, 2026 · net: phy: don't try to setup PHY-driven SFP cages when using genphy22Monitor
- Later →CVE-2026-53234Jun 25, 2026 · net: ibm: emac: Fix use-after-free during device removal31Monitor
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 | 9b019376cbee10c4f9184d1745fa37d156e36f30 | Vendor (CNA) |
| Linux Linux | c299321bc6232770ce378d6fa6bc46004d2d7fdb | Vendor (CNA) |
| Linux Linux | c849de7d8757a7af801fc4a4058f71d481d367f2 | Vendor (CNA) |
| Linux Linux | e055ca9205d3eb6aec3e5fe4ecc18abbbf18c599 | Vendor (CNA) |
| debian:linux | 6.12.94-1 · Debian:13 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_10 | 6-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_11 | 6-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_12 | 4-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_13 | 4-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_14 | 4-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_15 | 2-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_4 | 11-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_5 | 10-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_6 | 9-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_7 | 8-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_8 | 7-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_9 | 6-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-529931 days aparttipc: fix double-free in tipc_buf_append()39Monitor
- CVE-2026-6388824 days apartscsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()39Monitor
- CVE-2026-6438330 days apartsmb: client: fix double-free in SMB2_flush() replay39Monitor
- CVE-2026-6438430 days apartsmb: client: fix change notify replay double-free39Monitor
- CVE-2026-6438530 days apartsmb: client: fix double-free in SMB2_ioctl() replay39Monitor
- CVE-2026-6438730 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.