CVE-2023-53186: skbuff: Fix a race between coalescing and releasing SKBs
Noroxi assessment
Priority: Monitor (action score 18/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.26% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 0646dc31ca886693274df5749cd0c8c1eaaeb5ca, 5f692c992a3bb9a8018e3488098b401a4229e7ec, 71850b5af92da21b4862a9bc55bda61091247d00.
- Severity is disputed: the assigning authority (CNA) scores it 8.1, NVD 4.7.
Low priority for now. Upgrade to Linux Linux 0646dc31ca886693274df5749cd0c8c1eaaeb5ca, 5f692c992a3bb9a8018e3488098b401a4229e7ec, 71850b5af92da21b4862a9bc55bda61091247d00 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: skbuff: Fix a race between coalescing and releasing SKBs Commit 1effe8ca4e34 ("skbuff: fix coalescing for page_pool fragment recycling") allowed coalescing to proceed with non page pool page and page pool page when @from is cloned, i.e. to->pp_recycle --> false from->pp_recycle --> true skb_cloned(from) --> true However, it actually requires skb_cloned(@from) to hold true until coalescing finishes in this situation. If the other cloned SKB is released while the merging is in process, from_shinfo->nr_frags will be set to 0 toward the end of the function, causing the increment of frag page _refcount to be unexpectedly skipped resulting in inconsistent reference counts. Later when SKB(@to) is released, it frees the page directly even though the page pool page is still in use, leading to use-after-free or double-free errors. So it should be prohibited. The double-free error message below prompted us to investigate: BUG: Bad page state in process swapper/1 pfn:0e0d1 page:00000000c6548b28 refcount:-1 mapcount:0 mapping:0000000000000000 index:0x2 pfn:0xe0d1 flags: 0xfffffc0000000(node=0|zone=1|lastcpupid=0x1fffff) raw: 000fffffc0000000 0000000000000000 ffffffff00000101 0000000000000000 raw: 0000000000000002 0000000000000000 ffffffffffffffff 0000000000000000 page dumped because: nonzero _refcount CPU: 1 PID: 0 Comm: swapper/1 Tainted: G E 6.2.0+ Call Trace: <IRQ> dump_stack_lvl+0x32/0x50 bad_page+0x69/0xf0 free_pcp_prepare+0x260/0x2f0 free_unref_page+0x20/0x1c0 skb_release_data+0x10b/0x1a0 napi_consume_skb+0x56/0x150 net_rx_action+0xf0/0x350 ? __napi_schedule+0x79/0x90 __do_softirq+0xc8/0x2b1 __irq_exit_rcu+0xb9/0xf0 common_interrupt+0x82/0xa0 </IRQ> <TASK> asm_common_interrupt+0x22/0x40 RIP: 0010:default_idle+0xb/0x20
- Published
- Sep 15, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- CWE-362
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.7
- CNA · Linux
- 8.1
- 3.4 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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 kernel5.15 and later · before 5.15.108
- linux linux kernel5.16 and later · before 6.1.25
- linux linux kernel6.2 and later · before 6.2.12
- linux linux kernel6.3
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
- 5.15affected
- 53e0961da1c7bbdabd1abebb20de403ec237ec09 and later · before 906a6689bb0191ad2a44131a3377006aa098af59affected · git
- 53e0961da1c7bbdabd1abebb20de403ec237ec09 and later · before 71850b5af92da21b4862a9bc55bda61091247d00affected · git
- 53e0961da1c7bbdabd1abebb20de403ec237ec09 and later · before 5f692c992a3bb9a8018e3488098b401a4229e7ecaffected · git
- 53e0961da1c7bbdabd1abebb20de403ec237ec09 and later · before 0646dc31ca886693274df5749cd0c8c1eaaeb5caaffected · git
- before 5.15not affected · semver
- 5.15.108 and later · up to and including 5.15.*not affected · semver
- 6.1.25 and later · up to and including 6.1.*not affected · semver
- 6.2.12 and later · up to and including 6.2.*not affected · semver
- 6.3 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:12 | linux | before 6.1.25-1 | 6.1.25-1 |
| Red Hat:rhel_e4s:9.2::appstream | bpftool-debuginfo | before 0:7.0.0-284.142.1.el9_2 | 0:7.0.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-debug-devel | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-debuginfo | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-devel | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-devel-matched | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debug-debuginfo | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debug-devel | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debug-devel-matched | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-devel | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-devel-matched | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-doc | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-tools-debuginfo | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-zfcpdump-devel | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-zfcpdump-devel-matched | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | perf | before 0:5.14.0-284.142.1.el9_2 | 0:5.14.0-284.142.1.el9_2 |
+50
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-2023-53184Sep 15, 2025 · arm64/sme: Set new vector length before reallocating31Monitor
- ← EarlierCVE-2023-53185Sep 15, 2025 · wifi: ath9k: don't allow to overwrite ENDPOINT0 attributes22Monitor
- Later →CVE-2023-53188Sep 15, 2025 · net: openvswitch: fix race on port output18Monitor
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 | 0646dc31ca886693274df5749cd0c8c1eaaeb5ca | Vendor (CNA) |
| Linux Linux | 5f692c992a3bb9a8018e3488098b401a4229e7ec | Vendor (CNA) |
| Linux Linux | 71850b5af92da21b4862a9bc55bda61091247d00 | Vendor (CNA) |
| Linux Linux | 906a6689bb0191ad2a44131a3377006aa098af59 | Vendor (CNA) |
| debian:linux | 6.1.25-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.142.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.142.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.142.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.142.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.142.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.142.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.142.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.142.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.142.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.142.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.142.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-284.142.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | 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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- 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.