Vulnerability · Published Sep 15, 2025 · Assigned by Linux
CVE-2023-53186skbuff: Fix a race between coalescing and releasing SKBs
High 8.1
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 19% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.25-1 | DEBIAN-CVE-2023-53186 |
| Debian:13 | linux | 6.1.25-1 | DEBIAN-CVE-2023-53186 |
| Debian:14 | linux | 6.1.25-1 | DEBIAN-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux | 5.15.0-79.86 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1042.47 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1045.52 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1045.52.1 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1039.47 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1039.44 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1025.30 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1035.38 | UBUNTU-CVE-2023-53186 |
| Ubuntu:24.04:LTS | linux-intel | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1037.42 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1039.44 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-79.88 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1030.30 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1016.16 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1002.2 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1040.46 | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1035.38 | UBUNTU-CVE-2023-53186 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-53186 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1025.29 | UBUNTU-CVE-2023-53186 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 53e0961da1c7bbdabd1abebb20de403ec237ec09 – before 906a6689bb0191ad2a44131a3377006aa098af5953e0961da1c7bbdabd1abebb20de403ec237ec09 – before 71850b5af92da21b4862a9bc55bda61091247d0053e0961da1c7bbdabd1abebb20de403ec237ec09 – before 5f692c992a3bb9a8018e3488098b401a4229e7ec53e0961da1c7bbdabd1abebb20de403ec237ec09 – before 0646dc31ca886693274df5749cd0c8c1eaaeb5ca |
| Linux | Linux | 5.15 |