CVE-2025-22058: udp: Fix memory accounting leak.
Noroxi assessment
Priority: Monitor (action score 22/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.23% (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 13550273171f5108b1ac572d8f72f4256ab92854, 3836029448e76c1e6f77cc5fe0adc09b018b5fa8, 9122fec396950cc866137af7154b1d0d989be52e; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.
Low priority for now. Upgrade to Linux Linux 13550273171f5108b1ac572d8f72f4256ab92854, 3836029448e76c1e6f77cc5fe0adc09b018b5fa8, 9122fec396950cc866137af7154b1d0d989be52e; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 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: udp: Fix memory accounting leak. Matt Dowling reported a weird UDP memory usage issue. Under normal operation, the UDP memory usage reported in /proc/net/sockstat remains close to zero. However, it occasionally spiked to 524,288 pages and never dropped. Moreover, the value doubled when the application was terminated. Finally, it caused intermittent packet drops. We can reproduce the issue with the script below [0]: 1. /proc/net/sockstat reports 0 pages # cat /proc/net/sockstat | grep UDP: UDP: inuse 1 mem 0 2. Run the script till the report reaches 524,288 # python3 test.py & sleep 5 # cat /proc/net/sockstat | grep UDP: UDP: inuse 3 mem 524288 <-- (INT_MAX + 1) >> PAGE_SHIFT 3. Kill the socket and confirm the number never drops # pkill python3 && sleep 5 # cat /proc/net/sockstat | grep UDP: UDP: inuse 1 mem 524288 4. (necessary since v6.0) Trigger proto_memory_pcpu_drain() # python3 test.py & sleep 1 && pkill python3 5. The number doubles # cat /proc/net/sockstat | grep UDP: UDP: inuse 1 mem 1048577 The application set INT_MAX to SO_RCVBUF, which triggered an integer overflow in udp_rmem_release(). When a socket is close()d, udp_destruct_common() purges its receive queue and sums up skb->truesize in the queue. This total is calculated and stored in a local unsigned integer variable. The total size is then passed to udp_rmem_release() to adjust memory accounting. However, because the function takes a signed integer argument, the total size can wrap around, causing an overflow. Then, the released amount is calculated as follows: 1) Add size to sk->sk_forward_alloc. 2) Round down sk->sk_forward_alloc to the nearest lower multiple of PAGE_SIZE and assign it to amount. 3) Subtract amount from sk->sk_forward_alloc. 4) Pass amount >> PAGE_SHIFT to __sk_mem_reduce_allocated(). When the issue occurred, the total in udp_destruct_common() was 2147484480 (INT_MAX + 833), which was cast to -2147482816 in udp_rmem_release(). At 1) sk->sk_forward_alloc is changed from 3264 to -2147479552, and 2) sets -2147479552 to amount. 3) reverts the wraparound, so we don't see a warning in inet_sock_destruct(). However, udp_memory_allocated ends up doubling at 4). Since commit 3cd3399dd7a8 ("net: implement per-cpu reserves for memory_allocated"), memory usage no longer doubles immediately after a socket is close()d because __sk_mem_reduce_allocated() caches the amount in udp_memory_per_cpu_fw_alloc. However, the next time a UDP socket receives a packet, the subtraction takes effect, causing UDP memory usage to double. This issue makes further memory allocation fail once the socket's sk->sk_rmem_alloc exceeds net.ipv4.udp_rmem_min, resulting in packet drops. To prevent this issue, let's use unsigned int for the calculation and call sk_forward_alloc_add() only once for the small delta. Note that first_packet_length() also potentially has the same problem. [0]: from socket import * SO_RCVBUFFORCE = 33 INT_MAX = (2 ** 31) - 1 s = socket(AF_INET, SOCK_DGRAM) s.bind(('', 0)) s.setsockopt(SOL_SOCKET, SO_RCVBUFFORCE, INT_MAX) c = socket(AF_INET, SOCK_DGRAM) c.connect(s.getsockname()) data = b'a' * 100 while True: c.send(data)
- BDU:2025-11911
- ALSA-2025:14420
- ALSA-2025:14438
- ALSA-2025:14439
- ALSA-2025:15005
- DLA-4404-1
- RHSA-2025:14420
- RHSA-2025:14438
- RHSA-2025:14439
- RHSA-2025:15005
- RHSA-2025:15656
- RHSA-2025:15657
- RHSA-2025:15658
- RHSA-2025:15669
- RHSA-2025:15670
- RHSA-2025:16669
- RHSA-2025:17009
- RHSA-2025:17124
- RLSA-2025:14420
- RLSA-2025:15005
- Published
- Apr 16, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-401
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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 kernel4.10 and later · before 5.4.301
- linux linux kernel5.5 and later · before 5.10.246
- linux linux kernel5.11 and later · before 5.15.195
- linux linux kernel5.16 and later · before 6.1.134
- linux linux kernel6.2 and later · before 6.6.87
- linux linux kernel6.7 and later · before 6.12.23
- linux linux kernel6.13 and later · before 6.13.11
- linux linux kernel6.14 and later · before 6.14.2
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
- 4.10affected
- f970bd9e3a06f06df8d8ecf1f8ad2c8615cc17eb and later · before 13550273171f5108b1ac572d8f72f4256ab92854affected · git
- f970bd9e3a06f06df8d8ecf1f8ad2c8615cc17eb and later · before d9c8266ce536e8314d84370e983afcaa36fb19cfaffected · git
- f970bd9e3a06f06df8d8ecf1f8ad2c8615cc17eb and later · before c3ad8c30b6b109283d2643e925f8e65f2e7ab34eaffected · git
- f970bd9e3a06f06df8d8ecf1f8ad2c8615cc17eb and later · before 9122fec396950cc866137af7154b1d0d989be52eaffected · git
- f970bd9e3a06f06df8d8ecf1f8ad2c8615cc17eb and later · before aeef6456692c6f11ae53d278df64f1316a2a405aaffected · git
- f970bd9e3a06f06df8d8ecf1f8ad2c8615cc17eb and later · before a116b271bf3cb72c8155b6b7f39083c1b80dcd00affected · git
- f970bd9e3a06f06df8d8ecf1f8ad2c8615cc17eb and later · before c4bac6c398118fba79e32b1cd01db22dbfe29fbfaffected · git
- f970bd9e3a06f06df8d8ecf1f8ad2c8615cc17eb and later · before 3836029448e76c1e6f77cc5fe0adc09b018b5fa8affected · git
- f970bd9e3a06f06df8d8ecf1f8ad2c8615cc17eb and later · before df207de9d9e7a4d92f8567e2c539d9c8c12fd99daffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-55.30.1.el10_0 | 6.12.0-55.30.1.el10_0 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-55.30.1.el10_0 | 6.12.0-55.30.1.el10_0 |
| AlmaLinux:8 | bpftool | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.71.1.el8_10 | 4.18.0-553.71.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.71.1.rt7.412.el8_10 | 4.18.0-553.71.1.rt7.412.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.71.1.rt7.412.el8_10 | 4.18.0-553.71.1.rt7.412.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.71.1.rt7.412.el8_10 | 4.18.0-553.71.1.rt7.412.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.71.1.rt7.412.el8_10 | 4.18.0-553.71.1.rt7.412.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.71.1.rt7.412.el8_10 | 4.18.0-553.71.1.rt7.412.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.71.1.rt7.412.el8_10 | 4.18.0-553.71.1.rt7.412.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.71.1.rt7.412.el8_10 | 4.18.0-553.71.1.rt7.412.el8_10 |
+96
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-2025-22052Apr 16, 2025 · staging: gpib: Fix Oops after disconnect in ni_usb22Monitor
- ← EarlierCVE-2025-22054Apr 16, 2025 · arcnet: Add NULL check in com20020pci_probe()22Monitor
- Later →CVE-2025-22059Apr 16, 2025 · udp: Fix multiple wraparounds of sk->sk_rmem_alloc.22Monitor
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 | 13550273171f5108b1ac572d8f72f4256ab92854 | Vendor (CNA) |
| Linux Linux | 3836029448e76c1e6f77cc5fe0adc09b018b5fa8 | Vendor (CNA) |
| Linux Linux | 9122fec396950cc866137af7154b1d0d989be52e | Vendor (CNA) |
| Linux Linux | a116b271bf3cb72c8155b6b7f39083c1b80dcd00 | Vendor (CNA) |
| Linux Linux | aeef6456692c6f11ae53d278df64f1316a2a405a | Vendor (CNA) |
| Linux Linux | c3ad8c30b6b109283d2643e925f8e65f2e7ab34e | Vendor (CNA) |
| Linux Linux | c4bac6c398118fba79e32b1cd01db22dbfe29fbf | Vendor (CNA) |
| Linux Linux | d9c8266ce536e8314d84370e983afcaa36fb19cf | Vendor (CNA) |
| Linux Linux | df207de9d9e7a4d92f8567e2c539d9c8c12fd99d | Vendor (CNA) |
| azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 | 5.15.200.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 5.14.0-570.37.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-570.37.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-570.37.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-570.37.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-570.37.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-570.37.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-570.37.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-570.37.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-570.37.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-570.37.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-570.37.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-570.37.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.135-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-570.37.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-570.37.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-570.37.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-570.37.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-570.37.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+8
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/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.
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 (9 more)Show less
- git.kernel.org/stable/c/3836029448e76c1e6f77cc5fe0adc09b018b5fa8
- git.kernel.org/stable/c/9122fec396950cc866137af7154b1d0d989be52e
- git.kernel.org/stable/c/a116b271bf3cb72c8155b6b7f39083c1b80dcd00
- git.kernel.org/stable/c/aeef6456692c6f11ae53d278df64f1316a2a405a
- git.kernel.org/stable/c/c3ad8c30b6b109283d2643e925f8e65f2e7ab34e
- git.kernel.org/stable/c/c4bac6c398118fba79e32b1cd01db22dbfe29fbf
- git.kernel.org/stable/c/d9c8266ce536e8314d84370e983afcaa36fb19cf
- git.kernel.org/stable/c/df207de9d9e7a4d92f8567e2c539d9c8c12fd99d
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.