Look up another CVE · open CVE-2026-52932 in the interactive tracker
CVE-2026-52932
xfrm: ipcomp: Free destination pages on acomp errors
Published 2026-06-24 (4 months ago) by the Linux kernel CNA. Subsystem net/xfrm. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-52932 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Move the out_free_req label up by a couple of lines so that the allocated dst SG list gets freed on error as well as success.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
net/xfrm/xfrm_ipcomp.c
- What this is
- NETWORKING [IPSEC]MAINTAINERS section matched on net/xfrm/ · netdev@vger.kernel.org · Maintained
- Kernel module
- xfrm_ipcomp
Check it on the machine
grep -wE 'CONFIG_XFRM|CONFIG_XFRM_IPCOMP' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w xfrm_ipcompPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this as a loadable module. Every release below compiles it as a module on every flavour, so whether the code is in the running kernel depends on whether that module is loaded.
- bookworm, trixie, forky, sidm
- m
- a loadable module on every flavour - check lsmod, can be blacklisted
- Build switches
- CONFIG_XFRM, CONFIG_XFRM_IPCOMP
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-06-24 (4 months ago)source
- CVSS
- 7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.61%, higher than 48.1% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- net/xfrm
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.15 | 6.18.35 | dc6dcba80d72 |
| 6.15 | 7.0.12 | b30aa173c380 |
| 6.15 | 7.1 | 7dbac7680eb6 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:NAttack vector, network
- Inbound IPComp packets are handled by the IPv4/IPv6 protocol handlers and dispatched through xfrm_input() to ipcomp_input() when they match an installed IPComp SA. A remote peer can send malformed IPComp payloads to a reasonably deployed IPsec/IPComp endpoint.
- AC:LAttack complexity, low
- The attacker only needs to send packets with invalid or oversized compressed data that make crypto_acomp_decompress() return an error after destination pages are allocated. There is no race or memory-layout prerequisite beyond reaching a configured IPComp SA.
- PR:NPrivileges required, none
- On the remote receive path, no local privileges or authenticated user account are required; packets are processed before any per-user credential check. SA configuration is a deployment precondition, not an attacker privilege.
- UI:NUser interaction, none
- No victim user action is required after the target is running with an inbound IPComp SA. The attacker can repeatedly trigger the error path by sending network packets.
- S:UScope, unchanged
- The vulnerability consumes kernel memory within the same operating-system security authority. It does not cross a VM, hypervisor, IOMMU, or separate security-scope boundary.
- C:NConfidentiality impact, none
- The bug leaks caller-allocated destination pages on the error path but does not expose their contents to the attacker. No arbitrary read or information disclosure primitive was found.
- I:NIntegrity impact, none
- The missed cleanup is a memory/resource leak, not a use-after-free, out-of-bounds write, or control-flow corruption. It does not provide a data modification primitive.
- A:HAvailability impact, high
- Each failed IPComp decompression can leak multiple kernel pages, and a remote attacker can repeat this to exhaust kernel memory and cause system-wide denial of service. Under the required higher-severity rule, this is scored as high availability impact.