xfrm: iptfs: preserve shared-frag marker in iptfs_consume_frags()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.367.0.137.1In the Linux kernel, the following vulnerability has been resolved:
xfrm: iptfs: preserve shared-frag marker in iptfs_consume_frags()
iptfs_consume_frags() transfers paged fragments from one socket buffer to another but fails to propagate the SKBFL_SHARED_FRAG flag. This is the same class of bug that was fixed in skb_try_coalesce() for CVE-2026-46300: when fragments backed by read-only page-cache pages are merged, the marker indicating their shared nature must be preserved so that ESP can decide correctly whether in-place encryption is safe.
Apply the same two-line fix used in skb_try_coalesce() to iptfs_consume_frags().
From the CVE record · Linux
The Linux kernel's iptfs_consume_frags() can lose a marker identifying shared, read-only page-cache fragments when transferring them between socket buffers. This can cause ESP to incorrectly decide that in-place encryption is safe. The input does not specify how an attacker could trigger the issue or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with xfrm iptfs should check their versions against the vendor advisory; affected versions were not provided.