netrom: fix double-free in nr_route_frame()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 9f5fa78d9980fe75a69835521627ab7943cb3d67| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netrom: fix double-free in nr_route_frame()
In nr_route_frame(), old_skb is immediately freed without checking if nr_neigh->ax25 pointer is NULL. Therefore, if nr_neigh->ax25 is NULL, the caller function will free old_skb again, causing a double-free bug.
Therefore, to prevent this, we need to modify it to check whether nr_neigh->ax25 is NULL before freeing old_skb.
From the CVE record · Linux
The Linux kernel's netrom nr_route_frame() can free old_skb twice when nr_neigh->ax25 is NULL. The input does not specify how an attacker could trigger this condition or whether access or user interaction is required.
Anyone running the Linux kernel should check whether their version includes the netrom fix; affected versions are not specified.