xfrm: xfrm_alloc_spi shouldn't use 0 as SPI
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
| No fix yet |
In the Linux kernel, the following vulnerability has been resolved:
xfrm: xfrm_alloc_spi shouldn't use 0 as SPI
x->id.spi == 0 means "no SPI assigned", but since commit 94f39804d891 ("xfrm: Duplicate SPI Handling"), we now create states and add them to the byspi list with this value.
__xfrm_state_delete doesn't remove those states from the byspi list, since they shouldn't be there, and this shows up as a UAF the next time we go through the byspi list.
From the CVE record · Linux
The Linux kernel's xfrm code can add a state with an SPI of zero to the byspi list, then fail to remove it when the state is deleted. A later traversal of that list can trigger a use-after-free. The input does not specify an attack path, authentication requirements, or user interaction.
Teams running Linux kernels should check their versions; the affected version range is not specified.