net: xfrm: unexport __init-annotated xfrm4_protocol_init()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2f32b51b609faea1e40bb8c5bd305f1351740936 · < 85a055c03691e51499123194a14a0c249cf33227| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: xfrm: unexport __init-annotated xfrm4_protocol_init()
EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic.
modpost used to detect it, but it has been broken for a decade.
Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds.
There are two ways to fix it:
- Remove __init - Remove EXPORT_SYMBOL
I chose the latter for this case because the only in-tree call-site, net/ipv4/xfrm4_policy.c is never compiled as modular. (CONFIG_XFRM is boolean)
From the CVE record · Linux
The Linux kernel exported xfrm4_protocol_init() despite marking it as initialization code that is freed after startup. A module accessing the symbol afterward could cause a kernel panic. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels that export xfrm4_protocol_init() should check their builds; affected versions are not specified.